Darwin MCP
Use your Darwin agent from Claude, ChatGPT, Cursor, and any compatible MCP client. The canonical server URL is https://mcp.darwin.so/mcp.
Shared Agent
One Darwin conversation across every client.
MCP clients reach the same user-scoped Darwin agent used by the web app, iOS app, and messaging channels.
Request
{
"days": 7,
"query": "What did we discuss last time, and what …"
}Response
{
"status": "ok",
"text": "I found the recent context from your Darwin c…"
}Request
{
"days": 7,
"query": "What did we discuss last time, and what …"
}Response
{
"status": "ok",
"text": "I found the recent context from your Darwin c…"
}I found the recent context from your Darwin conversation and continued from there. Your next best step is ready.
Darwin OAuth
No API key in the URL.
The MCP server starts the Darwin OAuth flow, verifies the signed user token, and forwards only the authenticated principal to Darwin API.
Request
{
"days": 7,
"query": "Connect Darwin to this client and show m…"
}Response
{
"status": "ok",
"text": "Connected with Darwin OAuth. I can now read a…"
}Request
{
"days": 7,
"query": "Connect Darwin to this client and show m…"
}Response
{
"status": "ok",
"text": "Connected with Darwin OAuth. I can now read a…"
}Connected with Darwin OAuth. I can now read and continue your shared Darwin agent conversation.
API Boundary
MCP transport outside, product logic inside API.
The MCP gateway owns protocol transport only. Conversation state, identity, agent runtime calls, and product data remain behind Darwin API.
Request
{
"days": 7,
"query": "Send this request to my Darwin agent and…"
}Response
{
"status": "ok",
"text": "The request was saved to your Darwin conversa…"
}Request
{
"days": 7,
"query": "Send this request to my Darwin agent and…"
}Response
{
"status": "ok",
"text": "The request was saved to your Darwin conversa…"
}The request was saved to your Darwin conversation and completed through the same agent runtime used by Darwin clients.
Canonical URL
Use mcp.darwin.so for MCP transport.
The public web page can explain MCP, but MCP-compatible clients should connect to the transport endpoint at https://mcp.darwin.so/mcp.
Request
{
"days": 7,
"query": "Add Darwin as a remote HTTP MCP server.…"
}Response
{
"status": "ok",
"text": "Use https://mcp.darwin.so/mcp. Darwin OAuth h…"
}Request
{
"days": 7,
"query": "Add Darwin as a remote HTTP MCP server.…"
}Response
{
"status": "ok",
"text": "Use https://mcp.darwin.so/mcp. Darwin OAuth h…"
}Use https://mcp.darwin.so/mcp. Darwin OAuth handles authentication when your client connects.
Get started in 3 minutes
Three steps to connect your AI client to your Darwin agent.
Sign in with Darwin
Darwin MCP uses OAuth. Sign in with the same Darwin account you use on the web or mobile app; no API key belongs in the MCP URL.
Sign in to DarwinAdd the MCP to your AI client
Open Claude's connector settings and paste these two fields. Claude will send you through Darwin OAuth the first time it connects.
All set — try it out
Start with a read-only prompt to confirm the connector can see your shared Darwin conversation.
Tools
The current Darwin MCP gateway exposes these tools, then forwards authenticated requests to Darwin API.
message_darwinSend a message to the authenticated user's Darwin agent.
get_darwin_conversationRead recent messages from the authenticated user's shared Darwin agent conversation.