Skip to main content
Exo speaks MCP over Streamable HTTP at https://api.get-exo.com/mcp/. Every client on this page talks to that one endpoint. What changes between them is how they authenticate and how much of the toolset they are allowed to see.

​
Pick your client

Two things decide your path: whether your client accepts a pasted API key, and whether it speaks OAuth.
Static keys work in Claude Code and Codex. They do not work in ChatGPT, which accepts OAuth or no auth for connectors and nothing else. The claude.ai app also uses OAuth rather than a pasted key.

​
Two ways in

Connecting a client gives an agent read and write access to your graph while you work. That is the live path. It is not how the graph gets its history.

Connect a client

Your agent reads your context during a session and writes back what it learns.

Bring data in

Load exports, documents, past coding sessions and repositories so there is something to read.
A brand new organization returns empty collections from every recall surface until content lands and the background cognition cycle runs. If you connect a client first and it finds nothing, that is the reason. See How a memory is made.

​
Bringing data in

Files and transcripts

ChatGPT and Claude exports, PDF, DOCX, Markdown, meeting transcripts.

Coding sessions

Backfill local Claude Code and Codex transcripts, then tail new ones.

GitHub

Install the app, sync repositories, keep them current.

​
Reference

MCP tool reference

What each tool does and the REST route behind it.

Read these docs from an agent

Add this site as an MCP server so your agent can look things up itself.