Skip to main content
The MCP server is in early access. The interface may change.
Adapt hosts a Model Context Protocol (MCP) server so external agents and tools can talk to your organization programmatically — not just through Slack and the web app. Point an MCP-capable client at Adapt, and it can run a full agent with all of your knowledge, integrations, and skills behind it.

​
Teach your agent

Already in Claude Code, Codex, Cursor, or another MCP client? Copy this prompt and paste it in — your agent will walk you through connecting Adapt and running your first query. Prefer to set it up by hand? The full steps are below.

​
What you can do

Once connected, you can address Adapt with @adapt from your client and put the same agent that runs in Slack and the web app to work — now alongside whatever you’re already doing in your editor or terminal. A few examples: Use your integrations
Draw on company knowledge
Use apps and the sandbox
Load up Claude or Codex with full context from an Adapt chat

​
Endpoint

The server uses the Streamable HTTP transport.

​
Authentication

Authenticate with your Adapt session token, sent as a Bearer credential:
To find your session token, open app.adapt.com while signed in, open your browser’s developer tools, and copy the value of the sessionToken cookie (Application > Cookies > app.adapt.com).
The sessionToken cookie can hold one of two values, and this header-based setup works with only one of them:
  • A 64-character hex string — valid for 7 days. This is the one to copy.
  • A value beginning with Fe26.2 — an encrypted session whose credential expires after a few minutes. The browser refreshes it automatically, but a header-only client can’t, so it stops working almost immediately.
Check the shape of the value before using it. If it starts with Fe26.2, sign in with Google or Apple and copy the new sessionToken — those sign-in methods issue the 64-character token.

​
Multiple organizations

If your account belongs to more than one organization, also send an X-Adapt-Org header with the organization ID you want to use:
Without it, the server returns a 400 because it can’t tell which organization to act in. A 401 means the token itself is missing or expired.

​
Setup

​
Claude Code

If you belong to multiple organizations, add the org header:

​
Codex

Codex has no mcp add command that can set request headers, so configure the server directly in ~/.codex/config.toml. Create the file if it doesn’t exist and add:
If you belong to multiple organizations, add the X-Adapt-Org header alongside it:
Codex reads config.toml at launch, so start or restart Codex to pick up the server. Verify it registered:
You should see transport: streamable_http, the URL, and http_headers: Authorization=***** (masked). Inside a Codex session, /mcp lists the server and its ask_adapt tool. This writes your token to config.toml in plaintext. It’s the 7-day token, so treat the file as a credential and refresh it when the token expires.

​
The ask_adapt tool

The server exposes one tool, ask_adapt, which runs an Adapt agent in your organization. Three ways to call it:
  • Start a conversation — pass message with no chat_id. Adapt creates a new chat, runs the agent, and returns the reply.
  • Continue a conversation — pass both message and chat_id to keep going in the same chat.
  • Read a conversation — pass only chat_id to return the full transcript.
Every reply is prefixed with chat_id: <id>. Save that value to continue or revisit the conversation later. Agent runs are asynchronous and can take some time on longer tasks. The tool waits for the reply and returns it when the run finishes.