Is this an official Close MCP server?

No. It is Memtro's MCP server with Memtro's Close connector behind it: the connector reads Close through its API with the credentials you connect on Dashboard → Connections, and Close publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

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 Close?

Not yet. Today every Close tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

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.

MCP server · CRM and sales

Close MCP server

Close in any MCP client, through Memtro: Close does not publish this server. Memtro's Close connector reads Close 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

Read-only Close CRM: search leads (accounts) with their contacts and opportunities, read a lead's recent calls, emails, notes and meetings, review the opportunity pipeline, and look up users, lead statuses and pipelines.

Reads

close_search_leadsSearch Close leads (companies/accounts) with their contacts and opportunities.
close_leadOne lead in full: contacts, every opportunity, and its most recent activities (calls, emails, notes, meetings, SMS…
close_opportunitiesOpportunities (deals) across leads: filter by status type (active/won/lost), owner, lead, won-since or updated-since date, newest-updated first…
close_activitiesActivities (calls, emails, notes, meetings, SMS, lead/opportunity status changes) for one lead or across the account in a date window, newest first…
close_usersUsers (sales reps), lead statuses and pipelines with their opportunity statuses: translate ids into names and learn the org's status labels for…

Connect it

First connect Close on Dashboard → Connections, then add Memtro to your client once. The Close tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer 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-..."
      }
    }
  }
}

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 Close 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

› What happened with Acme Corp last week?
› Which opportunities did we win in September and for how much?
› Summarise yesterday's calls and their outcomes
› Which Qualified leads have no activity in 30 days?
› What is in the Enterprise pipeline by status?

Questions

Is this an official Close MCP server?: No. It is Memtro's MCP server with Memtro's Close connector behind it: the connector reads Close through its API with the credentials you connect on Dashboard → Connections, and Close 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 Close?: Not yet. Today every Close tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
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.