Read and write Copper CRM people, companies, opportunities and activities. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"copper": {
"url": "https://copper.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"copper": {
"type": "http",
"url": "https://copper.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Copper API key and Copper account email.
Create a key in Copper → Settings → Integrations → API Keys. The email must be the one that owns the key. Your credentials are used only to call the API on your behalf and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Copper API key and Copper account email. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Copper connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
copper_get_account | read | Get account Get details of the authenticated Copper account. Copper REST: GET /account. |
copper_list_users | read | List users List users in the Copper account (id, name, email) — useful for resolving assignee ids. Copper REST: POST /users/search. |
copper_search_people | read | Search people Search/list people (contacts). All filters optional; returns a page of people. Copper REST: POST /people/search. |
copper_get_person | read | Get person Get a single person (contact) by id. Copper REST: GET /people/{id}. |
copper_search_companies | read | Search companies Search/list companies. All filters optional; returns a page of companies. Copper REST: POST /companies/search. |
copper_get_company | read | Get company Get a single company by id. Copper REST: GET /companies/{id}. |
copper_search_opportunities | read | Search opportunities Search/list opportunities (deals). All filters optional; returns a page of opportunities. Copper REST: POST /opportunities/search. |
copper_get_opportunity | read | Get opportunity Get a single opportunity (deal) by id. Copper REST: GET /opportunities/{id}. |
copper_search_leads | read | Search leads Search/list leads. All filters optional; returns a page of leads. Copper REST: POST /leads/search. |
copper_get_lead | read | Get lead Get a single lead by id. Copper REST: GET /leads/{id}. |
copper_search_tasks | read | Search tasks Search/list tasks. All filters optional; returns a page of tasks. Copper REST: POST /tasks/search. |
copper_get_task | read | Get task Get a single task by id. Copper REST: GET /tasks/{id}. |
copper_list_activities | read | List activities List activities (notes, calls, meetings, system events) attached to a record. Copper REST: POST /activities/search. |
copper_list_activity_types | read | List activity types List the account's activity types (user + system), needed to log an activity. Copper REST: GET /activity_types. |
copper_list_pipelines | read | List pipelines List sales pipelines and their stages (ids needed to place opportunities). Copper REST: GET /pipelines. |
copper_create_person | write | Create person Create a new person (contact). Copper REST: POST /people. |
copper_update_person | write | Update person Update fields on an existing person. Only provided fields are changed. Copper REST: PUT /people/{id}. |
copper_create_company | write | Create company Create a new company. Copper REST: POST /companies. |
copper_create_opportunity | write | Create opportunity Create a new opportunity (deal). `name` and `primary_contact_id` are required by Copper. Copper REST: POST /opportunities. |
copper_create_lead | write | Create lead Create a new lead. Copper REST: POST /leads. |
copper_create_task | write | Create task Create a new task. Copper REST: POST /tasks. |
copper_log_activity | write | 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_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
copper_request_feature | Request a missing feature Tell usefulapi that the user needs something the Copper tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
copper_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Copper tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
copper_cancel_subscription | Cancel the Pro subscription Cancel the caller's Copper Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run copper_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Copper server only. Subscribe with copper_upgrade (it returns a Stripe Checkout link). Cancel any time with copper_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running copper_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Copper. The server calls the Copper API with your own Copper access, so it sees only the data that your account can see.
The login page asks for your Copper API key and Copper account email. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Copper API key and Copper account email. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Copper API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Copper.
Yes, if you approve it. 7 of the 22 Copper tools can create or change data. The other 15 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Copper server only. Run copper_usage_status to see how many calls you used.
Ask the AI to run copper_upgrade: it returns a Stripe Checkout link. To cancel, run copper_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with copper_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.