Skip to main content

Documentation Index

Fetch the complete documentation index at: https://modem.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Modem MCP Server lets MCP-compatible clients call the Modem Agent from outside the Modem dashboard. Use it when you want an external assistant to ask Modem about your customer feedback, topics, people, companies, and connected tools.
The Modem MCP Server is currently in beta. Access may be limited to enabled organizations while we expand availability.
This page is about connecting an external MCP client to Modem. To connect external MCP tool servers for the Modem Agent to use, see the MCP Servers page.

​
Server URL

Use this URL in your MCP client: 
https://mcp.modem.dev/mcp
The server uses Streamable HTTP and OAuth. You do not need to create or paste an API key.

​
What It Can Do

The server currently exposes invoke_modem_agent, which runs the Modem Agent with a natural-language prompt and returns the final answer to your MCP client.
Treat each MCP call as a self-contained prompt. Follow-up conversation continuity from the MCP client is not supported yet.

​
Prerequisites

  • A Modem account with access to the organization you want to use
  • Access to the Modem MCP Server beta for that organization
  • An MCP client that supports remote Streamable HTTP servers with OAuth
Client support changes quickly. The examples below cover common MCP clients with remote HTTP support. Your client may use slightly different labels for the same fields, and it must support OAuth for Modem’s server.

​
Set Up Your Client

Use the setup path for your MCP client. In every case, the server URL is: 
https://mcp.modem.dev/mcp

​
Claude Code

Claude Code can add remote HTTP MCP servers from the CLI. 
claude mcp add --transport http modem https://mcp.modem.dev/mcp
Then run /mcp inside Claude Code and complete the browser authorization flow.

​
Cursor

In Cursor, open Settings → Cursor Settings → Tools & MCP, then add a new MCP server. Cursor stores MCP configuration in an mcp.json file. 
{
    "mcpServers": {
        "modem": {
            "url": "https://mcp.modem.dev/mcp"
        }
    }
}
If Cursor asks for a transport type, choose Streamable HTTP.

​
VS Code and GitHub Copilot

VS Code stores MCP configuration in an mcp.json file, either in your user profile or in .vscode/mcp.json for a workspace. 
{
    "servers": {
        "modem": {
            "type": "http",
            "url": "https://mcp.modem.dev/mcp"
        }
    }
}
Use MCP: Add Server or MCP: Open User Configuration from the command palette if you prefer to edit through VS Code.

​
Windsurf

Windsurf stores MCP configuration in ~/.codeium/windsurf/mcp_config.json. For remote HTTP servers, use serverUrl. 
{
    "mcpServers": {
        "modem": {
            "serverUrl": "https://mcp.modem.dev/mcp"
        }
    }
}

​
Cline

In Cline, open the MCP Servers panel and add a remote server manually:
1

Open MCP Servers

Click the MCP Servers icon in the Cline panel.
2

Add a remote server

Open the remote server flow, then enter modem as the server name.
3

Enter the server URL

Use https://mcp.modem.dev/mcp as the full endpoint URL.
4

Choose the transport

Select Streamable HTTP.
5

Authenticate

If your Cline version supports OAuth for remote servers, complete the browser authorization flow.

​
Other MCP Clients

Use the client’s remote HTTP or Streamable HTTP setup flow. If it asks for fields, use:
FieldValue
Namemodem
URLhttps://mcp.modem.dev/mcp
TransportStreamable HTTP or HTTP
AuthenticationOAuth
Client-specific MCP docs:
ClientDocs
Claude CodeConnect Claude Code to tools via MCP
CursorCursor MCP documentation
VS CodeMCP configuration reference
WindsurfCascade MCP integration
ClineCline MCP documentation

​
Authorize Modem

Your MCP client should open a browser window for OAuth authorization the first time it connects. On the Modem consent screen:
  • Confirm the requesting client name.
  • Review the redirect destination.
  • Choose the Modem organization if your account belongs to more than one.
  • Approve the agent:invoke permission.
After authorization completes, your MCP client can call the Modem MCP tool.

​
Example Prompts

Use prompts that give the Modem Agent a complete task. The MCP server returns the final answer synchronously. Because each MCP call is self-contained, include the context the agent needs in the prompt instead of relying on a previous MCP exchange.

​
Security and Access

Modem authorizes the MCP client with OAuth. The access token is scoped to the Modem account and organization selected during consent. The current MCP permission is:
ScopeMeaning
agent:invokeRun the Modem Agent on your behalf.
The MCP server resolves the organization from the OAuth token claims, not from the URL. Keep the server URL as https://mcp.modem.dev/mcp.

​
Troubleshooting

  • Confirm the server URL is exactly https://mcp.modem.dev/mcp.
  • Restart the client or reload its MCP server list.
  • Make sure your client supports remote Streamable HTTP MCP servers with OAuth.
  • Sign in with the Modem account that belongs to the organization you selected.
  • Re-run the OAuth flow and approve the agent:invoke permission.
  • If your organization is not enabled for the beta, contact Modem support.
Each MCP call currently starts a separate Modem agent invocation. Include the necessary context in the prompt you send from your MCP client.
Remove or disconnect the Modem MCP server in your client, then authorize again and select the correct organization on the Modem consent screen.
https://mintcdn.com/modem-844d7a4a/Wr2r4IRr97lNQiQb/icons/bot-bolt.svg?fit=max&auto=format&n=Wr2r4IRr97lNQiQb&q=85&s=dda761a2f7042ebc27c668cc644df76c

The Modem Agent

Learn what the Modem Agent can query and do.
https://mintcdn.com/modem-844d7a4a/Wr2r4IRr97lNQiQb/icons/link.svg?fit=max&auto=format&n=Wr2r4IRr97lNQiQb&q=85&s=e774d33588635d44c6c935b78ed55f13

MCP Servers

Connect external MCP tool servers for the Modem Agent to use.