The MCP server is in beta. The interface may still change.
Endpoint
Client setup
- Claude Code
- Codex CLI
- Cursor
- VS Code
- Claude Desktop
/mcp, then choose Adapt to sign in. Use /mcp any time to check status or re-authenticate.Other clients
ChatGPT
ChatGPT
Go to Settings > Connectors > Add custom connector (you may need to enable developer mode). Name it Custom connectors are available on ChatGPT Pro, Business, and Enterprise.
Adapt, use the endpoint below, and complete the browser flow.Windsurf
Windsurf
Add to
~/.codeium/windsurf/mcp_config.json, then reload the MCP server list and complete the browser flow.Zed
Zed
Add to Zed’s A remote server with no
settings.json, or use Settings > AI > MCP Servers > Add Server > Add Remote Server. Complete the browser flow when prompted.Authorization header makes Zed run the standard MCP OAuth flow.Goose
Goose
Run
goose configure, choose Add Extension > Remote Extension (Streaming HTTP), enter the endpoint, and complete the browser flow.OpenCode
OpenCode
Add to
opencode.json:Factory
Factory
Add to
~/.factory/mcp.json:Any other MCP client
Any other MCP client
Configure a remote Streamable HTTP server pointing at the endpoint below. Clients that support OAuth discovery will find Adapt’s authorization server from it and open the consent flow.
Teach your agent
Rather have your agent do it? Copy this prompt and paste it into Claude Code, Codex, Cursor, or any other MCP client — it will walk you through the setup above and run your first query.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
Authentication
Adapt serves OAuth protected-resource metadata at the endpoint, so MCP clients discover the authorization server and run the sign-in flow themselves.- Your client opens a browser window the first time it connects. Approve the sign-in and you’re done.
- Access tokens are short-lived (5 minutes) and your client refreshes them silently. Your session stays valid until 30 days of inactivity.
- Your organization comes from the token. Sign in with the organization you want to work in.
Session-token authentication, used during early access, is no longer accepted. If you connected before beta, see Reconnecting an early-access setup.
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
messagewith nochat_id. Adapt creates a new chat, runs the agent, and returns the reply. - Continue a conversation — pass both
messageandchat_idto keep going in the same chat. - Read a conversation — pass only
chat_idto return the full transcript.
chat_id: <id>. Save that value to continue or revisit the conversation later.
Long-running requests
Most MCP clients time out a tool call after 60 seconds, and plenty of Adapt work takes longer. Rather than hold the connection open,ask_adapt hands the run back to you:
1
The tool waits up to 45 seconds
Most requests finish inside that window and return normally.
2
Still going? You get a handle
The tool returns the
chat_id and status: working.3
Poll that chat_id
Call
ask_adapt again with only the chat_id — no message — at least 30 seconds later. Keep polling until the response no longer says working.status: failed with the transcript intact.
Permissions
The agent acts as you. It runs in the organization you signed in with and uses that organization’s integrations, knowledge, and skills, under your membership. Anything your organization restricts through policies applies to MCP the same way it applies in Slack and the web app — connecting over MCP does not widen what you can reach.Troubleshooting
The Adapt tools don't appear in my client
The Adapt tools don't appear in my client
Most MCP clients only load servers at startup. Restart the client, or open a new chat, and check again. In Claude Code and Codex,
/mcp lists the registered servers and their tools.Codex: MCP startup interrupted, the following servers were not initialized
Codex: MCP startup interrupted, the following servers were not initialized
Run
codex mcp get adapt from the project you expect it in. If you configured it per-project, confirm the repository is trusted — Codex only loads project config for trusted projects — or move the server to user-global config instead. Then run codex mcp login adapt, complete the browser flow, and restart Codex.403 Access denied
403 Access denied
Authentication worked, but the signed-in account isn’t an active, email-verified member of that organization. Verify your email, or ask an admin to confirm your membership.
429 Too Many Requests
429 Too Many Requests
The endpoint allows 300 requests per minute per IP. Polling a long-running run every 30 seconds, as instructed, stays well inside that.
Reconnecting an early-access setup
Early access authenticated with your Adapt session token as a Bearer credential. Configurations that still pass that header stop working. Remove the server and add it back without the header. Claude Code:http_headers line (and the X-Adapt-Org header, if present) from the [mcp_servers.adapt] block in ~/.codex/config.toml, leaving just the URL, then run codex mcp login adapt.