The Compound MCP server lets an AI app that supports the Model Context Protocol (MCP) hand finance work to your Compound agents and get back Excel models, PowerPoint decks and Word memos with every figure cited to its source. It works with Claude (claude.ai, Claude Desktop and Claude Code), Cursor, ChatGPT, Microsoft 365 Copilot and other MCP clients.
The server address is:
https://ws.getcompound.ai/mcpThere is nothing to install. You add the URL to your client and sign in to Compound in your browser. The client then works with the same agents, tasks and files you see at getcompound.ai, with the same permissions you have there.
Set it up
Add the server to your client
In Claude Code, run:
claude mcp add --transport http compound https://ws.getcompound.ai/mcpIn claude.ai or Claude Desktop, open Settings, go to Connectors, click Add custom connector and enter https://ws.getcompound.ai/mcp.
In ChatGPT, add a custom connector with the same URL. ChatGPT lists custom connectors under Settings, then Apps, once developer mode is on.
In Cursor and other MCP clients, add the server to the client’s MCP configuration:
{
"mcpServers": {
"compound": {
"url": "https://ws.getcompound.ai/mcp"
}
}
}
The server uses the Streamable HTTP transport. Microsoft 365 Copilot is set up by an administrator; see Microsoft 365 Copilot below.
Sign in and approve
Your client opens a browser window where you sign in to Compound, the same way you sign in to the web app. In Claude Code, start this by typing /mcp and choosing compound; other clients ask when you first use the server.
Compound then shows a consent page that names the app asking for access and where the sign-in goes. Claude and ChatGPT show as a Verified app. Any other app shows as “An unverified app that calls itself …” or as an app from the web address it came from; allow it only if you just added it. When the sign-in goes to a program on your computer, as it does for Claude Code, the page warns that any program can claim to be that app; allow it only if you just started signing in from it. After you click Allow, the client has access and renews it on its own.
Ask in plain English
Mention Compound in your request:
- “Use Compound to build a comps sheet for the five largest US semiconductor companies.”
- “Ask my Compound agent for a one-page summary of NVDA’s latest earnings call.”
- “Check whether my Compound task on Project Falcon is done and give me the link to the model.”
Name the agent to use, such as Frankie, or ask the client to list your agents. Long work runs as a Compound task, so it keeps running if you close the client, and the work and its files also show up at getcompound.ai.
What your client can do
The server’s tools are the operations of the Compound API. The server lists the most used ones as tools and lets your client load the others by group when it needs them, which keeps its tool list short. Through them, your client can:
- Create agents and projects, change their settings, and share agents with teammates.
- Send an agent messages and read its replies, and accept or decline the changes it proposes.
- Follow the tasks an agent works on, and pause, resume or archive them.
- List, search, copy, rename and delete an agent’s files, read and add comments on them, and get download links for the files the agent produces.
- Set up schedules that run an agent on a recurring basis.
- Look up companies, their financials, events and news, and choose the companies an agent watches. Analyst estimates need FactSet among your data sources.
- Read your credits and usage.
A few operations are not tools: the live event stream, exporting a file to PDF, opening a file in the Excel or PowerPoint desktop app, signing PDFs and the billing portal. Do those in the web app.
Every call runs as you. The client sees only the agents and files you can open in Compound, and the work it starts uses your credits, as it would in the web app.
Access, sign-out and security
- The client’s access lasts an hour at a time and renews on its own. It can no longer renew 90 days after you approved it, or after 30 days in which it was not used. Then the client asks you to sign in again.
- Signing out of Compound in the browser you approved from ends the client’s access too.
- If your team requires two-factor authentication or limits how long a sign-in lasts, the same rules apply to MCP clients. A client counts from the web sign-in that approved it, so it ends when that sign-in ends. See Two-factor authentication and sign-in expiry.
Disconnect a client
Open Settings > Personal > Account. Under Apps with access to your account, find the client and click Revoke. The client loses access right away. Removing the server from the client also stops that client from using Compound. To use it again, connect it again from the client.
If your organization has a Compound API key (it starts with cpd_ and is issued by Compound), a client can send it instead of signing in. Calls then run as your organization’s API account, not as you: the client sees the agents and files that account owns. In Claude Code: claude mcp add --transport http compound https://ws.getcompound.ai/mcp --header "Authorization: Bearer cpd_..."
Microsoft 365 Copilot
An administrator connects Compound to Microsoft 365 Copilot once for the organization. You need the Global Administrator or AI Administrator role in Microsoft 365, and each person who uses the connector needs a Microsoft 365 Copilot license and a Compound account.
Get a client ID and secret
Copilot signs in to Compound with a client ID and a client secret. Email support@getcompound.ai and we send you a pair, or register a client yourself with Compound’s client registration endpoint:
curl -X POST https://ws.getcompound.ai/oauth/register \
-H "Content-Type: application/json" \
-d '{
"client_name": "Microsoft 365 Copilot",
"redirect_uris": ["https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect"],
"token_endpoint_auth_method": "client_secret_post"
}'
The response contains client_id and client_secret. The secret is shown only in this response, so store it somewhere safe. Compound deletes a client registration after 30 days in which it signed no one in; if that happens, register again and update the portal.
Register the client in the Teams Developer Portal
In the Teams Developer Portal, open Tools, then OAuth client registration, and create a registration with these values:
| Field | Value |
|---|---|
| Client ID | the client_id from step 1 |
| Client secret | the client_secret from step 1 |
| Authorization endpoint | https://ws.getcompound.ai/oauth/authorize |
| Token endpoint | https://ws.getcompound.ai/oauth/token |
| Refresh endpoint | https://ws.getcompound.ai/oauth/token |
| Scopes | compound offline_access |
| PKCE | On |
The registration’s redirect URI is https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect, the address registered in step 1. Copy the OAuth client registration ID the portal shows.
Add the connector in the Microsoft 365 admin center
In the Microsoft 365 admin center, open Copilot, then Connectors, and choose Create a new connector, then Connect to MCP server. Enter https://ws.getcompound.ai/mcp as the base URL and the OAuth client registration ID from step 2, then choose who can use the connector.
People sign in on first use
The first time someone uses Compound in Copilot, Copilot opens the Compound sign-in. Compound’s consent page shows the connector as an unverified app with the client_name you registered, because every Teams and Copilot app returns to the same Microsoft address. The person approves it once. Each person’s access then follows the rules in Access, sign-out and security above.
MCP server or Compound CLI?
| Compound MCP server | Compound CLI | |
|---|---|---|
| Setup | Add a URL; nothing to install | Your agent installs a command-line tool and a skill |
| Works in | Any MCP client, including Claude, Cursor, ChatGPT and Microsoft 365 Copilot | Terminal agents: Claude Code, Codex, OpenClaw |
| Sign-in | In the browser, from the client | compound login, then paste a code |
| Best for | Using Compound from a chat app, an editor or Copilot | Uploading local folders and data rooms, and scripting work from a terminal |
See Compound CLI to set up the CLI.
What to read next
- Compound for developers and the API reference: the API the MCP server’s tools come from.
- Tasks and the chat: how tasks run and how to answer the agent’s questions.
- Agents and projects: create agents and choose what each one can do.