Skip to main content
Glama
Copper CRM MCP Server

Copper CRM MCP Server

by hasankhadra

Copper CRM MCP Server

An MCP server that lets an AI agent (Claude Desktop, or any MCP client) read your Copper CRM and run light pipeline hygiene — search deals, spot stale opportunities, log a note, and schedule a follow-up.

Unofficial. Built to show what an official Copper MCP server could look like. It's a focused, read-heavy demo — not a production integration.

Why it looks the way it does

  • Read-heavy by design. Six of the seven tools only read. Exactly one tool writes (log_activity), and even that only appends an activity — it can't edit or delete existing records. A deliberately small blast radius is the right security posture for letting an agent touch your CRM.

  • Descriptions written for an agent. Each tool says what it returns and when to reach for it, so the model chains them correctly (e.g. call list_pipelines to turn a stage name into the IDs the other tools need).

  • Clean errors, not stack traces. A bad key comes back as Copper API returned 401 — check COPPER_API_KEY, so the agent can explain the problem instead of choking on it.

Related MCP server: MCP Suite CRM

Install (3 steps)

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

Then add this block to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS), and restart Claude Desktop:

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

Get your API key from Copper under Settings → Integrations → API Keys. The COPPER_USER_EMAIL must be the email of the user who owns that key.

Tools

Tool

Reads / Writes

What it does

search_people

read

Find people by name or email.

search_companies

read

Find companies by name.

search_opportunities

read

List/filter deals by pipeline, stage, or assignee.

list_pipelines

read

Every pipeline and its stages — maps stage names → IDs.

get_opportunity

read

Full detail of one deal (custom fields, tags, contact).

create_task

write*

Schedule a follow-up task, optionally linked to a record.

log_activity

write

Append a note/call to a person, company, opportunity, or lead.

* create_task creates a new task record; it never modifies existing CRM data. log_activity is the only tool that writes onto an existing record.

Try it

Once it's wired into Claude Desktop, ask:

"Which deals in my main pipeline are closing this month and have had no activity in the last 2 weeks? Log a note on the top one reminding me to send pricing, and create a follow-up task for Friday."

The agent calls list_pipelines → search_opportunities → get_opportunity to triage, then log_activity + create_task to act.

Configuration

Read from the environment (never hardcoded):

Variable

Description

COPPER_API_KEY

Your Copper API key.

COPPER_USER_EMAIL

Email of the key's owner.

For local testing outside Claude Desktop, copy .env.example to .env and run COPPER_API_KEY=... COPPER_USER_EMAIL=... npm start.

Development

npm run build   # compile TypeScript → dist/
npm run dev     # tsc --watch
npm start       # run the built server on stdio

Layout: src/copperClient.ts is the single HTTP/auth/error layer; each tool lives in its own file under src/tools/; src/index.ts registers them and opens the stdio transport.


Built by Hasan Khadra — hk@hasankhadra.me · hasankhadra.me.

The official version ships with full OAuth 2.1, write coverage across the CRM, and a two-week fixed-scope delivery.

License

MIT

Available Tools

7 tools
create_taskCreate TaskA

Create a follow-up task in Copper, optionally linked to a person, company, or opportunity. Use this to schedule a reminder (e.g. 'send pricing on Friday'). Returns the created task. This tool creates a task record but does not modify any existing CRM data.

Inputs: name (required), details, due_date, related_resource.

get_opportunityGet OpportunityA

Fetch the full detail of a single opportunity (deal) by its id — including custom fields, tags, status, monetary value, close date, primary contact, and the last activity dates you need to spot stale deals. Use this after search_opportunities to drill into one deal.

Inputs: id (required).

list_pipelinesList PipelinesA

List every sales pipeline in Copper along with its ordered stages. Call this first when you need to map a human stage or pipeline name (e.g. 'Closing this month') to the numeric IDs that search_opportunities and get_opportunity use. Returns each pipeline's id and name, plus each stage's id, name, and win_probability. Takes no arguments.

Inputs: no named parameters.

log_activityLog Activity (write)A

Log a note or call activity onto a person, company, opportunity, or lead in Copper. This is the only tool that writes to the CRM — it APPENDS an activity (it never edits or deletes existing data). Use it to record a call summary or leave a reminder note on a record. Defaults to a 'Note' activity. Returns the created activity.

Inputs: parent (required), details (required), activity_type_id.

search_companiesSearch CompaniesA

Find companies (accounts) in Copper by name. Use this to resolve a company before filtering opportunities or logging an activity against it. Returns a list of matches, each with id, name, domain, and primary phone. If no name is given it returns the most recent companies.

Inputs: name, page_size.

search_opportunitiesSearch OpportunitiesA

List and filter opportunities (deals) in Copper. Filter by pipeline, stage, or assignee to triage a book of business. Returns each deal's id, name, monetary_value, pipeline_id, pipeline_stage_id, close_date, company_name, and assignee_id. It also returns date_last_contacted (the last call/meeting/email date) and interaction_count, so you can spot stale deals directly from this one call without fetching each opportunity. Stage and pipeline are returned as IDs — call list_pipelines to map them to names. Use get_opportunity for the full record (custom fields, tags, contacts).

Inputs: page_size, assignee_id, pipeline_id, pipeline_stage_id.

search_peopleSearch PeopleA

Find people (contacts) in Copper by name and/or email address. Use this to look up a contact before logging an activity or creating a task against them. Returns a list of matches, each with id, name, primary email, company_name, and title. If no filters are given it returns the most recent people.

Inputs: name, email, page_size.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (tasks, opportunities, pipelines, activities, companies, people). No overlap in functionality; agents can easily distinguish between searching, fetching, creating, and logging.

    Naming Consistency5/5

    All tool names use snake_case and follow a clear verb_noun pattern (e.g., create_task, search_opportunities, list_pipelines). The naming is consistent and predictable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a CRM focus. Each tool serves a distinct purpose, and the count falls comfortably within the typical 3-15 range.

    Completeness2/5

    The server covers search and read operations for people, companies, and opportunities, and allows creating tasks and logging activities. However, it lacks tools to create, update, or delete core CRM records (opportunities, companies, people), leaving significant lifecycle gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Exposes HubSpot CRM data and actions as tools for AI agents, enabling contact lookup, company search, contact creation, and activity logging via natural language.
      4
      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
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to work with Copper CRM data: search contacts and companies, review pipelines, move deals between stages, and log notes, activities and tasks. It handles date, status and stage translation so agents can query and update CRM records through natural language.
      14
      MIT