mcpbeat Sign in

Copper MCP by usefulapi MCP Server

answering

Copper MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 22 tools. Last commit 12 Oct 2026.

Read and write Copper CRM people, companies, opportunities and activities.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
22
Tools
read from the server
95 ms
Response time
average over 24h
0
Stars
last commit 12 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
8 Oct a tool changed version2 times that day
1 Oct a tool changed version
and 4 more, back to 1 October 2026

Nothing serious here today

Today is the operative word: we check Copper MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add copper --transport http https://copper.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "copper": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.copper]
url = "https://copper.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "copper": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "copper": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

copper
copper_create_company
Create a new company. Copper REST: POST /companies.
copper_create_lead
Create a new lead. Copper REST: POST /leads.
copper_create_opportunity
Create a new opportunity (deal). `name` and `primary_contact_id` are required by Copper. Copper REST: POST /opportunities.
copper_create_person
Create a new person (contact). Copper REST: POST /people.
copper_create_task
Create a new task. Copper REST: POST /tasks.
copper_get_account
Get details of the authenticated Copper account. Copper REST: GET /account.
copper_get_company
Get a single company by id. Copper REST: GET /companies/{id}.
copper_get_lead
Get a single lead by id. Copper REST: GET /leads/{id}.
copper_get_opportunity
Get a single opportunity (deal) by id. Copper REST: GET /opportunities/{id}.
copper_get_person
Get a single person (contact) by id. Copper REST: GET /people/{id}.
copper_get_task
Get a single task by id. Copper REST: GET /tasks/{id}.
copper_list_activities
List activities (notes, calls, meetings, system events) attached to a record. Copper REST: POST /activities/search.
copper_list_activity_types
List the account's activity types (user + system), needed to log an activity. Copper REST: GET /activity_types.
copper_list_pipelines
List sales pipelines and their stages (ids needed to place opportunities). Copper REST: GET /pipelines.
copper_list_users
List users in the Copper account (id, name, email) — useful for resolving assignee ids. Copper REST: POST /users/search.
copper_log_activity
Log a user activity (e.g. a note or call) on a record. Get the activity_type_id from copper_list_activity_types. Copper REST: POST /activities.
copper_search_companies
Search/list companies. All filters optional; returns a page of companies. Copper REST: POST /companies/search.
copper_search_leads
Search/list leads. All filters optional; returns a page of leads. Copper REST: POST /leads/search.
copper_search_opportunities
Search/list opportunities (deals). All filters optional; returns a page of opportunities. Copper REST: POST /opportunities/search.
copper_search_people
Search/list people (contacts). All filters optional; returns a page of people. Copper REST: POST /people/search.
copper_search_tasks
Search/list tasks. All filters optional; returns a page of tasks. Copper REST: POST /tasks/search.
copper_update_person
Update fields on an existing person. Only provided fields are changed. Copper REST: PUT /people/{id}.

Endpoints

URLTransportStateLatencyChecked
https://copper.usefulapi.io/mcp streamable-http answering 97 ms 1 min ago

Alternatives to Copper MCP by usefulapi

same job, measured the same way
Folk MCP by usefulapi
by usefulapi

Read and write Folk CRM people, companies, groups and notes.

14 tools answering
Twenty MCP by usefulapi
by usefulapi

Read people, companies, opportunities, notes and tasks; create and update records in Twenty CRM.

20 tools answering
Teamgate MCP by usefulapi
by usefulapi

Manage Teamgate CRM leads, people, companies, deals, activities and notes.

34 tools answering
Insightly MCP by usefulapi
by usefulapi

Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.

21 tools answering
Keap MCP by usefulapi
by usefulapi

List and create Keap contacts, companies, tasks, opportunities, orders, tags and campaigns.

18 tools answering
Pipedrive MCP by usefulapi
by usefulapi

Read deals, persons, organizations, activities and pipelines; create and update CRM records.

19 tools answering
Pipeline CRM MCP by usefulapi
by usefulapi

Manage Pipeline CRM deals, people, companies, notes and calendar entries.

30 tools answering
People Data Labs MCP by usefulapi
by usefulapi

Enrich and search people and companies, resolve identities, and enrich IP addresses.

8 tools answering

Copper MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Copper MCP by usefulapi do?
It exposes 22 tools, read directly from the server on our last check. Among them: copper_create_company, copper_create_lead, copper_create_opportunity, copper_create_person, copper_create_task, copper_get_account and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Copper MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 95 ms. The bar chart above shows every period we have measured.
How do I connect Copper MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Copper MCP by usefulapi need an API key?
No. Copper MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 22 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Copper MCP by usefulapi?
It answers our handshake in 95 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Copper MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.