[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Copper CRM API and MCP server

> Yes, Copper has a full REST Developer API, but no official MCP server (checked 20 Oct 2026). You create an API key under System settings > API Keys and send it with your email on every call, which means code or a third-party server and a key that acts as one user.

CRM for teams that work in Google Workspace: leads, people, companies, opportunities in pipelines, projects, tasks and an activity log on every record.

## What is the Copper CRM API?

Cotlet's Copper CRM API exposes 12 endpoints for your own Copper CRM account: list pipelines, list leads, list people, list opportunities, get opportunity, list tasks, create lead, convert lead, create opportunity, update opportunity, create task and log activity. The list_pipelines endpoint returns pipelines with their stages, and the loss reasons of your workspace. Each endpoint takes simple JSON inputs like status, limit or cursor and works both as an operation of the copper_crm_read or copper_crm_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 12 (6 read, 6 write)
- **Updated:** 2026-10-21

Yes, Copper has a full REST Developer API, but no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Copper CRM with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Copper CRM have an official API?

Yes, Copper has a full REST Developer API, but no official MCP server (checked 20 Oct 2026). You create an API key under System settings > API Keys and send it with your email on every call, which means code or a third-party server and a key that acts as one user.

| Task | Copper CRM official | Cotlet |
|---|---|---|
| List and read opportunities, pipelines and stages | Yes: Developer API, with your own code or a connector | Yes |
| Move an opportunity to another stage | Yes: Developer API update, Zapier action Update Opportunity | Yes |
| Mark an opportunity Won or Lost with a loss reason | Yes: Developer API loss_reason_id on a Lost opportunity | Yes |
| Convert a lead to a person, company and opportunity | Yes: Developer API convert endpoint, no Zapier action | Yes |
| Create leads and opportunities | Yes: Developer API and Zapier create actions | Yes |
| Create tasks on any record | Yes: Developer API and Zapier Create Task | Yes |
| Log an activity on a record | Yes: Developer API and Zapier Create Activity | Yes |
| Let an AI agent do the above without code | No: No official MCP server | Yes |

Sources: [Copper Developer API: Getting started](https://developer.copper.com/), [Copper Developer API: Authentication](https://developer.copper.com/introduction/authentication.html), [Copper Developer API: Requests and rate limits](https://developer.copper.com/introduction/requests.html), [Copper Help: Automating your account with Workflow Automation](https://support.copper.com/hc/en-us/articles/360014085894-Automating-your-Account-with-Workflow-Automation), [Copper triggers and actions on Zapier](https://zapier.com/apps/copper/integrations)

## For AI agents

```text
Yes, Copper has a full REST Developer API, but no official MCP server (checked 20 Oct 2026). You create an API key under System settings > API Keys and send it with your email on every call, which means code or a third-party server and a key that acts as one user.
Cotlet provides a hosted MCP server and REST API for Copper CRM: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=copper-crm, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    copper_crm_read, copper_crm_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/copper-crm, each operation at its own route, e.g. PATCH /api/v1/copper-crm/opportunities/{opportunity_id}
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_pipelines, list_leads, list_people, list_opportunities, get_opportunity, list_tasks, create_lead, convert_lead, create_opportunity, update_opportunity, create_task, log_activity
Confirm      create_lead, convert_lead, create_opportunity, update_opportunity, create_task, log_activity (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/copper-crm-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=copper-crm, requests Copper CRM in the Cotlet console and creates an API key there.
2. The user signs in to Copper CRM once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Copper CRM for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Copper CRM server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Copper CRM MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Copper CRM in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Copper CRM only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Copper CRM login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Copper CRM's terms; Cotlet is not affiliated with Copper CRM.
```

## What can an AI agent do in Copper CRM?

Cotlet is best for Copper users who are not developers and want their AI agent to chase stale deals, convert leads, close lost deals and log calls without running or fixing a server.

- **[Follow up on stale deals](https://cotlet.dev/integrations/copper-crm-api-mcp-server/follow-up-on-stale-deals.md)** (runs: weekly): "List open Sales opportunities in Copper that sat 14 or more days with no activity, read their last notes and create a follow-up task for each owner." → `list_opportunities`, `get_opportunity`, `create_task`
- **[Convert qualified leads](https://cotlet.dev/integrations/copper-crm-api-mcp-server/convert-qualified-leads.md)** (runs: daily): "Go through Open leads in Copper. Convert the ones with a company and a work email to a person with a deal in the Sales pipeline, and leave the rest for me with a one-line reason." → `list_leads`, `list_people`, `convert_lead`
- **[Close lost deals with a reason](https://cotlet.dev/integrations/copper-crm-api-mcp-server/close-lost-deals-with-a-reason.md)** (runs: weekly): "Find open Sales deals in Copper that have been quiet for 30 days. If the last notes show the customer chose someone else or turned down the price, mark the deal Lost with the matching loss reason. If they asked to wait, mark it Abandoned. Leave the rest." → `list_opportunities`, `get_opportunity`, `list_pipelines`, `update_opportunity`
- **Log a call and set the next step**: "Log a Phone Call on Dana Whitfield at Brightside Clinic with these notes, then create a Meeting task for next Tuesday to send the proposal." → `list_people`, `log_activity`, `create_task`
- **Add inbound enquiries as leads** (runs: daily): "Take the enquiries from this list, skip anyone who is already a lead or a person in Copper, and add the rest as leads with status New." → `list_leads`, `list_people`, `create_lead`
- **Weekly pipeline summary** (runs: weekly): "Every Monday, list open Sales deals by stage with count and total value, and name the five largest." → `list_pipelines`, `list_opportunities`

## Can Copper CRM automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Copper CRM connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to follow up on stale deals, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/copper-crm/opportunities. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/copper-crm/opportunities with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Copper CRM.

### list_pipelines

Pipelines with their stages, and the loss reasons of your workspace. Access: read. REST: `GET /api/v1/copper-crm/pipelines`. MCP: `copper_crm_read → list_pipelines`.

No parameters.

Returns every pipeline you can see with its stages in board order, and the loss reasons set under Settings > Loss Reasons. Use pipeline and stage names as the filters of list_opportunities and as the values for create_opportunity and update_opportunity. Use a loss reason name with update_opportunity when you mark a deal Lost.

Example response:

```json
{
  "pipelines": [
    {
      "pipeline_id": "1042",
      "name": "Sales",
      "stages": [
        "Discovery",
        "Proposal",
        "Negotiation"
      ]
    },
    {
      "pipeline_id": "1043",
      "name": "Renewals",
      "stages": [
        "Upcoming",
        "Contacted",
        "Confirmed"
      ]
    }
  ],
  "loss_reasons": [
    "Competitor",
    "Features",
    "Price"
  ]
}
```

### list_leads

Leads with status, company and email. Needs Leads switched on in your workspace. Access: read. REST: `GET /api/v1/copper-crm/leads`. MCP: `copper_crm_read → list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Lead Status name as your workspace shows it, e.g. New, Open, Unqualified or Junk. |
| `limit` | integer | no | How many leads to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists leads, filtered by Lead Status (the defaults are New, Open, Unqualified and Junk, and your workspace may have more). Follow next_cursor for the next page. Pass lead_id to convert_lead. If Leads are off in the workspace, the call fails and says so; an admin turns them on under Workspace Settings > Customize > Lead Statuses.

Example response:

```json
{
  "leads": [
    {
      "lead_id": "52710344",
      "name": "Dana Whitfield",
      "status": "Open",
      "company_name": "Brightside Clinic",
      "email": "dana@brightside.example",
      "created_at": "2026-10-14T09:12:00Z"
    },
    {
      "lead_id": "52710901",
      "name": "Lee Park",
      "status": "Open",
      "company_name": null,
      "email": "lee.park@mail.example",
      "created_at": "2026-10-15T16:40:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_people

People (contacts) matching a name or email, with company and Contact Type. Access: read. REST: `GET /api/v1/copper-crm/peoples`. MCP: `copper_crm_read → list_people`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name or email to search for. |
| `limit` | integer | no | How many people to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches the People section by name or email. Use it before creating a lead or converting one, so you do not make a second person for the same address. Returns person_id, company and Contact Type as Copper shows them. Follow next_cursor for more.

Example response:

```json
{
  "people": [
    {
      "person_id": "77120458",
      "name": "Marta Cole",
      "email": "marta@brightside.example",
      "company_name": "Brightside Clinic",
      "contact_type": "Potential Customer"
    }
  ],
  "next_cursor": null
}
```

### list_opportunities

Opportunities with pipeline, stage, status, value, close date, days in stage and inactive days. Access: read. REST: `GET /api/v1/copper-crm/opportunities`. MCP: `copper_crm_read → list_opportunities`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pipeline` | string | no | Pipeline name, e.g. Sales. |
| `stage` | string | no | Stage name within the pipeline. |
| `status` | enum | no | Open, Won, Lost or Abandoned. Default: Open. |
| `limit` | integer | no | How many opportunities to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists opportunities, filtered by pipeline, stage and status (Open, Won, Lost or Abandoned). Each row has days_in_stage and inactive_days as Copper calculates them, has_open_tasks (the same signal as the task indicator light) and the primary contact. Follow next_cursor to the end of the list. Pass opportunity_id to get_opportunity or update_opportunity.

Example response:

```json
{
  "opportunities": [
    {
      "opportunity_id": "31842907",
      "name": "Northwind renewal",
      "pipeline": "Sales",
      "stage": "Negotiation",
      "status": "Open",
      "monetary_value": 18000,
      "close_date": "2026-10-30",
      "primary_contact": "Priya Nair",
      "days_in_stage": 21,
      "inactive_days": 33,
      "has_open_tasks": false
    },
    {
      "opportunity_id": "31844120",
      "name": "Harbor Dental proposal",
      "pipeline": "Sales",
      "stage": "Proposal",
      "status": "Open",
      "monetary_value": 9500,
      "close_date": "2026-11-12",
      "primary_contact": "Sam Ortiz",
      "days_in_stage": 9,
      "inactive_days": 14,
      "has_open_tasks": false
    }
  ],
  "next_cursor": null
}
```

### get_opportunity

One opportunity with its latest activity-log entries and open tasks. Access: read. REST: `GET /api/v1/copper-crm/opportunities/{opportunity_id}`. MCP: `copper_crm_read → get_opportunity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Id from list_opportunities. |

Returns the fields of list_opportunities plus the newest entries of the record's Activity Log, newest first, and its open tasks. Use it to read what happened on a deal before you write a task or change its status.

Example response:

```json
{
  "opportunity_id": "31844120",
  "name": "Harbor Dental proposal",
  "pipeline": "Sales",
  "stage": "Proposal",
  "status": "Open",
  "monetary_value": 9500,
  "close_date": "2026-11-12",
  "activities": [
    {
      "type": "Phone Call",
      "date": "2026-10-06",
      "details": "Asked for revised pricing, will decide after the board meeting."
    },
    {
      "type": "Meeting",
      "date": "2026-09-29",
      "details": "Walked through the proposal with the practice manager."
    }
  ],
  "open_tasks": []
}
```

### list_tasks

Tasks with due date, type, assignee and the record they belong to. Access: read. REST: `GET /api/v1/copper-crm/tasks`. MCP: `copper_crm_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `related_to_id` | string | no | Only tasks on this lead, person, company or opportunity id. |
| `due_before` | date | no | Only tasks due on or before this date, YYYY-MM-DD. |
| `limit` | integer | no | How many tasks to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists tasks, soonest due first. Filter by the record they belong to or by a due-date cutoff. Tasks are visible to every user in the account unless their owner made them private, so you see what your account role lets you see. Follow next_cursor for more.

Example response:

```json
{
  "tasks": [
    {
      "task_id": "9061233",
      "name": "Send revised pricing",
      "activity_type": "To-do",
      "due_date": "2026-10-21",
      "assignee": "Sam Ortiz",
      "related_to": {
        "type": "opportunity",
        "id": "31844120",
        "name": "Harbor Dental proposal"
      },
      "status": "open"
    }
  ],
  "next_cursor": null
}
```

### create_lead

Add a lead with name, email, company and status. Access: write, asks the user first. REST: `POST /api/v1/copper-crm/leads`. MCP: `copper_crm_write → create_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Full name of the lead. |
| `email` | string | no | Email address. |
| `company_name` | string | no | Company the lead works for. |
| `status` | string | no | Lead Status name, e.g. New or Open. |
| `description` | string | no | Extra details that have no field of their own. |

Adds a lead the way Add New > Add Lead does. Only the name is required. Leads must be switched on in the workspace. The lead is visible to your team. Search with list_leads and list_people first to avoid duplicates. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": "52711477",
  "name": "Omar Haddad",
  "status": "New",
  "company_name": "Cedar Labs",
  "url": "https://app.copper.com/companies/leads/52711477"
}
```

### convert_lead

Convert a lead to a person, optionally with an opportunity. Access: write, asks the user first. REST: `POST /api/v1/copper-crm/leads/{lead_id}/convert`. MCP: `copper_crm_write → convert_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | string | yes | Id from list_leads. |
| `contact_type` | string | no | Contact Type as your workspace names it, e.g. Potential Customer. |
| `opportunity_name` | string | no | Pipeline Record Name. Leave out to convert without an opportunity. |
| `pipeline` | string | no | Pipeline name for the opportunity, from list_pipelines. |
| `close_date` | date | no | Close date of the opportunity, YYYY-MM-DD. |
| `monetary_value` | number | no | Value of the opportunity. |

Runs Convert Lead from the lead's Details tab. It creates the person and, when you pass opportunity_name and pipeline, an opportunity with the close date and value you give. The lead record is removed. It fails when a required field of the person or the opportunity is empty, and the error names the field. Copper cannot turn a person back into a lead. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "person": {
    "person_id": "77121902",
    "name": "Dana Whitfield",
    "contact_type": "Potential Customer"
  },
  "opportunity": {
    "opportunity_id": "31850018",
    "name": "Brightside Clinic rollout",
    "pipeline": "Sales",
    "stage": "Discovery",
    "monetary_value": 12000,
    "close_date": "2026-12-15"
  },
  "lead_removed": true
}
```

### create_opportunity

Add an opportunity to a pipeline for an existing person. Access: write, asks the user first. REST: `POST /api/v1/copper-crm/primary-contacts/{primary_contact_id}/opportunities`. MCP: `copper_crm_write → create_opportunity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Name of the opportunity. |
| `primary_contact_id` | string | yes | person_id of the primary contact, from list_people. |
| `pipeline` | string | no | Pipeline name, from list_pipelines. |
| `stage` | string | no | Stage name within the pipeline. |
| `monetary_value` | number | no | Value of the opportunity. |
| `close_date` | date | no | Close date, YYYY-MM-DD. |

Adds an opportunity the way Add Opportunity does. Copper requires only the name and the primary contact. Pipeline, stage, value and close date are optional. The opportunity is visible to your team and can trigger Workflow Automation rules. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "opportunity_id": "31850733",
  "name": "Cedar Labs onboarding",
  "pipeline": "Sales",
  "stage": "Discovery",
  "status": "Open",
  "monetary_value": 7200,
  "close_date": "2026-12-01",
  "primary_contact": "Omar Haddad"
}
```

### update_opportunity

Move an opportunity to another stage or set its status, loss reason and close date. Access: write, asks the user first. REST: `PATCH /api/v1/copper-crm/opportunities/{opportunity_id}`. MCP: `copper_crm_write → update_opportunity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Id from list_opportunities. |
| `stage` | string | no | Stage name within the opportunity's pipeline. |
| `status` | enum | no | Open, Won, Lost or Abandoned. |
| `loss_reason` | string | no | Loss reason name from list_pipelines. Used with status Lost. |
| `close_date` | date | no | Close date, YYYY-MM-DD. |
| `monetary_value` | number | no | Value of the opportunity. |

Changes only the fields you pass. Set status to Won, Lost, Abandoned or Open. For Lost, pass loss_reason from list_pipelines, as the Loss Reasons box in Copper asks for one, and set close_date to today to keep reports accurate. Other users see the change, and Workflow Automation rules may fire on it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "opportunity_id": "31842907",
  "name": "Northwind renewal",
  "pipeline": "Sales",
  "stage": "Negotiation",
  "status": "Lost",
  "loss_reason": "Price",
  "close_date": "2026-10-20",
  "monetary_value": 18000
}
```

### create_task

Add a task with a type and due date on a lead, person, company or opportunity. Access: write, asks the user first. REST: `POST /api/v1/copper-crm/tasks`. MCP: `copper_crm_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Task title. |
| `related_to_type` | enum | no | lead, person, company or opportunity. |
| `related_to_id` | string | no | Id of the record the task belongs to. |
| `due_date` | date | no | Due date, YYYY-MM-DD. |
| `activity_type` | string | no | Activity Type name, e.g. Phone Call or Meeting. |
| `assignee` | string | no | Name or email of the teammate. Default: you. |

Adds a task the way Add Task in the Related section does. activity_type is the Activity Type Copper asks for: Phone Call, Meeting, To-do (once turned on) or one of your custom types. Tasks are visible to the whole account by default, and an assignee other than you gets it in their list. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": "9061877",
  "name": "Follow up on Harbor Dental proposal: asked for revised pricing on Oct 6",
  "activity_type": "Phone Call",
  "due_date": "2026-10-23",
  "assignee": "Sam Ortiz",
  "related_to": {
    "type": "opportunity",
    "id": "31844120",
    "name": "Harbor Dental proposal"
  }
}
```

### log_activity

Log a call, meeting or custom activity on a record. Access: write, asks the user first. REST: `POST /api/v1/copper-crm/records/{record_id}/activities`. MCP: `copper_crm_write → log_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_type` | enum | yes | lead, person, company, opportunity or project. |
| `record_id` | string | yes | Id of the record. |
| `activity_type` | string | yes | Activity Type name, e.g. Phone Call or Meeting. |
| `details` | string | no | Notes for the entry. |
| `occurred_at` | datetime | no | When it happened, ISO 8601. Default: now. |

Adds an entry to the record's Activity Log, as Log Activity does. Phone Call and Meeting count in interaction stats and the Activity by User report, To-do does not, and a custom type counts only if it was created as an interaction. Completing a task does not log an activity by itself. The entry is visible to your team. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "activity_id": "64018822",
  "activity_type": "Phone Call",
  "record": {
    "type": "person",
    "id": "77121902",
    "name": "Dana Whitfield"
  },
  "occurred_at": "2026-10-19T15:30:00Z",
  "details": "Walked through pricing, she will check with the clinic owner."
}
```

## How do I connect Copper CRM to Claude Code, Codex or Cursor?

Connecting Copper CRM takes three steps: sign up, sign in to Copper CRM once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Copper CRM to your agent.

1. **Create an account** Sign up and add Copper CRM in the console. Your API key is there too.

2. **Sign in to Copper CRM in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Copper CRM there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Copper CRM tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List open Sales opportunities in Copper that sat 14 or more days with no activity, read their last notes and create a follow-up task for each owner.
```

### Call Copper CRM from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/copper-crm with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/copper-crm/opportunities/31842907 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"Lost","loss_reason":"Price","close_date":"2026-10-20"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "opportunity_id": "31842907",
  "name": "Northwind renewal",
  "pipeline": "Sales",
  "stage": "Negotiation",
  "status": "Lost",
  "loss_reason": "Price",
  "close_date": "2026-10-20",
  "monetary_value": 18000
}
```

## Why use Cotlet for Copper CRM?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Copper CRM yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Copper CRM changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Copper CRM to Cotlet?

Yes. You sign in to Copper CRM yourself, in your own Cloud Browser, and we never save your password. Your agents only get Copper CRM once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Copper CRM integration?**

No, Cotlet is independent of Copper CRM. Copper CRM's own API is too limited for this work. Cotlet works through your own Copper CRM account, the way you use Copper CRM in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Copper CRM in your console: your agents lose access at once and you stay signed in. Signing out of Copper CRM in the browser works too, and Reset browser deletes the whole profile.

## Is there a Copper CRM MCP server on GitHub?

Yes. Community Copper MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it your Copper API key and email, and keep it running yourself. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create an API key in Copper, add it to each MCP client | Sign up, sign in to Copper once, add one MCP server or API key |
| When Copper changes | Copper publishes a changelog and a change policy for its API, so breaks are rare, but you update the server yourself | Our team tests it daily and fixes it for you; failed calls are free |
| Your Copper access | An API key and your email in a file on your computer, readable by any program you run | A session in your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | The key works until someone deletes it, then tools fail until you make a new one | Your Cloud Browser keeps you signed in; if Copper logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Copper CRM changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Copper CRM API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Copper CRM API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Copper CRM account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Copper CRM yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Copper CRM only after you enable it. When Copper CRM signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Copper CRM, sign out of Copper CRM in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Copper CRM's terms:** You use your own Copper CRM account and stay responsible for following Copper CRM's terms. Cotlet is independent and not affiliated with Copper CRM. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Copper CRM in the console and press Request access. Then you create your API key and connect Copper CRM there.

**Do I need to be technical?**

No. You sign in to Copper CRM once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Copper CRM to Cotlet?**

Yes. You sign in to Copper CRM yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Copper CRM once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Copper CRM sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Copper CRM cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Copper CRM's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Copper CRM sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Copper CRM login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Copper CRM offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need an API key or the admin role in Copper?**

No. Cotlet works in your signed-in Copper session, not through an API key, which an admin or user creates under System settings > API Keys. Your role still counts: Leads must be switched on in your workspace, and you only see and change what your Copper account may.

**What does the agent not do in Copper?**

It does not create Workflow Automation rules (only admins make them in the web app), send emails, upload files, or edit Projects, companies and custom fields. It works on leads, people, opportunities, tasks and activities.

**Can my agent post or send messages in Copper CRM without asking me?**

No. Every call to create_lead, convert_lead, create_opportunity, update_opportunity, create_task or log_activity waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Copper CRM API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/copper-crm from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.