Copper MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 营销与社交媒体

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://copper.usefulapi.io/mcp

claude mcp add --transport http copper https://copper.usefulapi.io/mcp

{
  "mcpServers": {
    "copper": {
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "copper": {
      "type": "http",
      "url": "https://copper.usefulapi.io/mcp"
    }
  }
}

https://copper.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月9日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• copper_search_projects

  List/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.

• copper_get_project

  Read one Copper project, including details and raw custom-field values. GET /projects/{id}.

• copper_list_custom_field_definitions

  Map 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 /custom_field_definitions.

• copper_list_files

  List 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.

• copper_get_file_metadata

  Read 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}.

• 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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• ✓ 通过

  仍在维护

  代码最后更新于今天

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 15 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 27 个工具描述，未发现针对 AI 的隐藏指令

与“营销与社交媒体”中的其他服务器比较i

• 星标数多于此分类中其他 3727 个服务器的 80%
• 发布到注册中心的时间比此分类中其他 3727 个服务器的 98% 更新
• 基础检查结果等于或优于此分类中其他 3727 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{