Connect-MCP

Copper MCP by usefulapi

io.usefulapi/copper · v1.11.1

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

MCPremoteno credentialsCRM & sales

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 22 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 22 tools · 15 read, 7 write (incl. delete/pay) · CRM & sales

Test call copper_get_account: needs a key: HTTP 401 (1,089 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://copper.usefulapi.io/mcp

Tools

22 tools listed at last check
  • copper_get_account Get details of the authenticated Copper account. Copper REST: GET /account.
  • copper_list_users List users in the Copper account (id, name, email) — useful for resolving assignee ids. Copper REST: POST /users/search.
  • copper_search_people Search/list people (contacts). All filters optional; returns a page of people. Copper REST: POST /people/search.
  • copper_get_person Get a single person (contact) by id. Copper REST: GET /people/{id}.
  • copper_search_companies Search/list companies. All filters optional; returns a page of companies. Copper REST: POST /companies/search.
  • copper_get_company Get a single company by id. Copper REST: GET /companies/{id}.
  • copper_search_opportunities Search/list opportunities (deals). All filters optional; returns a page of opportunities. Copper REST: POST /opportunities/search.
  • copper_get_opportunity Get a single opportunity (deal) by id. Copper REST: GET /opportunities/{id}.
  • copper_search_leads Search/list leads. All filters optional; returns a page of leads. Copper REST: POST /leads/search.
  • copper_get_lead Get a single lead by id. Copper REST: GET /leads/{id}.
  • copper_search_tasks Search/list tasks. All filters optional; returns a page of tasks. Copper REST: POST /tasks/search.
  • 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_create_person Create a new person (contact). Copper REST: POST /people.
  • copper_update_person Update fields on an existing person. Only provided fields are changed. Copper REST: PUT /people/{id}.
  • copper_create_company Create a new company. Copper REST: POST /companies.
  • copper_create_opportunity Create a new opportunity (deal). `name` and `primary_contact_id` are required by Copper. Copper REST: POST /opportunities.
  • copper_create_lead Create a new lead. Copper REST: POST /leads.
  • copper_create_task Create a new task. Copper REST: POST /tasks.
  • 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.

Badge

Connect-MCP badge for io.usefulapi/copper

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/copper.svg)](https://clawy.uk/mcp/s/io.usefulapi/copper)