Less Annoying CRM MCP by usefulapi

Every tool targets a distinct resource and action, with descriptions explicitly clarifying boundaries (e.g., list_pipelines is setup, list_pipeline_items is data; events vs tasks are time-based vs date-based). The related group tools—get_contact_groups, list_groups, and list_contacts_in_group—are clearly differentiated. No two tools appear to do the same thing.

All names use a consistent lacrm_ prefix and snake_case verb_noun pattern, which makes the set predictable. There are minor inconsistencies in verb choice: add vs create (add_contact_to_group vs create_contact) and edit vs update (edit_contact/edit_task vs update_pipeline_item), but these do not seriously hinder recognition.

At 23 tools, the server sits in the heavy range (16–25) for a single CRM integration. While each tool is plausibly useful, several read-only list/get tools could be consolidated or made optional, making the surface feel slightly bloated for the domain.

The tool set covers creation, editing, and reading for contacts, tasks, and pipeline items, plus supplementary reads for events, notes, groups, users, and custom fields. However, there are no delete or remove operations anywhere (contacts, notes, events, tasks, group memberships, pipeline items), and notes/events lack update/edit tools, leaving notable lifecycle gaps.