Skip to content
actionlake
Start free

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 freeSee 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
  • 89actionsin one signed file
  • 44readlook, never change
  • 33writecreate and update
  • 12wait for a yesdestructive, 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_keyCopper API key (System settings > Integrations > API Keys)
    • user_emailEmail 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 callcheck { 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_keyuser_email
Limits we pace to
180 calls a minute, per connection
API covered
Copper CRM API v1api.copper.com/developer_api/v1
Built from
Copper's documentation, read 20 September 2026developer.copper.comdeveloper.copper.com
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.

  • 44readlook, never change
  • 33writecreate and update
  • 12destructivewait 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.

ActionWhat it doesEffectSame name in
copper.people.searchSearch Copper peopleList 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…readcrm.contact.search46 connectors
copper.companies.searchSearch Copper companiesList 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`…readcrm.company.search36 connectors
copper.people.createCreate a Copper personCreate a new person.writecrm.contact.create161 connectors
copper.companies.createCreate a Copper companyCreate a new company.writecrm.company.create142 connectors
copper.opportunities.searchSearch Copper opportunitiesList or filter opportunities — every filter is optional; with none you get all opportunities sorted by `sort_by`. Copper pages with `page_number` and…readcrm.deal.search9 connectors
copper.opportunities.createCreate a Copper opportunityCreate a new opportunity.writecrm.deal.create43 connectors
copper.tasks.searchSearch Copper tasksList 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…readwork.task.search26 connectors
copper.leads.searchSearch Copper leadsList 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…readcrm.lead.search6 connectors
copper.people.deleteDelete a Copper personDelete one person by id.destructivecrm.contact.delete147 connectors
copper.tasks.createCreate a Copper taskCreate a new task.writework.task.create127 connectors
copper.projects.createCreate a Copper projectCreate a new project.writework.project.create102 connectors
copper.leads.createCreate a Copper leadCreate a new lead.writecrm.lead.create24 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. Readread

    Which Copper deals are due to close this month, and what are they worth in total?

    callscopper.opportunities.search

  2. Planwrite

    Convert a qualified lead into a person, company and opportunity in Copper. Ask me before anything is sent or changed.

    callscopper.leads.getcopper.lead_activities.listcopper.pipeline_stages.listcopper.leads.convertcopper.opportunities.get+1 more

  3. Planread

    Pull a full activity digest for one company account in Copper.

    callscopper.companies.getcopper.company_activities.listcopper.related_items.listcopper.files.listcopper.opportunities.search

  4. Writewrite

    Create a Copper person in Copper. Show me exactly what you will send before you save it.

    callscopper.people.create

  5. Across systemsread

    Which Copper companies have invoices in ConnectWise PSA, and how many each?

    callscopper.companies.searchconnectwise_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

  • Which Copper companies have invoices in NetSuite, and how many each?

    copper.companies.search + netsuite.views.invoices, on crm.company · NetSuite

Also mapped by other connectorsidentity.user 517crm.company 227crm.contact 192work.project 116work.task 105crm.deal 43crm.lead 28crm.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 decidesImport 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 decidesSend 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 decidesConvert 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 decidesPermanently 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 personcopper.people.delete
  • Delete a Copper companycopper.companies.delete
  • Delete a Copper opportunitycopper.opportunities.delete
  • Delete a Copper taskcopper.tasks.delete
  • Delete a Copper projectcopper.projects.delete
  • Delete a Copper leadcopper.leads.delete
  • Delete a Copper activitycopper.activities.delete
  • Remove a relationship between Copper recordscopper.related_items.delete
  • Delete a Copper webhook subscriptioncopper.webhooks.delete
  • Delete a Copper connect-field linkcopper.related_links.delete
  • Delete a Copper custom field definitioncopper.custom_field_definitions.delete
  • Delete a file attached to a Copper recordcopper.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.

docopper.people.deleteconfirm_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: "[email protected]" },    { match: "copper.companies.delete", approver: "[email protected]" },    { match: "copper.opportunities.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 89 Copper actions
  • 89actions pageeach page of a long list is one call
  • 43reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Copper action.

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

Config14
  • copper.custom_activity_types.createCreate a Copper custom activity typewrite
  • copper.custom_activity_types.getGet a Copper custom activity typeread
  • copper.custom_activity_types.listList Copper custom activity typesread
  • copper.custom_activity_types.updateUpdate a Copper custom activity typewrite
  • copper.custom_field_definitions.createCreate a Copper custom field definitionwrite
  • copper.custom_field_definitions.deleteDelete a Copper custom field definitiondestructive
  • copper.custom_field_definitions.getGet a Copper custom field definitionread
  • copper.custom_field_definitions.listList Copper custom field definitionsread
  • copper.custom_field_definitions.updateUpdate a Copper custom field definitionwrite
  • copper.field_layouts.getGet a Copper entity's field layoutread
  • copper.related_links.createCreate a Copper connect-field linkwrite
  • copper.related_links.deleteDelete a Copper connect-field linkdestructive
  • copper.related_links.listList Copper connect-field linksread
  • copper.tags.listList Copper tagsread
Leads12
  • copper.customer_sources.listList Copper customer sourcesread
  • copper.lead_activities.listList activities on a Copper leadread
  • copper.lead_statuses.listList Copper lead statusesread
  • copper.leads.bulk_createBulk create Copper leadswrite
  • copper.leads.bulk_updateBulk update Copper leadswrite
  • copper.leads.convertConvert a Copper leadwrite
  • copper.leads.createCreate a Copper leadwrite
  • copper.leads.deleteDelete a Copper leaddestructive
  • copper.leads.getGet a Copper leadread
  • copper.leads.searchSearch Copper leadsread
  • copper.leads.updateUpdate a Copper leadwrite
  • copper.leads.upsertUpsert a Copper leadwrite
Opportunities10
  • copper.loss_reasons.listList Copper loss reasonsread
  • copper.opportunities.bulk_createBulk create Copper opportunitieswrite
  • copper.opportunities.createCreate a Copper opportunitywrite
  • copper.opportunities.deleteDelete a Copper opportunitydestructive
  • copper.opportunities.getGet a Copper opportunityread
  • copper.opportunities.searchSearch Copper opportunitiesread
  • copper.opportunities.updateUpdate a Copper opportunitywrite
  • copper.pipeline_stages.listList Copper pipeline stagesread
  • copper.pipeline_stages.list_by_pipelineList stages of one Copper pipelineread
  • copper.pipelines.listList Copper pipelinesread
People10
  • copper.contact_types.listList Copper contact typesread
  • copper.people.bulk_createBulk create Copper peoplewrite
  • copper.people.bulk_updateBulk update Copper peoplewrite
  • copper.people.createCreate a Copper personwrite
  • copper.people.deleteDelete a Copper persondestructive
  • copper.people.getGet a Copper personread
  • copper.people.get_by_emailGet a Copper person by emailread
  • copper.people.searchSearch Copper peopleread
  • copper.people.updateUpdate a Copper personwrite
  • copper.person_activities.listList activities on a Copper personread
Companies8
  • copper.companies.bulk_createBulk create Copper companieswrite
  • copper.companies.bulk_updateBulk update Copper companieswrite
  • copper.companies.createCreate a Copper companywrite
  • copper.companies.deleteDelete a Copper companydestructive
  • copper.companies.getGet a Copper companyread
  • copper.companies.searchSearch Copper companiesread
  • copper.companies.updateUpdate a Copper companywrite
  • copper.company_activities.listList activities on a Copper companyread
Activities7
  • copper.activities.bulk_createBulk log Copper activitieswrite
  • copper.activities.createLog a Copper activitywrite
  • copper.activities.deleteDelete a Copper activitydestructive
  • copper.activities.getGet a Copper activityread
  • copper.activities.querySearch Copper activitiesread
  • copper.activities.updateUpdate a Copper activitywrite
  • copper.activity_types.listList Copper activity typesread
Files5
  • copper.files.attachAttach an uploaded file to a Copper recordwrite
  • copper.files.deleteDelete a file attached to a Copper recorddestructive
  • copper.files.getGet an attached file's metadataread
  • copper.files.get_upload_urlGet a signed S3 upload URL for a Copper recordread
  • copper.files.listList files attached to a Copper recordread
Projects5
  • copper.projects.createCreate a Copper projectwrite
  • copper.projects.deleteDelete a Copper projectdestructive
  • copper.projects.getGet a Copper projectread
  • copper.projects.searchSearch Copper projectsread
  • copper.projects.updateUpdate a Copper projectwrite
Tasks5
  • copper.tasks.createCreate a Copper taskwrite
  • copper.tasks.deleteDelete a Copper taskdestructive
  • copper.tasks.getGet a Copper taskread
  • copper.tasks.searchSearch Copper tasksread
  • copper.tasks.updateUpdate a Copper taskwrite
Webhooks5
  • copper.webhooks.createCreate a Copper webhook subscriptionwrite
  • copper.webhooks.deleteDelete a Copper webhook subscriptiondestructive
  • copper.webhooks.getGet a Copper webhook subscriptionread
  • copper.webhooks.listList Copper webhook subscriptionsread
  • copper.webhooks.updateUpdate a Copper webhook subscriptionwrite
Related4
  • copper.related_items.createRelate a record to a Copper recordwrite
  • copper.related_items.deleteRemove a relationship between Copper recordsdestructive
  • copper.related_items.listList records related to a Copper recordread
  • copper.related_items.list_by_typeList related records of one typeread
Users3
  • copper.users.getGet a Copper userread
  • copper.users.meGet the API userread
  • copper.users.searchList Copper usersread
Account1
  • copper.account.getGet the Copper accountread

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

Joins with, on shared entities

Browse

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 freeSee pricing

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