Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Copper to Claude Code

Make Claude log activities and update opportunities in Copper. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Copper to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Copper, you add a Copper MCP server: a small hosted service that exposes Copper's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Copper account. No API keys pasted into config files.

claude mcp add --transport http copper https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Copper once connected?

Full read-write Copper access lets Claude create and update leads, people, and companies, log calls and meetings against the right record, move an opportunity to its next stage, and keep custom fields current. The follow-up that used to mean tabbing back into the CRM happens where your pipeline already lives.

  • Create or update a lead, person, or company record
  • Log a call, meeting, or note as an activity on the right record
  • Update an opportunity's value, close date, or custom fields
  • Advance an opportunity to its next pipeline stage
  • Create a follow-up task and assign it to the right owner
  • Find every opportunity matching a query and propose batched updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Copper access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Copper API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Copper changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Copper connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Copper connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Copper account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Copper's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Copper?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Copper account it signs in with. Revoking access is one click in Copper.

More on the Copper connector

Copper connector for claude.aiSalesforce + Claude CodeHubSpot + Claude CodePipedrive + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us