Copper MCP by usefulapi

Each tool targets a distinct resource-action pair (e.g., create/get/search per entity, plus specialized activity and reference-list tools). While some list/search operations are similar in spirit, they operate on clearly different resources (e.g., people vs users vs activities) and the descriptions reinforce the boundaries. No two tools appear to do the same thing.

All tool names follow a consistent snake_case verb_noun pattern with a uniform `copper_` prefix (e.g., copper_create_company, copper_search_people, copper_log_activity). The verbs used (create, get, search, list, log, update) are standard and applied predictably. No mixing of conventions or vague names.

With 22 tools, the set is on the heavy side for the rubric (16–25 feels heavy), though each tool maps to a specific Copper REST operation. The near-uniform create/get/search pattern across five core entities plus several reference and activity tools means the count is not bloated, but it exceeds the typical well-scoped range. A more consolidated surface (e.g., fewer list tools or optional parameters) could reduce cognitive load.

The surface covers create, get, and search for companies, leads, opportunities, people, and tasks, plus activity logging and reference lists. However, update and delete are missing for nearly every entity except a single update_person tool, which is an inconsistent and notable gap for a CRM integration. Agents can read and create records but will hit dead ends when trying to modify or remove most records.