Copper logoMCP server · CRM and sales

Copper MCP server

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

Copper CRM: pipelines and stages, opportunities by pipeline, stage, status and owner with values, people and companies, leads, a record's activities and open tasks; can also add a note, create or update opportunities, tasks and people, create leads and companies, convert a lead, and delete an opportunity, task or person, when you ask.

Reads

  • copper_pipelinesCopper's pipelines with their stages (id, name, win probability), the account's lead statuses, activity types and users (id, name, email).
  • copper_opportunitiesOpportunities (deals) in Copper, most recently modified first: name, company, primary contact, pipeline and stage, status (open, won, lost…
  • copper_peoplePeople (contacts) in Copper: name, title, company, emails, phones, location, owner, tags, interaction count and when last contacted.
  • copper_companiesCompanies in Copper: name, email domain, phones, websites, location, owner, tags, interaction count and when last contacted.
  • copper_leadsLeads in Copper (unqualified prospects, before they become a person and opportunity): name, title, company, email, status, value, owner…
  • copper_activitiesActivities logged in Copper — notes, calls, meetings, emails, stage and status changes — for one record (a person, company, opportunity, lead…
  • copper_tasksTasks in Copper, soonest due first: name, status (Open or Completed), priority, due and reminder dates, assignee and the record it relates to.
  • copper_recordOne Copper record in full by type and id — a person, company, opportunity or lead — with its ten most recent activities.

Acts, when you ask

These change something in Copper. 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.

  • copper_add_noteAdds a note to a Copper person, company, opportunity or lead, where it appears in that record's activity feed under the key's user.
  • copper_create_opportunityCreates an opportunity (deal) in Copper under the key's user, visible to everyone who can see the pipeline.
  • copper_update_opportunityChanges a Copper opportunity: name, stage (by name or id), status (Open, Won, Lost, Abandoned, with a loss reason id when lost), value…
  • copper_create_taskCreates a task in Copper, optionally on a person, company, opportunity, lead or project, with an assignee (Copper's default, the key's user…
  • copper_update_taskUpdates a Copper task: name, assignee, due or reminder date, priority, details, or status (Completed closes it, Open reopens it).
  • copper_create_personCreates a person (contact) in Copper with a name and, optionally, email, phone, title, company id, owner and details.
  • copper_update_personUpdates a Copper person: name, title, details, owner, or their emails or phone numbers (each list given replaces the existing one…
  • copper_create_leadCreates a lead in Copper with a name and, optionally, email, phone, company name, title, expected value, owner and details.
  • copper_convert_leadConverts a Copper lead into a person, optionally placing them at a company (an existing company id, or a name…
  • copper_create_companyCreates a company in Copper with a name and, optionally, email domain, phone, address, primary contact id, owner and details.
  • copper_delete_opportunityDeletes an opportunity in Copper by id.
  • copper_delete_taskDeletes a task in Copper by id.
  • copper_delete_personDeletes a person (contact) in Copper by id.

Connect it

First connect Copper on Dashboard → Connections, then add Memtro to your client once. The Copper 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 Copper 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 opportunities in the Sales pipeline are at Proposal and who owns them?
  • › What did we win in October and what was it worth?
  • › What happened with Northwind Traders in the last two weeks?
  • › Mark the Bluefin renewal as Won
  • › Add a note to the Bluefin renewal opportunity: they want the contract by 20 November

Questions

Is this an official Copper MCP server?
No. It is Memtro's MCP server with Memtro's Copper connector behind it: the connector reads Copper through its API with the credentials you connect on Dashboard → Connections, and Copper 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 Copper?
Only when you ask, and only what it has been granted: add a note to a person, company, opportunity or lead; create an opportunity, or change its stage, status, value, owner or details; create a task, or update or complete one; create a person, or update their name, title, emails, phones or owner; create a lead or a company; convert a lead into a person, with a company and an opportunity if asked (the lead is removed); delete an opportunity, task or person permanently. 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.

Other MCP servers · CRM and sales

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time