Copper MCP
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_ID | Yes | Your Copper user ID | |
| COPPER_USER_EMAIL | Yes | Your Copper account email |
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_peopleB | Search Copper contacts by name, email, or phone. Returns matching person records with IDs for use in create_activity. |
| get_personC | Get full details of a Copper contact by their ID. |
| create_personC | Create a new person (contact) in Copper CRM. |
| update_personB | Update an existing person (contact) in Copper CRM. Only include fields you want to change. The 'details' field is the 'About' section visible at the top of the contact page. |
| search_companiesC | Search Copper companies by name. Returns matching company records. |
| list_activity_typesA | List all available activity types in Copper (e.g., Note, Meeting, Phone Call). Returns activity_type_id values needed for create_activity. |
| create_activityA | Log an activity (meeting note, phone call, etc.) against a Copper person or company. Use list_activity_types first to get the correct activity_type_id. |
| list_opportunitiesB | Search Copper opportunities (deals). Optionally filter by company or person. Returns deal name, value, status, and pipeline stage. |
| list_activitiesA | Search Copper activities (meeting notes, calls, emails logged against contacts). Filter by parent record, activity type, or date range. Returns resolved parent names. Excludes system activities (assignee/status changes) by default. |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, create_activity, list_activities, and list_activity_types all handle activities but with specific roles (creation, searching, and type listing), while person/company/opportunity tools target different CRM entities. The descriptions clearly differentiate overlapping domains like search_people vs get_person.
All tools follow a consistent verb_noun naming pattern throughout, such as create_activity, list_activities, search_companies, and update_person. There are no deviations in style or convention, making the set predictable and easy to navigate for an agent.
With 9 tools, the count is well-scoped for a CRM server, covering core entities like people, companies, activities, and opportunities. Each tool earns its place by providing essential CRUD and search operations without redundancy or bloat.
The tool surface is largely complete for CRM operations, offering create, get, update, and search for people and activities, plus search for companies and opportunities. A minor gap exists in lacking update/delete for companies and opportunities, but agents can work around this with existing tools for basic workflows.