Three tools and a filter set are enough for the question this exists to answer: what was done, where, and by which agent. The filters — project path, machine, source, time range — are what turn the answer into a specific session rather than a summary of everything.
UltraContext's MCP server over the Context API. It gives any MCP-compatible agent access to sessions other agents have already had, whether the CLI ingested them or an SDK wrote them.
- list_contexts — recent contexts, filtered by source, user, host, project path, session id, or a time window
- get_context_messages — every message in one context, fetched by its public id
- get_recent_activity — the 'what happened last?' shortcut, taking the latest context and returning its most recent messages
- Sessions from claude, codex and openclaw sitting in the same store
Node.js 22 or newer, and a Context API key in ~/.ultracontext/config.json — the same file the CLI writes, which the MCP server reads by itself. The CLI has to be running for sessions to be ingested. There is a hosted route as well: any Streamable HTTP client can talk to https://api.ultracontext.ai/mcp with the same Bearer token the REST API uses, and the standalone HTTP transport listens on port 3100 unless MCP_PORT says otherwise.
One command plus a key — npm install -g ultracontext, then supply credentials