Pipeline CRM MCP server
Pipeline CRM in any MCP client, through Memtro: Pipeline CRM does not publish this server. Memtro's Pipeline CRM connector reads Pipeline CRM through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Pipeline CRM: deals with stage, value, owner, company and people; people (leads and contacts) with position, company and status; companies; activities (notes) on a deal, person or company; tasks and events; and the account's stages, pipelines and categories. Can create and edit deals, people and companies, delete a deal or an activity, log an activity, comment on one, and add or complete a task or event, each only when asked.
Reads
pipelinecrm_list_dealsPipeline CRM deals: name, value and currency, stage, probability, owner, company, primary contact and people, expected close date, next task…pipelinecrm_get_dealOne Pipeline CRM deal by id with its most recent activities (notes): title, content, category, author and date.pipelinecrm_list_peoplePipeline CRM people (leads and contacts): name, type, work email, position, company, lead status, owner and dates.pipelinecrm_list_companiesPipeline CRM companies: name, website, city and country, owner, tags, description and dates.pipelinecrm_list_notesPipeline CRM activities (the API calls them notes) on a deal, person or company, newest first: title, content, category, author…pipelinecrm_list_calendar_entriesPipeline CRM tasks and events: name, kind, due date or start and end, whether complete, the deal, person or company it is on, owner and category.pipelinecrm_referencePipeline CRM lookup lists, ids and names only: deal_stages (with win percent and pipeline), deal_pipelines, deal_statuses, deal_loss_reasons…
Acts, when you ask
These change something in Pipeline CRM. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
pipelinecrm_create_dealCreate a Pipeline CRM deal.pipelinecrm_update_dealChange a Pipeline CRM deal.pipelinecrm_delete_dealDelete a Pipeline CRM deal.pipelinecrm_create_personCreate a Pipeline CRM person, a lead or a contact.pipelinecrm_update_personChange a Pipeline CRM person's name, work email, position, company, lead status, type (Lead to Contact converts them) or owner.pipelinecrm_create_companyCreate a Pipeline CRM company.pipelinecrm_create_noteLog an activity (a note) on a Pipeline CRM deal, person or company, as the token's user.pipelinecrm_delete_noteDelete a Pipeline CRM activity (note) and its comments.pipelinecrm_add_commentComment on a Pipeline CRM activity (note) as the token's user.pipelinecrm_create_calendar_entryAdd a task or an event in Pipeline CRM, optionally on a deal, person or company, owned by the token's user.pipelinecrm_complete_calendar_entryMark a Pipeline CRM task or event complete, or not complete again with complete false.
Connect it
First connect Pipeline CRM on Dashboard → Connections, then add Memtro to your client once. The Pipeline CRM tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Pipeline CRM connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which deals are expected to close this month?
- › What was the last activity on the Northwind deal?
- › Which leads have I not touched in two weeks?
- › What tasks are due for me tomorrow?
- › Log a note on the BigCo deal that pricing was agreed
Questions
- Is this an official Pipeline CRM MCP server?
- No. It is Memtro's MCP server with Memtro's Pipeline CRM connector behind it: the connector reads Pipeline CRM through its API with the credentials you connect on Dashboard → Connections, and Pipeline CRM publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Pipeline CRM?
- Only when you ask, and only what it has been granted: create a deal; change a deal's name, value, stage, probability, close date, company, people or owner (a stage or probability change can close the deal); delete a deal (permanent); create a person (lead or contact); change a person's name, email, position, company, status or owner; create a company; log an activity (note) on a deal, person or company; delete an activity (permanent); comment on an activity (users on its notify list are emailed); add a task or event to a deal, person or company; mark a task or event complete or not complete. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.