Copper CRM
Drive Copper (Google Workspace-native CRM) from any AI agent: people, companies, opportunities, leads, activities, tasks. 12 tools, API-token auth with email + token + appname headers.
7 天免费 · 无需信用卡 · EU 托管
问 Copper 任何事
通过 AnythingMCP 对 Copper CRM 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 CopperClaude 是 AI,可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Copper CRM。提示时粘贴凭据。
- 3生成 MCP API 密钥,将 AI 客户端指向生成的 MCP URL。
配置 Copper CRM
直接来自连接器定义:在哪里获取凭据、需要哪些权限,以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
This connector uses the Copper REST API v1 (developer.copper.com).
Setup:
- Sign in to Copper → top-right avatar → Settings → Integrations → API Keys → Generate API Key.
- Copy: the key + the email of the user it belongs to.
- Set:
COPPER_API_KEY= generated keyCOPPER_USER_EMAIL= the email of the API key ownerCOPPER_APP_NAME= a label for your integration (e.g.anythingmcp)
Authentication: three custom headers — X-PW-AccessToken: ${COPPER_API_KEY}, X-PW-Application: developer_api, X-PW-UserEmail: ${COPPER_USER_EMAIL}. Quirky but it's Copper's convention.
Pluralization quirk: most endpoints use the PLURAL form (/people, /companies, /opportunities, /leads). Single-record GETs use /people/{id}. Search uses POST /people/search (yes, POST for read — Copper-specific).
People = contacts, Leads = unqualified prospects (separate object before they become a person attached to a company). A 'company' is one record; a 'person' belongs to one company.
Pagination: search endpoints use page_number (1-based) + page_size (max 200). The response is a flat array; total count is NOT returned by default.
Custom fields: custom_fields on every record — array of {custom_field_definition_id, value}. Discover IDs via copper_list_custom_field_definitions.
Rate limits: ~10 req/sec per account. On 429, back off.
Out of scope here: webhooks, projects, automations, custom activity types beyond standard, file attachments.