Copper API vs HubSpot API + MCP

Copper API

Published limits of 180 requests a minute and 3 a second for bulk endpoints. No official MCP server, OpenAPI spec or llms.txt.

HubSpot API + MCP

Remote MCP server GA since 13 April 2026, OAuth 2.1 with PKCE only. Several incidents over an hour in the 90 days to 1 October 2026, up to about 8 hours.

Copper API

1. Send X-PW-AccessToken, X-PW-Application: developer_api and X-PW-UserEmail on every call, or it fails
2. Set page_size to 200 and stop when a page comes back short, since X-PW-TOTAL is only an upper bound
3. Back off on 429 on your own clock, since no Retry-After is documented
4. Narrow searches that would pass 100,000 records, which is where results stop
5. Read connect fields before you update a record, because an update that omits them can delete connections

HubSpot API + MCP

1. Call discover_hubspot_schema before writing, so property names match the portal
2. Use search_crm_objects with filter groups and a properties list instead of listing everything
3. Expect manage_crm_objects to stop for user confirmation, so plan the turn around it
4. Read policyName on a 429 to tell a 10-second burst from the daily cap
5. Ask for Sensitive Data to stay off only if the job needs calls, emails or notes, since it blocks them