Tommos MCP server
Tommos is a CRM whose AI agents, the tommos, take a B2B inquiry to a signed contract: Tommo SDR answers the inquiry and books the call, Tommo Closer sends the recap, the proposal and the follow-ups, Tommo Legal reads the client's contract against your positions.
This repository is the documentation of the Tommos MCP server. The server itself runs at https://app.tommos.ai/api/mcp; there is nothing to install or run on your side. Add one address to your MCP client, sign in once, and your agent works your Tommos workspace as you, with your role: contacts, deals, forms, booking pages, the cards that wait for a decision.
Add the server
Claude Code
claude mcp add --transport http tommos https://app.tommos.ai/api/mcp
Claude (web and desktop): Settings, Connectors, «Add custom connector», paste https://app.tommos.ai/api/mcp.
Cursor (.cursor/mcp.json or the global mcp.json):
{
"mcpServers": {
"tommos": { "url": "https://app.tommos.ai/api/mcp" }
}
}
Cline (cline_mcp_settings.json, or MCP Servers, Remote Servers, add by URL):
{
"mcpServers": {
"tommos": {
"type": "streamableHttp",
"url": "https://app.tommos.ai/api/mcp",
"disabled": false,
"autoApprove": []
}
}
}
VS Code (.vscode/mcp.json):
{
"servers": {
"tommos": { "type": "http", "url": "https://app.tommos.ai/api/mcp" }
}
}
Windsurf (mcp_config.json):
{
"mcpServers": {
"tommos": { "serverUrl": "https://app.tommos.ai/api/mcp" }
}
}
Any other client that speaks streamable HTTP takes the same URL as a remote server.
Sign in once
Your client opens app.tommos.ai in the browser. Sign in with Google on a work address on your company's own domain, and allow the agent. If your company has no workspace yet, you open one on the same page and connect in one step: you are its owner. One free workspace per company domain; 14 days of everything, no card.
The server registers OAuth clients dynamically (RFC 7591): the client needs no pre-shared client id or secret, token_endpoint_auth_method is none, and the grants are authorization_code and refresh_token.
An agent with no person behind it
The owner of the workspace issues an API key in Settings, with only the rights the agent needs, and can revoke it there at once. The agent sends it as a header:
Authorization: Bearer <your key>
A key can read a card and refuse it. Only a signed-in person can approve a card that sends something outside the company.
A first call
After the connection, call read_the_workspace_state (or where_the_work_stands). It returns the workspace, its plan and what the tommos are working on, so you know the sign-in worked and whose workspace you are in.
What the tools cover
Over 100 tools in seven groups. Every act is signed on the record, so the timeline always says who did it and how, and that it came through MCP.
A person stays in charge
- A card that sends something outside the company is approved only by a signed-in person, and the record says who. The owner can let a tommo send one kind of email on its own for a form, after it has approved that kind 12 times without edits.
- Money is a person's. The agent can start the 14 days and ask the owners to choose a plan; only an owner pays.
- Keys are issued per agent, with only the rights it needs, and revoked in Settings at once.
Plans
Book $299, Close $599, Sign $899 a month, one price per company, the agents and the model inside, no seats. 14 days of everything with no card, and a 30-day money-back guarantee on the first payment. Details: https://tommos.ai/pricing
Elsewhere
- The official MCP Registry:
ai.tommos/tommos - Glama, Smithery, mcpservers.org: search «Tommos»
- Questions: [email protected]