Method CRM MCP by usefulapi

The generic table tools (method_query_records, method_create_record, method_update_record, method_get_record) intentionally overlap with the dedicated wrappers (method_search_customers, method_list_invoices, method_list_activities, method_create_customer, method_create_activity), but the descriptions explicitly state which to prefer ("For customers/leads and activities use the dedicated tools"), which resolves most ambiguity. Residual confusion remains between method_search_customers and a filtered method_query_records on Customer, and between method_list_invoices and method_query_records with `apply`, but an agent can pick correctly.

Every tool follows the same method_<verb>_<noun> snake_case pattern with a consistent verb vocabulary (count, create, get, list, query, search, update). No mixed conventions or stray naming styles.

16 tools is at the upper edge but each maps to a real need: a generic table layer (list_tables, get_table_fields, query_records, count_records, get_record, create_record, update_record) plus focused CRM helpers for the most common tables. A few helpers (list_invoices, search_customers, list_activities) are convenience wrappers over the generic layer, but they add filter semantics worth the surface.

Create/read/update and discovery are well covered, but the server explicitly has no delete operation, and child line records (e.g. InvoiceLine) cannot be created through method_create_record, so building a complete invoice is a dead end. File listing/download exists but there is no upload or attach operation.