agent-context-mcp
Enables AI coding agents to read each other's conversation history read-only and sanitized, so you can continue work across different tools without re-explaining context.
README
agent-context-mcp
Three read-only MCP servers that let your AI coding agents read each other's conversation history — so you can pick up in one tool exactly where you left off in another.
If you run more than one coding agent (Claude Code, Codex, Hermes), they normally have no idea what you did in the others. You end up re-explaining the same context several times a day. These servers fix that: each agent can read the past conversations of the others, read-only and sanitized.
| Server | Reads | Source |
|---|---|---|
hermes_context |
Hermes sessions | state.db (SQLite) |
codex_context |
Codex sessions | ~/.codex/sessions/**/rollout-*.jsonl |
claude_code_context |
Claude Code sessions | ~/.claude/projects/**/*.jsonl |
Safety contract
Every server is strictly read-only and sanitizes before returning anything:
- Read-only. Source transcripts/databases are opened read-only. Nothing is ever written back.
- No hidden instructions. System/developer messages, base instructions and harness bootstrap blocks (slash commands,
<system-reminder>, project memory dumps) are excluded. - No reasoning leaks. Assistant "thinking"/reasoning and encrypted chains-of-thought are dropped unless explicitly requested.
- Tools are opt-in. Tool calls/outputs are excluded by default and truncated when included.
- Secrets redacted. API keys, tokens and JWTs are replaced with
[REDACTED_SECRET]. - Tolerates live writes. A half-written trailing JSON line in an active session is ignored, not fatal.
Output is structured Markdown, not raw JSON.
Requirements
- Python 3.10+
- The
mcppackage (installed below)
pip install -r requirements.txt
By default each server auto-detects its source under your home directory. Override with env vars if your stores live elsewhere:
CODEX_SESSIONS_ROOT(default~/.codex/sessions)CLAUDE_PROJECTS_ROOT(default~/.claude/projects)HERMES_HOME(default%LOCALAPPDATA%/hermeson Windows, else~/.hermes)
Install per agent
Use your Python interpreter (python below — use the full path to the interpreter where you installed mcp).
Claude Code
claude mcp add codex_context --scope user -- python /path/to/agent-context-mcp/servers/codex_context_mcp.py
claude mcp add hermes_context --scope user -- python /path/to/agent-context-mcp/servers/hermes_context_mcp.py
# (optional) read your own past Claude Code sessions:
claude mcp add claude_code_context --scope user -- python /path/to/agent-context-mcp/servers/claude_code_context_mcp.py
Codex (~/.codex/config.toml)
[mcp_servers.claude_code_context]
command = 'python'
args = ['/path/to/agent-context-mcp/servers/claude_code_context_mcp.py']
[mcp_servers.hermes_context]
command = 'python'
args = ['/path/to/agent-context-mcp/servers/hermes_context_mcp.py']
Hermes
hermes mcp add codex_context --command python --args /path/to/agent-context-mcp/servers/codex_context_mcp.py
hermes mcp add claude_code_context --command python --args /path/to/agent-context-mcp/servers/claude_code_context_mcp.py
Restart the agent's session after adding a server so its MCP cache picks it up.
Full mesh
Register all three servers in all three agents and every agent can read every agent (its own past sessions included):
| Agent | reads Hermes | reads Codex | reads Claude Code |
|---|---|---|---|
| Claude Code | ✅ | ✅ | ✅ |
| Codex | ✅ | ✅ | ✅ |
| Hermes | ✅ | ✅ | ✅ |
Tools
hermes_context:list_hermes_conversations,search_hermes_conversations,get_hermes_conversation_context,get_latest_hermes_conversation_contextcodex_context:codex_list_conversations,codex_search_conversations,codex_read_conversation,codex_read_latest_conversation,codex_export_context_bundleclaude_code_context:claude_code_list_conversations,claude_code_search_conversations,claude_code_read_conversation,claude_code_read_latest_conversation,claude_code_export_context_bundle
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.