Skip to main content
Glama
README.md
# copper-mcp

MCP server for the [Copper CRM](https://www.copper.com/) API. Search contacts, log activities, manage opportunities, and query companies.

## Tools

| Tool | Description |
|------|-------------|
| `search_people` | Search contacts by name, email, or phone |
| `get_person` | Get full contact details by ID |
| `create_person` | Create a new contact |
| `update_person` | Update contact fields |
| `search_companies` | Search companies by name |
| `list_activity_types` | List available activity types |
| `create_activity` | Log a meeting, call, or note against a contact/company |
| `list_activities` | Search activities with filters and resolved parent names |
| `list_opportunities` | Search deals/opportunities |

## Setup

1. Install dependencies:
   ```bash
   npm install
   ```

2. Copy `.env.example` to `.env` and fill in your credentials:
   ```bash
   cp .env.example .env
   ```

   Required environment variables:
   - `COPPER_API_KEY` - Your Copper API key
   - `COPPER_USER_EMAIL` - Your Copper account email
   - `COPPER_USER_ID` - Your Copper user ID

## Usage with Claude Code

Add to your Claude Code MCP config (`~/.claude.json`):

```json
{
  "mcpServers": {
    "copper-crm": {
      "command": "node",
      "args": ["/path/to/copper-mcp/server.js"],
      "env": {
        "COPPER_API_KEY": "your-api-key",
        "COPPER_USER_EMAIL": "your-email",
        "COPPER_USER_ID": "your-user-id"
      }
    }
  }
}
```

## License

MIT

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues