---
title: "Copper MCP server for AI agents - actionlake"
description: "Give Claude 89 Copper actions through one MCP server: config, leads, opportunities, people. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/copper
updated: 2026-09-21
---

Connectors · CRM & sales

# Copper MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Copper and the rest of your systems. It gives your agent 89 Copper actions (44 reads, 33 writes and 12 that wait for a confirmation) and holds the Copper credential itself, so the agent never does. It paces Copper's limits and records every call.

[Connect Copper free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "copper.account.get",
  intent: "check which Copper account is connected"
}
# Get the Copper account · read · 1 upstream call
```

- 89 actions in one signed file
- 44 read look, never change
- 33 write create and update
- 12 wait for a yes destructive, confirmed first

Set up

## Connect Copper in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Copper.
   Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `api_key` Copper API key (System settings > Integrations > API Keys)
   - `user_email` Email address of the Copper user who generated the API key
   ```
   account { op: "connections.requirements", service: "copper" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "copper.account.get" }
   # get the copper account · read · 1 upstream call
   check { action: "copper.people.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Copper at a glance

**Sign-in**

Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`api_key` `user_email`

**Limits we pace to**

180 calls a minute, per connection

**API covered**

Copper CRM API v1`api.copper.com/developer_api/v1`

**Built from**

Copper's documentation, read 20 September 2026[developer.copper.com](https://developer.copper.com/) [developer.copper.com](https://developer.copper.com/download/copper_postman_collection.json)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

43 of 44 reads, for up to an hour; a write clears what it affects

**Ready-made plans**

8 in the store

**Shared entities**

8, so ask can line Copper up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Copper.

89 actions in 13 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **44** read look, never change
- **33** write create and update
- **12** destructive wait for a confirmation

1. ### Config
   14
   7 read · 5 write · 2 destructive
   List Copper tags · List Copper connect-field links · List Copper custom activity types · List Copper custom field definitions
2. ### Leads
   12
   5 read · 6 write · 1 destructive
   Search Copper leads · Create a Copper lead · Get a Copper lead · Update a Copper lead
3. ### Opportunities
   10
   6 read · 3 write · 1 destructive
   Search Copper opportunities · Create a Copper opportunity · Get a Copper opportunity · Update a Copper opportunity
4. ### People
   10
   5 read · 4 write · 1 destructive
   Search Copper people · Create a Copper person · Get a Copper person · Update a Copper person
5. ### Companies
   8
   3 read · 4 write · 1 destructive
   Search Copper companies · Create a Copper company · Get a Copper company · Update a Copper company
6. ### Activities
   7
   3 read · 3 write · 1 destructive
   Search Copper activities · Log a Copper activity · Get a Copper activity · Update a Copper activity
7. ### Files
   5
   3 read · 1 write · 1 destructive
   List files attached to a Copper record · Get an attached file's metadata · Get a signed S3 upload URL for a Copper record · Delete a file attached to a Copper record
8. ### Projects
   5
   2 read · 2 write · 1 destructive
   Create a Copper project · Search Copper projects · Get a Copper project · Update a Copper project

**5 more areas · 18 actions**

- Tasks **5**
- Webhooks **5**
- Related **4**
- Users **3**
- Account **1**

Top actions

## The Copper API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 66 of Copper's 66 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `copper.people.search` Search Copper people | List or filter people — every filter is optional; with none you get all people sorted by `sort_by`. Copper pages with `page_number` and `page_size` inside the… | read | `crm.contact.search` 46 connectors |
| `copper.companies.search` Search Copper companies | List or filter companies — every filter is optional; with none you get all companies sorted by `sort_by`. Copper pages with `page_number` and `page_size`… | read | `crm.company.search` 36 connectors |
| `copper.people.create` Create a Copper person | Create a new person. | write | `crm.contact.create` 161 connectors |
| `copper.companies.create` Create a Copper company | Create a new company. | write | `crm.company.create` 142 connectors |
| `copper.opportunities.search` Search Copper opportunities | List or filter opportunities — every filter is optional; with none you get all opportunities sorted by `sort_by`. Copper pages with `page_number` and… | read | `crm.deal.search` 9 connectors |
| `copper.opportunities.create` Create a Copper opportunity | Create a new opportunity. | write | `crm.deal.create` 43 connectors |
| `copper.tasks.search` Search Copper tasks | List or filter tasks — every filter is optional; with none you get all tasks sorted by `sort_by`. Copper pages with `page_number` and `page_size` inside the… | read | `work.task.search` 26 connectors |
| `copper.leads.search` Search Copper leads | List or filter leads — every filter is optional; with none you get all leads sorted by `sort_by`. Copper pages with `page_number` and `page_size` inside the… | read | `crm.lead.search` 6 connectors |
| `copper.people.delete` Delete a Copper person | Delete one person by id. | destructive | `crm.contact.delete` 147 connectors |
| `copper.tasks.create` Create a Copper task | Create a new task. | write | `work.task.create` 127 connectors |
| `copper.projects.create` Create a Copper project | Create a new project. | write | `work.project.create` 102 connectors |
| `copper.leads.create` Create a Copper lead | Create a new lead. | write | `crm.lead.create` 24 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Copper actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Copper deals are due to close this month, and what are they worth in total?
   calls `copper.opportunities.search`
2. Plan write
   Convert a qualified lead into a person, company and opportunity in Copper. Ask me before anything is sent or changed.
   calls `copper.leads.get` `copper.lead_activities.list` `copper.pipeline_stages.list` `copper.leads.convert` `copper.opportunities.get` +1 more
3. Plan read
   Pull a full activity digest for one company account in Copper.
   calls `copper.companies.get` `copper.company_activities.list` `copper.related_items.list` `copper.files.list` `copper.opportunities.search`
4. Write write
   Create a Copper person in Copper. Show me exactly what you will send before you save it.
   calls `copper.people.create`
5. Across systems read
   Which Copper companies have invoices in ConnectWise PSA, and how many each?
   calls `copper.companies.search` `connectwise_manage.invoices.list`

Across your systems

## Copper, joined to the rest of your business.

One `ask` fetches from Copper and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- Which Copper companies have invoices in ConnectWise PSA, and how many each?
  `copper.companies.search` + `connectwise_manage.invoices.list`, on `crm.company` · [ConnectWise PSA](https://actionlake.com/connectors/connectwise-psa)
- Which Copper companies have invoices in NetSuite, and how many each?
  `copper.companies.search` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `identity.user` **517** `crm.company` **227** `crm.contact` **192** `work.project` **116** `work.task` **105** `crm.deal` **43** `crm.lead` **28** `crm.activity` **10**

ask

```
ask {
  intent: "which Copper companies have invoices in ConnectWise PSA, and how many each",
  steps: [
    { action: "copper.companies.search", as: "co", input: {}, limit: 100, max_pages: 5 },
    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "co",
        right: "inv",
        on: "crm.company",
        group_by: "co.name",
        select: ["co.name", "count(inv.id) as invoices"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

The plan store

## Ready-made plans for Copper.

8 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

1. ### Pull a full activity digest for one company account
   Use it when Someone needs a complete history of one account before a meeting, renewal or escalation.
   **Effect**
   read
   **Steps**
   5
   **Needs**
   company id
   **Install**
   `copper-account-activity-digest`
2. ### Report open opportunities against pipeline stages and loss reasons
   Use it when Someone asks for a pipeline review or wants to know what is open and how it is distributed across stages.
   **Effect**
   read
   **Steps**
   5 · loops
   **Install**
   `copper-pipeline-health-report`
3. ### Find overdue tasks for an owner and log a chase note on each
   Use it when A rep's task list has slipped and each overdue item should be chased and noted in the CRM.
   **Effect**
   write
   **Steps**
   3 · loops
   **Install**
   `copper-overdue-task-chase`
4. ### Create a lead, tag its source and log the intake activity
   Use it when A new inbound lead needs to be entered in Copper with its source recorded and an intake note attached.
   **Effect**
   write
   **Steps**
   5
   **Needs**
   name
   **Install**
   `copper-lead-intake-and-assign`
5. ### Import a batch of leads after a human checks the mapping
   Use it when A list of leads from a campaign or event needs loading into Copper in one go.
   A person decides Import _number of leads_ leads into Copper.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   leads
   **Install**
   `copper-bulk-lead-import`
6. ### Register a Copper webhook and confirm it is live
   Use it when A new integration endpoint needs a Copper webhook created and verified.
   A person decides Send Copper _type_/_event_ events to _target_.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   target, type and event
   **Install**
   `copper-webhook-provisioning-check`
7. ### Convert a qualified lead into a person, company and opportunity
   Use it when A lead has been qualified and should become a real opportunity with its person and company records.
   A person decides Convert lead _name_ into a person, company and opportunity. This cannot be undone.
   **Effect**
   write
   **Steps**
   7
   **Needs**
   lead id
   **Install**
   `copper-convert-lead-to-opportunity`
8. ### Review untouched leads and delete the ones nobody wants
   Use it when The lead list has filled with dead inbound records and someone wants them reviewed and purged.
   A person decides Permanently delete _number of items_ Copper leads with no interaction in the last _quiet days_ days. This cannot be undone.
   **Effect**
   destructive
   **Steps**
   5 · loops
   **Needs**
   quiet days
   **Install**
   `copper-stale-lead-sweep`

install a plan

```
account { op: "plans.install", slug: "copper-account-activity-digest" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Copper

## Destructive actions wait for a yes.

12 Copper actions are destructive. These are all of them:

- Delete a Copper person `copper.people.delete`
- Delete a Copper company `copper.companies.delete`
- Delete a Copper opportunity `copper.opportunities.delete`
- Delete a Copper task `copper.tasks.delete`
- Delete a Copper project `copper.projects.delete`
- Delete a Copper lead `copper.leads.delete`
- Delete a Copper activity `copper.activities.delete`
- Remove a relationship between Copper records `copper.related_items.delete`
- Delete a Copper webhook subscription `copper.webhooks.delete`
- Delete a Copper connect-field link `copper.related_links.delete`
- Delete a Copper custom field definition `copper.custom_field_definitions.delete`
- Delete a file attached to a Copper record `copper.files.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do copper.people.delete confirm_policy: **human**

Delete a Copper person?

**intent:** the user asked me to delete a Copper person

run suspended · waiting for a named person · key _copper-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "copper-agent",
  allowed_actions: ["copper.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "copper.people.delete", approver: "lead@example.com" },
    { match: "copper.companies.delete", approver: "lead@example.com" },
    { match: "copper.opportunities.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Copper only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Copper costs on actionlake.

Every Copper action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Copper refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 89 Copper actions
- 89 actions page each page of a long list is one call
- 43 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Copper action.

89 actions by area: the id your agent calls, what it does, and its effect.

**Config 14**

- `copper.custom_activity_types.create` Create a Copper custom activity type write
- `copper.custom_activity_types.get` Get a Copper custom activity type read
- `copper.custom_activity_types.list` List Copper custom activity types read
- `copper.custom_activity_types.update` Update a Copper custom activity type write
- `copper.custom_field_definitions.create` Create a Copper custom field definition write
- `copper.custom_field_definitions.delete` Delete a Copper custom field definition destructive
- `copper.custom_field_definitions.get` Get a Copper custom field definition read
- `copper.custom_field_definitions.list` List Copper custom field definitions read
- `copper.custom_field_definitions.update` Update a Copper custom field definition write
- `copper.field_layouts.get` Get a Copper entity's field layout read
- `copper.related_links.create` Create a Copper connect-field link write
- `copper.related_links.delete` Delete a Copper connect-field link destructive
- `copper.related_links.list` List Copper connect-field links read
- `copper.tags.list` List Copper tags read

**Leads 12**

- `copper.customer_sources.list` List Copper customer sources read
- `copper.lead_activities.list` List activities on a Copper lead read
- `copper.lead_statuses.list` List Copper lead statuses read
- `copper.leads.bulk_create` Bulk create Copper leads write
- `copper.leads.bulk_update` Bulk update Copper leads write
- `copper.leads.convert` Convert a Copper lead write
- `copper.leads.create` Create a Copper lead write
- `copper.leads.delete` Delete a Copper lead destructive
- `copper.leads.get` Get a Copper lead read
- `copper.leads.search` Search Copper leads read
- `copper.leads.update` Update a Copper lead write
- `copper.leads.upsert` Upsert a Copper lead write

**Opportunities 10**

- `copper.loss_reasons.list` List Copper loss reasons read
- `copper.opportunities.bulk_create` Bulk create Copper opportunities write
- `copper.opportunities.create` Create a Copper opportunity write
- `copper.opportunities.delete` Delete a Copper opportunity destructive
- `copper.opportunities.get` Get a Copper opportunity read
- `copper.opportunities.search` Search Copper opportunities read
- `copper.opportunities.update` Update a Copper opportunity write
- `copper.pipeline_stages.list` List Copper pipeline stages read
- `copper.pipeline_stages.list_by_pipeline` List stages of one Copper pipeline read
- `copper.pipelines.list` List Copper pipelines read

**People 10**

- `copper.contact_types.list` List Copper contact types read
- `copper.people.bulk_create` Bulk create Copper people write
- `copper.people.bulk_update` Bulk update Copper people write
- `copper.people.create` Create a Copper person write
- `copper.people.delete` Delete a Copper person destructive
- `copper.people.get` Get a Copper person read
- `copper.people.get_by_email` Get a Copper person by email read
- `copper.people.search` Search Copper people read
- `copper.people.update` Update a Copper person write
- `copper.person_activities.list` List activities on a Copper person read

**Companies 8**

- `copper.companies.bulk_create` Bulk create Copper companies write
- `copper.companies.bulk_update` Bulk update Copper companies write
- `copper.companies.create` Create a Copper company write
- `copper.companies.delete` Delete a Copper company destructive
- `copper.companies.get` Get a Copper company read
- `copper.companies.search` Search Copper companies read
- `copper.companies.update` Update a Copper company write
- `copper.company_activities.list` List activities on a Copper company read

**Activities 7**

- `copper.activities.bulk_create` Bulk log Copper activities write
- `copper.activities.create` Log a Copper activity write
- `copper.activities.delete` Delete a Copper activity destructive
- `copper.activities.get` Get a Copper activity read
- `copper.activities.query` Search Copper activities read
- `copper.activities.update` Update a Copper activity write
- `copper.activity_types.list` List Copper activity types read

**Files 5**

- `copper.files.attach` Attach an uploaded file to a Copper record write
- `copper.files.delete` Delete a file attached to a Copper record destructive
- `copper.files.get` Get an attached file's metadata read
- `copper.files.get_upload_url` Get a signed S3 upload URL for a Copper record read
- `copper.files.list` List files attached to a Copper record read

**Projects 5**

- `copper.projects.create` Create a Copper project write
- `copper.projects.delete` Delete a Copper project destructive
- `copper.projects.get` Get a Copper project read
- `copper.projects.search` Search Copper projects read
- `copper.projects.update` Update a Copper project write

**Tasks 5**

- `copper.tasks.create` Create a Copper task write
- `copper.tasks.delete` Delete a Copper task destructive
- `copper.tasks.get` Get a Copper task read
- `copper.tasks.search` Search Copper tasks read
- `copper.tasks.update` Update a Copper task write

**Webhooks 5**

- `copper.webhooks.create` Create a Copper webhook subscription write
- `copper.webhooks.delete` Delete a Copper webhook subscription destructive
- `copper.webhooks.get` Get a Copper webhook subscription read
- `copper.webhooks.list` List Copper webhook subscriptions read
- `copper.webhooks.update` Update a Copper webhook subscription write

**Related 4**

- `copper.related_items.create` Relate a record to a Copper record write
- `copper.related_items.delete` Remove a relationship between Copper records destructive
- `copper.related_items.list` List records related to a Copper record read
- `copper.related_items.list_by_type` List related records of one type read

**Users 3**

- `copper.users.get` Get a Copper user read
- `copper.users.me` Get the API user read
- `copper.users.search` List Copper users read

**Account 1**

- `copper.account.get` Get the Copper account read

Questions

## The Copper MCP server, answered.

**Is there a Copper MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 89 Copper actions across config, leads, opportunities and people, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Copper.

**What do I need to connect Copper?**

Copper API key (System settings > Integrations > API Keys) and Email address of the Copper user who generated the API key. The free call account { op: "connections.requirements", service: "copper" } lists exactly what to paste.

**Can an AI agent delete or change things in Copper?**

Only if its key allows it, and only with an explicit confirmation. 12 Copper actions are destructive, including delete a Copper person, delete a Copper company and delete a Copper opportunity. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Copper API limit?**

actionlake paces every call to the limits in the Copper service file: 180 calls a minute per connection. Repeated reads are answered from cache (43 Copper actions can be), which never reaches Copper.

**What does a Copper action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (89 Copper actions page). Cache hits, searches, dry runs and calls Copper refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Copper API does it cover?**

The Copper CRM API v1 at api.copper.com/developer_api/v1. It is built from Copper's documentation as read on 20 September 2026. 89 actions in 13 areas, each one in the signed service file (version 1.0.0).

**Can I combine Copper with my other systems?**

Yes. ask joins Copper to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Copper maps crm.company, which 227 other connectors also map.

**Does actionlake keep my Copper data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Copper credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Copper

Shares the most action names with

- [Pipedrive 54](https://actionlake.com/connectors/pipedrive)
- [Insightly CRM 32](https://actionlake.com/connectors/insightly-crm)
- [Salesloft 24](https://actionlake.com/connectors/salesloft)
- [Crelate 24](https://actionlake.com/connectors/crelate)
- [Freshsales 24](https://actionlake.com/connectors/freshsales)
- [Affinity 23](https://actionlake.com/connectors/affinity)

Joins with, on shared entities

- [Odoo 7](https://actionlake.com/connectors/odoo)
- [ERPNext (Frappe) 7](https://actionlake.com/connectors/erpnext-frappe)
- [Accelo 7](https://actionlake.com/connectors/accelo)
- [Acumatica Cloud ERP 6](https://actionlake.com/connectors/acumatica-cloud-erp)
- [Unified.to 6](https://actionlake.com/connectors/unified-to)
- [Productive.io 6](https://actionlake.com/connectors/productive-io)

Browse

- [All CRM & sales connectors](https://actionlake.com/connectors/category/crm-and-sales)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Copper; the name is the vendor's own. Counts are from the Copper service file, version 1.0.0.

## Give your agent Copper today.

[Connect Copper free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/copper
More: https://actionlake.com/llms.txt