Skip to main content
Glama
Copper CRM MCP Server

Copper CRM MCP Server

by OfirOhan

Copper CRM MCP Server

CI MCP License: MIT

A Model Context Protocol server for Copper, the CRM for Google Workspace. It lets Claude, Cursor, ChatGPT and other AI agents search contacts and companies, review the pipeline, move deals between stages, and log notes and tasks.

Unofficial. This is a community project and is not affiliated with Copper. It was built from Copper's public Developer API docs.

What you can ask your agent

  • "Give me a pipeline review: open deals closing this quarter, by stage, with total value."

  • "Which open deals haven't changed stage since September?"

  • "Move the Acme renewal to Proposal, set the close date to Nov 30, and add a note that I sent the revised quote."

  • "Who at Globex is in the CRM, and when did we last talk to them?"

  • "What tasks are overdue for me? Create a follow-up task for Dana for Friday."

  • "Show me the last 10 activities on the Initech deal."

Related MCP server: Copper CRM MCP Server

Tools

Tool

What it does

Writes?

get_account_info

Account, API user, and all users with IDs

No

search_people

Contacts by name, email, company, tags, owner, location, last contact

No

find_person_by_email

One contact by exact email

No

search_companies

Companies by name, tags, owner, location

No

list_pipelines

Pipelines with stage IDs, names and win probability

No

search_opportunities

Deals by status, pipeline, stage, owner, value, close date, staleness. Returns totals by status and stage

No

get_opportunity

One deal with all fields

No

create_opportunity

Create a deal

Yes

update_opportunity

Move stage, mark Won/Lost, change value, close date or owner

Yes

search_tasks

Tasks by owner, status, due date, deal

No

create_task

Create a task linked to a record

Yes

complete_task

Mark a task Completed

Yes

log_activity

Add a note (or call, meeting...) to a record

Yes

list_activities

Activity feed for a record or date range, or the activity types

No

The server does the translation an LLM would otherwise get wrong. It accepts ISO dates and converts them to Copper's unix-second timestamps (and M/D/YYYY close dates), maps Open/Won/Lost/Abandoned to Copper's status IDs, swaps stage IDs for stage names, and returns compact records instead of full API payloads (use raw: true when you want everything). Write tools carry MCP annotations, so clients can ask before running them.

Setup

  1. In Copper, go to Settings > API Keys and generate a key.

  2. Build it:

git clone https://github.com/OfirOhan/copper-mcp.git
cd copper-mcp && npm install && npm run build

Claude Desktop

Add this to claude_desktop_config.json:

{
  "mcpServers": {
    "copper": {
      "command": "node",
      "args": ["/absolute/path/to/copper-mcp/dist/index.js"],
      "env": { "COPPER_API_KEY": "...", "COPPER_USER_EMAIL": "you@company.com" }
    }
  }
}

Claude Code / Cursor / other MCP clients

claude mcp add copper -e COPPER_API_KEY=... -e COPPER_USER_EMAIL=you@company.com -- node /path/to/copper-mcp/dist/index.js

For Cursor and other clients, use the same command with the variables in the environment.

Variable

Default

Notes

COPPER_API_KEY

(required)

API key from Settings > API Keys

COPPER_USER_EMAIL

(required)

Email of the user who generated the key

COPPER_BASE_URL

https://api.copper.com/developer_api/v1

Override for testing

Development

npm install
npm test   # builds, runs unit tests and an end-to-end MCP stdio test against a fake Copper API

The tests run on Node 20, 22 and 24 in CI.

Author

Built by Ofir Ohana, an AI agents engineer. Issues and PRs are welcome.

License

MIT

Available Tools

14 tools
complete_taskComplete taskC
Idempotent

Mark a task as Completed.

Inputs: task_id (required).

create_opportunityCreate opportunityA

Create a new deal. Use list_pipelines for pipeline and stage IDs and get_account_info for user IDs.

Inputs: name (required), tags, status, details, +8 more.

create_taskCreate taskC

Create a task, optionally linked to a person, company, lead or opportunity.

Inputs: name (required), tags, details, due_date, +5 more.

find_person_by_emailFind person by emailA
Read-only

Look up one contact by exact email address. Returns the full person record.

Inputs: email (required).

get_account_infoAccount, me and usersA
Read-only

Get the Copper account, the API user, and all users with their IDs. Use the user IDs as assignee_id in other tools.

Inputs: no named parameters.

get_opportunityGet opportunityB
Read-only

Get one deal with all fields, including custom fields.

Inputs: opportunity_id (required).

list_activitiesList activitiesB
Read-only

Recent activity (notes, emails, calls, meetings, stage changes) for a record, or across the account in a date range. Set types=true to list activity types instead.

Inputs: since, types, until, page_size, +3 more.

list_pipelinesList pipelinesA
Read-only

List pipelines with their stages (id, name, win probability). Needed to move deals between stages.

Inputs: no named parameters.

log_activityLog note or activityA

Add a note (default) or another user activity type (call, meeting...) to a person, company, lead or opportunity. Use list_activities with types=true to see activity type IDs.

Inputs: details (required), parent_id (required), parent_type (required), activity_date, +1 more.

search_companiesSearch companiesC
Read-only

Search companies by name, tags, assignee or location.

Inputs: city, name, tags, country, +5 more.

search_opportunitiesSearch opportunities (deals)A
Read-only

Search deals by name, status, pipeline, stage, owner, company, value or close date. Returns totals by status and stage (count and value) and a compact list with stage names instead of IDs. Good for pipeline reviews and forecasts.

Inputs: raw, name, tags, sort_by, +14 more.

search_peopleSearch peopleB
Read-only

Search contacts (people) by name, email, company, tags, assignee or location. Returns a compact list.

Inputs: raw, city, name, tags, +10 more.

search_tasksSearch tasksB
Read-only

Search tasks by owner, status, due date or related deal. Good for 'what's overdue for me?'.

Inputs: sort_by, statuses, due_after, page_size, +5 more.

update_opportunityUpdate opportunityA
Idempotent

Update a deal: move it to another stage, mark it Won/Lost, change value, close date, owner or name. Only the fields you pass are changed.

Inputs: opportunity_id (required), name, tags, status, +10 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (search_opportunities vs get_opportunity vs create/update_opportunity are clearly separable). The only mild overlap is search_people vs find_person_by_email, since find_person_by_email is essentially a constrained lookup, but the descriptions clarify the difference (compact list vs full record).

    Naming Consistency5/5

    All 14 tools follow a consistent snake_case verb_noun pattern (search_people, get_opportunity, create_task, list_activities, log_activity). Verbs are used predictably for their action type across resources.

    Tool Count5/5

    14 tools is well within a sensible range and each earns its place across the CRM's core entities (people, companies, deals, tasks, activities, pipelines). No redundant or filler tools.

    Completeness3/5

    Coverage is strong for deals, tasks, and activities (create/search/get/update/complete), but there is no way to create or update people or companies, and no delete operations anywhere. These are notable gaps for a CRM surface and will force agents to work around missing write paths.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read and manage Copper CRM data, including searching people, companies, and opportunities, listing pipelines, and logging activities or creating tasks.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with a CRM covering companies, people, leads, deals, and more, with role checks, scoped agent keys, approval gates, and a shared audit trail.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and act on SmartAgent real estate CRM data, such as finding leads, creating tasks, moving deals through pipelines, looking up property listings, and leaving notes.
      MIT