Index / MCP servers / Copper MCP by usefulapi

Copper MCP by usefulapi MCP server

Connect Copper MCP by usefulapi and your agent gets 27 tools, among them copper_create_company, copper_create_lead, copper_create_opportunity. It answers at https://copper.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.

Status
Answering
Tools
27
Official
yes, served from usefulapi.io
Reliability
4 of 4 checks
Response time
916 ms
Transport
streamable HTTP
Last checked
15 November 2026

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

Description as the publisher wrote it.

The 27 tools Copper MCP by usefulapi offers

ToolWhat it does
copper_create_companyCreate a new company. Copper REST: POST /companies.
Inputs: name, email_domain, phone_numbers, assignee_id, tags, details
copper_create_leadCreate a new lead. Copper REST: POST /leads.
Inputs: name, email, phone_numbers, company_name, title, customer_source_id
copper_create_opportunityCreate a new opportunity (deal). `name` and `primary_contact_id` are required by Copper. Copper REST: POST /opportunities.
Inputs: name, primary_contact_id, pipeline_id, pipeline_stage_id, company_id, assignee_id
copper_create_personCreate a new person (contact). Copper REST: POST /people.
Inputs: name, emails, phone_numbers, title, company_id, company_name
copper_create_taskCreate a new task. Copper REST: POST /tasks.
Inputs: name, related_resource_type, related_resource_id, assignee_id, due_date, reminder_date
copper_get_accountGet details of the authenticated Copper account. Copper REST: GET /account.
copper_get_companyGet a single company by id. Copper REST: GET /companies/{id}.
Inputs: id
copper_get_file_metadataRead metadata for a file attached to a specific Copper record. The public contract provides no download or Drive-link resolver; this tool does not claim to read the file's contents. GET /{entity_type}/{entity_id}/files/{file_id}.
Inputs: entity_type, entity_id, file_id
copper_get_leadGet a single lead by id. Copper REST: GET /leads/{id}.
Inputs: id
copper_get_opportunityGet a single opportunity (deal) by id. Copper REST: GET /opportunities/{id}.
Inputs: id
copper_get_personGet a single person (contact) by id. Copper REST: GET /people/{id}.
Inputs: id
copper_get_projectRead one Copper project, including details and raw custom-field values. GET /projects/{id}.
Inputs: id
copper_get_taskGet a single task by id. Copper REST: GET /tasks/{id}.
Inputs: id
copper_list_activitiesList activities (notes, calls, meetings, system events) attached to a record. Copper REST: POST /activities/search.
Inputs: parent_type, parent_id, minimum_activity_date, maximum_activity_date, page_number, page_size
copper_list_activity_typesList the account's activity types (user + system), needed to log an activity. Copper REST: GET /activity_types.
copper_list_custom_field_definitionsMap custom_field_definition_id to its label, data type (including URL), options and applicable entities. Existing opportunity/project reads return raw values. A returned private document URL still needs access through its own provider. GET
Inputs: available_on
copper_list_filesList attached-file IDs, names, sizes, types and timestamps on an opportunity, project or other supported entity. Returns metadata, not file bytes or Google Drive document access. GET /{entity_type}/{entity_id}/files.
Inputs: entity_type, entity_id
copper_list_pipelinesList sales pipelines and their stages (ids needed to place opportunities). Copper REST: GET /pipelines.
copper_list_usersList users in the Copper account (id, name, email) — useful for resolving assignee ids. Copper REST: POST /users/search.
Inputs: page_number, page_size
copper_log_activityLog 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.
Inputs: parent_type, parent_id, activity_type_id, details, activity_date
copper_search_companiesSearch/list companies. All filters optional; returns a page of companies. Copper REST: POST /companies/search.
Inputs: name, assignee_ids, tags, city, state, country
copper_search_leadsSearch/list leads. All filters optional; returns a page of leads. Copper REST: POST /leads/search.
Inputs: name, emails, assignee_ids, customer_source_ids, tags, city
copper_search_opportunitiesSearch/list opportunities (deals). All filters optional; returns a page of opportunities. Copper REST: POST /opportunities/search.
Inputs: name, assignee_ids, pipeline_ids, pipeline_stage_ids, company_ids, status_ids
copper_search_peopleSearch/list people (contacts). All filters optional; returns a page of people. Copper REST: POST /people/search.
Inputs: name, emails, phone_number, assignee_ids, company_ids, tags
copper_search_projectsList/search Copper Projects. name uses the vendor's name filter. contains_name scans a bounded number of pages locally; inspect complete and continue with next_page before claiming exhaustive results. POST /projects/search.
Inputs: name, contains_name, page_number, page_size, max_pages, assignee_ids
copper_search_tasksSearch/list tasks. All filters optional; returns a page of tasks. Copper REST: POST /tasks/search.
Inputs: name, assignee_ids, status, sort_by, sort_direction, page_number
copper_update_personUpdate fields on an existing person. Only provided fields are changed. Copper REST: PUT /people/{id}.
Inputs: id, name, emails, phone_numbers, title, company_id

Add Copper MCP by usefulapi to your AI client

Every block below points at https://copper.usefulapi.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http copper-mcp-by-usefulapi https://copper.usefulapi.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://copper.usefulapi.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "copper-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "copper-mcp-by-usefulapi": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "serverUrl": "https://copper.usefulapi.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Copper MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
  - name: Copper MCP by usefulapi
    type: streamable-http
    url: https://copper.usefulapi.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "httpUrl": "https://copper.usefulapi.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "copper-mcp-by-usefulapi": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fcopper.usefulapi.io%2Fmcp&type=streamable_http&id=copper-mcp-by-usefulapi&name=Copper%20MCP%20by%20usefulapi

Is Copper MCP by usefulapi up right now?

It answered our last check on 15 November 2026 in 916 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Copper MCP by usefulapi

Questions about Copper MCP by usefulapi

Is there an official Copper MCP by usefulapi MCP server?

Yes. It is published by usefulapi.io and served from copper.usefulapi.io, the vendor's own domain: https://copper.usefulapi.io/mcp.

How many tools does Copper MCP by usefulapi have?

27, as returned by the server's own tools/list on 18 November 2026: copper_create_company, copper_create_lead, copper_create_opportunity, copper_create_person, copper_create_task, copper_get_account, copper_get_company, copper_get_file_metadata, and 19 more.

Is Copper MCP by usefulapi down?

It answered our last check on 15 November 2026 in 916 ms. Over 4 checks since 29 September 2026 it answered 4.

How do I add Copper MCP by usefulapi to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://copper.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Copper MCP by usefulapi need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.usefulapi. Endpoint host: copper.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:copper. First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.