Copper CRM

This connector uses the Copper REST API v1 (developer.copper.com).

Setup:

1. Sign in to Copper → top-right avatar → Settings → Integrations → API Keys → Generate API Key.
2. Copy: the key + the email of the user it belongs to.
3. Set:
   • COPPER_API_KEY = generated key
   • COPPER_USER_EMAIL = the email of the API key owner
   • COPPER_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.