Copper CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COPPER_API_KEY | Yes | Your Copper API key. | |
| COPPER_USER_EMAIL | Yes | Email of the key's owner. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_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. |
| search_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. |
| search_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). |
| list_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. |
| get_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. |
| create_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. |
| log_activityA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.