mcp-nimble-crm
This MCP server lets you manage Nimble CRM data and metadata through MCP tools.
Look up account/user info and list, search, retrieve, create, update, delete, or bulk-delete contacts.
Manage contact notes and tags, create tasks, and list pending/past activities.
Inspect and manage contact field metadata: tabs, groups, custom fields, and presentation settings.
Manage lead/contact pipelines: list pipelines, move leads between stages, mark leads won/lost, and undo transitions.
Manage v2 deals: list/get/create/update/delete deals, query deals won last month, and manage deal tags, notes, and overdue activities.
Manage deal fields/columns and deal pipelines/stages, including create/update/delete, archive/unarchive, lost reasons, and pipeline deal views by stage or owner.
List and create message drafts.
Run it as a single-user stdio MCP server or as a hosted multi-tenant OAuth service with encrypted per-user Nimble API keys.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-nimble-crm show me deals won last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-nimble-crm
MCP server for the Nimble CRM API — manage contacts, deals, deal pipelines, notes, tasks, tags, fields metadata, and message drafts from Claude, Cursor, Zed, or any MCP client.
This project began as a fork of cphoskins/nimble-crm-mcp (MIT licensed). It has since been rewritten against Nimble's official v1/v2 OpenAPI reference (readthedocs/Redocly spec) to correct and extend coverage: deals and deal pipelines now correctly target the v2 API (/api/v2/deals), with full pipeline/stage/field/group/choice management, deal tags, deal notes, and lead pipeline transitions — plus the full v1 contacts-fields-metadata CRUD surface (tabs, groups, fields, choices) that the upstream project didn't cover. See NIMBLE_API_REFERENCE.md for the endpoint-by-endpoint source notes.
Scope note: binary file upload/download endpoints (deal files, contact avatar uploads via Azure Blob SDK) are intentionally not implemented — they require a separate multipart/Azure Blob integration outside a JSON REST client's scope.
Note on naming: this is unrelated to
nimble-js-mcpon npm, which is for Nimbleway (a web-scraping/data API company) — a different "Nimble" entirely.
Installation
Install from source:
git clone https://github.com/meshachjackson/mcp-nimble-crm.git
cd mcp-nimble-crm
pip install -e .Requires Python 3.11 or newer.
Not on PyPI yet.
pip install mcp-nimble-crmdoes not work today — the package name is reserved inpyproject.tomlandserver.json, but no release has been published. Install from source until then. See Releasing.
Related MCP server: nimble-crm-mcp
Hosted mode (claude.ai custom connector)
This server also runs as a multi-tenant remote MCP service: deploy it once, and every Claude account (web, mobile, Desktop, Code) connects via OAuth, each user pasting their own Nimble API key a single time on a setup page. See REMOTE.md.
Environment variables the hosted mode reads (names only):
NIMBLE_MCP_PUBLIC_URL: required; the public HTTPS base URL of the deployment, used for the OAuth issuer and setup links.NIMBLE_MCP_ENCRYPTION_KEY: required; the Fernet key that encrypts each user's stored Nimble key.NIMBLE_MCP_DB: optional; the SQLite file path (defaults tonimble-remote.db).HOST: optional; the bind address (defaults to0.0.0.0).PORT: optional; the bind port (defaults to8000).NIMBLE_MCP_REMOTE: switches on hosted mode; themcp-nimble-crm-remoteentrypoint sets it, so you do not set it yourself.NIMBLE_API_KEY: single-user stdio mode only; leave it unset in hosted mode (it is only a fallback if no per-user key resolves).
No shared Nimble API key is stored on the server: each user's own key is stored encrypted (Fernet) in the SQLite database, and the encryption key lives only in the deploy environment.
Configuration
Get your Nimble API Key
Log in to Nimble
Go to Settings > API Tokens (or visit the API Access guide)
Generate an API key
Claude Code
Register the server with the claude CLI:
claude mcp add nimble-crm --scope user -e NIMBLE_API_KEY=your-api-key-here -- mcp-nimble-crm--scope user makes it available in every project; use --scope project to
write a shared .mcp.json instead. Verify with claude mcp get nimble-crm.
Claude Code stores MCP servers in ~/.claude.json (user scope) or a project
.mcp.json — not in settings.json. Prefer the CLI over editing either
file by hand.
Generic MCP Client
{
"mcpServers": {
"nimble-crm": {
"command": "python",
"args": ["-m", "mcp_nimble_crm.server"],
"env": {
"NIMBLE_API_KEY": "your-api-key-here"
}
}
}
}Available Tools
Contacts
list_contacts — List contacts with optional keyword search and record type filter
search_contacts — Advanced search with field-level operators (is, contains, range, etc.)
get_contact — Get a single contact by ID with all fields and tags
create_contact — Create a person or company contact with name, email, phone, tags
update_contact — Update contact fields (merge or replace mode)
list_contact_ids — List contact IDs only (faster than a full listing)
get_contacts_by_ids — Standard listings for up to 30 explicit IDs
delete_contact — Delete a single contact, with
regularorforcedeletiondelete_contacts — Delete one or more contacts by ID
delete_contacts_by_query — Bulk-delete contacts matching a query (needs bulk delete permission)
Notes
list_notes — List notes for a specific contact
get_note — Get a single note by ID
create_note — Create a note attached to one or more contacts
create_contact_note — Create a note attached to a single contact
update_note — Update an existing note
delete_note — Delete a note
Tags
replace_tags — Replace all tags on a contact (full replace, not additive)
Tasks
create_task — Create a task with subject, notes, due date, and related contacts
Contacts Fields Metadata
list_contact_fields — List all contact field metadata (tabs, groups, fields, types)
create_contact_field / update_contact_field / delete_contact_field — Manage custom contact fields
create_contact_field_group — Create a fields group
create_contact_field_tab — Create a fields tab
Contact Pipelines (Leads)
list_contact_pipelines — List lead/contact pipelines visible to the user
move_lead_to_stage — Move a lead into a pipeline stage
exit_lead_successful / exit_lead_unsuccessful — Exit a lead as won/lost
undo_lead_transition — Undo a recent won/lost transition
Activities & Tasks
list_activities — List pending or past activities, filterable by contact/deal
create_task — Create a task with subject, notes, due date, related contacts/deals, and tags
Deals (v2)
list_deals — List the current user's deals
get_deal — Get a single deal by ID
create_deal — Create a deal (pipeline, stage, fields_values, owner, currency, tags)
update_deal — Update deal fields, pipeline, stage, owner, or tags
delete_deal — Delete a deal
get_won_deals_last_month — Sum/count of deals won in the last month
Deal Tags & Notes
list_deal_tags / add_tags_to_deals / rename_deal_tag / delete_deal_tag
create_deal_note / update_deal_note / delete_deal_note
list_deal_overdue_activities — Overdue activities for a deal
Deal Fields
list_deal_fields — Standard + per-pipeline deal fields
list_deal_column_catalogue — Deal column/column-group catalogue
Deal Pipelines (v2)
list_deal_pipelines / get_deal_pipeline / create_deal_pipeline / update_deal_pipeline / delete_deal_pipeline
list_pipeline_deals_by_stage / list_pipeline_deals_by_owner
archive_deal_pipeline / unarchive_deal_pipeline / add_pipeline_lost_reason
create_pipeline_stage / update_pipeline_stage / archive_pipeline_stage
Messages
list_message_drafts — List draft messages
create_message_draft — Create a draft message linked to recipients
Account
get_myself — Get current authenticated user info
Development
# Clone and install
git clone https://github.com/meshachjackson/mcp-nimble-crm.git
cd mcp-nimble-crm
pip install -e .
# Run tests (no credentials needed — all mocked)
pytest tests/ -v
# Run integration tests against a live account (creates + cleans up real records)
NIMBLE_API_KEY=your-key pytest tests/test_integration.py -v
# Run the server locally
NIMBLE_API_KEY=your-key mcp-nimble-crmThe integration tests in tests/test_integration.py are skipped when NIMBLE_API_KEY is not set, so pytest tests/ is safe to run without credentials.
Releasing
./release.sh <version>This bumps the version in pyproject.toml, mcp_nimble_crm/__init__.py, and server.json, commits, tags, and pushes. Publishing a GitHub Release for that tag triggers the PyPI publish workflow (.github/workflows/publish.yml).
License
MIT — see LICENSE. Includes portions originally from cphoskins/nimble-crm-mcp, also MIT licensed.
Available Tools
62 toolsadd_pipeline_lost_reasonA
Add a new lost-reason option to a pipeline.
Args: pipeline_id: The Nimble pipeline ID. reason: Reason description.
Inputs: reason (required), pipeline_id (required). Returns: result
add_tags_to_dealsA
Assign tags to all deals matching an advanced search query.
Args: query_json: JSON-encoded advanced search query for deals. tags: Comma-separated tags to assign.
Inputs: tags (required), query_json (required). Returns: result
archive_deal_pipelineC
Archive a deal pipeline.
Args: pipeline_id: The Nimble pipeline ID.
Inputs: pipeline_id (required). Returns: result
archive_pipeline_stageB
Archive a pipeline stage.
Args: pipeline_id: The Nimble pipeline ID. stage_id: The stage ID to archive.
Inputs: stage_id (required), pipeline_id (required). Returns: result
create_contactA
Create a new contact (person or company).
Args: record_type: 'person' or 'company'. first_name: First name (for person records). last_name: Last name (for person records). company_name: Company name (required for company records). email: Email address. email_modifier: Email type: 'work', 'personal', or 'other'. phone: Phone number. phone_modifier: Phone type: 'work', 'home', 'mobile', 'main', 'other'. tags: Comma-separated tags (max 5 on creation).
Inputs: record_type (required), tags, email, phone, +5 more. Returns: result
create_contact_fieldA
Create a new custom contact field.
Args: name: Field name (1-50 chars). field_kind: One of 'string', 'long_string', 'choice', 'number', 'datetime', 'boolean', 'address', 'user'. tab_id: ID of the tab this field belongs to. presentation_json: JSON string describing presentation (required for number/datetime fields, e.g. {"number_type": "integer"}). group_id: Optional group ID to nest the field under. insert_after: Optional field/group ID to insert after. multiples: Whether this field can hold multiple values.
Inputs: name (required), tab_id (required), field_kind (required), group_id, +3 more. Returns: result
create_contact_field_groupA
Create a new contact fields group.
Args: name: Group name (1-50 chars). tab_id: ID of the tab this group belongs to. logo_id: Optional logo ID to display. insert_after: Optional field/group ID to insert after.
Inputs: name (required), tab_id (required), logo_id, insert_after. Returns: result
create_contact_field_tabB
Create a new contact fields tab.
Args: tab_name: Tab name (1-50 chars). contact_types: Comma-separated types: 'person', 'company'. insert_after: Optional tab ID to insert after.
Inputs: tab_name (required), insert_after, contact_types. Returns: result
create_contact_noteA
Create a note attached to a single contact.
Args: contact_id: The Nimble contact ID. note: Full note text. note_preview: Short preview. Defaults to the full note if omitted.
Inputs: note (required), contact_id (required), note_preview. Returns: result
create_dealA
Create a new deal in Nimble CRM (deals_v2).
Args: pipeline_id: Pipeline to place the deal in. stage_id: Stage within that pipeline. fields_values_json: JSON string keyed by field id, each a list of {"value": ...} dicts. Must include the deal name field; probability is required unless the stage has a default. Example: {"63760e653af0e748fe48366a": [{"value": "Big Deal"}]} owner_id: User ID who owns the deal. currency: ISO-4217 3-letter currency code. tags: Comma-separated tags to apply.
Inputs: stage_id (required), pipeline_id (required), fields_values_json (required), tags, +2 more. Returns: result
create_deal_noteA
Create a note attached to a deal.
Args: deal_id: The Nimble deal ID. title: Note title (1-256 chars). body: Note body text.
Inputs: title (required), deal_id (required), body. Returns: result
create_deal_pipelineB
Create a new deal pipeline in Nimble CRM.
Args: name: Pipeline name (1-200 chars). description: Pipeline description. color: Pipeline color. default_currency: ISO-4217 3-letter currency code.
Inputs: name (required), color, description, default_currency. Returns: result
create_message_draftA
Create a draft message in Nimble CRM.
Args: subject: Message subject. body: Message body text. to: Comma-separated recipient email addresses.
Inputs: body (required), subject (required), to. Returns: result
create_noteA
Create a note attached to one or more contacts.
Args: contact_ids: Comma-separated contact IDs (1-10). note: Full note text (can contain HTML). note_preview: Short plain-text preview. If empty, first 100 chars of note are used.
Inputs: note (required), contact_ids (required), note_preview. Returns: result
create_pipeline_stageB
Create a new stage within a deal pipeline.
Args: pipeline_id: The Nimble pipeline ID. name: Stage name. description: Stage description. expected_days: Expected number of days a deal spends in this stage. default_probability: Default win probability (0-100) for deals entering this stage.
Inputs: name (required), pipeline_id (required), description, expected_days, +1 more. Returns: result
create_taskB
Create a task in Nimble CRM.
Args: subject: Task title. notes: Additional task notes. related_contacts: Comma-separated contact IDs to associate. related_deals: Comma-separated deal IDs to associate. due_date: Due date, e.g. YYYY-MM-DDTHH:MM:SS. tags: Comma-separated tags to apply.
Inputs: subject (required), tags, notes, due_date, +2 more. Returns: result
delete_contactA
Delete a single contact by ID.
Args: contact_id: The Nimble contact ID. deletion_method: 'regular' (errors if relations block deletion) or 'force' (delete despite relations). cleanup_email_lists: If true, also remove matching email list entries.
Inputs: contact_id (required), deletion_method, cleanup_email_lists. Returns: result
delete_contact_fieldA
Delete a custom contact field.
Args: field_id: The field ID. preflight_checks: If true, errors if the field is in use by any contacts instead of deleting it.
Inputs: field_id (required), preflight_checks. Returns: result
delete_contactsA
Delete one or more contacts by ID.
Args: contact_ids: Comma-separated contact IDs to delete.
Inputs: contact_ids (required). Returns: result
delete_contacts_by_queryA
Bulk-delete contacts matching an advanced query or keyword list.
Requires bulk delete permission for the authenticated user.
Args: query_json: JSON-encoded advanced search query. If provided, record_type is ignored by Nimble. keyword: Comma-separated list of keywords; contacts whose fields contain any of these values will be deleted. record_type: 'person', 'company', or 'all'. preflight_checks: If true, verify contacts are editable first.
Inputs: keyword, query_json, record_type, preflight_checks. Returns: result
delete_dealB
Delete a deal by ID.
Args: deal_id: The Nimble deal ID.
Inputs: deal_id (required). Returns: result
delete_deal_noteC
Delete a note from a deal.
Args: deal_id: The Nimble deal ID. note_id: The note ID.
Inputs: deal_id (required), note_id (required). Returns: result
delete_deal_pipelineA
Delete a deal pipeline by ID. All deals in it will also be deleted!
Args: pipeline_id: The Nimble pipeline ID.
Inputs: pipeline_id (required). Returns: result
delete_deal_tagC
Delete/unlink a deal tag from all deals.
Args: tag_name: Tag name to delete.
Inputs: tag_name (required). Returns: result
delete_noteB
Delete a note by ID.
Args: note_id: The Nimble note ID.
Inputs: note_id (required). Returns: result
exit_lead_successfulA
Exit a lead from a pipeline as won.
Args: lead_id: The contact/lead ID. pipeline_id: The pipeline ID. notes: Optional notes about the transition.
Inputs: lead_id (required), pipeline_id (required), notes. Returns: result
exit_lead_unsuccessfulB
Exit a lead from a pipeline as lost.
Args: lead_id: The contact/lead ID. pipeline_id: The pipeline ID. notes: Optional notes about the transition. lost_reason: Optional lost reason.
Inputs: lead_id (required), pipeline_id (required), notes, lost_reason. Returns: result
get_contactA
Get a single contact by ID with all fields and tags.
Args: contact_id: The Nimble contact ID.
Inputs: contact_id (required). Returns: result
get_contacts_by_idsA
Return standard contact listings for up to 30 explicit IDs.
Args: contact_ids: Comma-separated contact IDs (max 30).
Inputs: contact_ids (required). Returns: result
get_dealA
Get a single deal by ID.
Args: deal_id: The Nimble deal ID.
Inputs: deal_id (required). Returns: result
get_deal_pipelineA
Get a single deal pipeline by ID.
Args: pipeline_id: The Nimble pipeline ID.
Inputs: pipeline_id (required). Returns: result
get_myselfA
Get current authenticated Nimble user info and account details.
Inputs: no named parameters. Returns: result
get_noteA
Get a single note by ID.
Args: note_id: The Nimble note ID.
Inputs: note_id (required). Returns: result
get_won_deals_last_monthA
Get the sum and count of deal amounts won in the last month.
Inputs: no named parameters. Returns: result
list_activitiesA
List activities (pending or past) matching filters.
Args: direction: 'pending' (future) or 'past' (old) activities. limit: Max activities to return. contact_ids: Comma-separated contact IDs to filter by. deal_ids: Comma-separated deal IDs to filter by. completed: True for only completed, False for uncompleted.
Inputs: direction (required), limit, deal_ids, completed, +1 more. Returns: result
list_contact_fieldsA
List all contact field metadata — tabs, groups, and fields.
Returns the complete schema of available contact fields including custom fields, their types, and valid modifiers.
Inputs: no named parameters. Returns: result
list_contact_idsA
List contact IDs only (faster than a full contact listing).
Args: record_type: Filter by 'person', 'company', or 'all'. keyword: Simple search across indexed fields. per_page: Results per page (default 30). page: Page number (starts at 1).
Inputs: page, keyword, per_page, record_type. Returns: result
list_contact_pipelinesA
List contact/lead pipelines visible to the requesting user.
Inputs: no named parameters. Returns: result
list_contactsA
List contacts with optional keyword search.
Args: record_type: Filter by 'person', 'company', or 'all'. keyword: Simple search across indexed fields (name, email, etc). per_page: Results per page (default 30). page: Page number (starts at 1).
Inputs: page, keyword, per_page, record_type. Returns: result
list_deal_column_catalogueB
List the deal column/column-group catalogue for the user.
Inputs: no named parameters. Returns: result
list_deal_fieldsB
List deal standard fields and per-pipeline fields.
Inputs: no named parameters. Returns: result
list_deal_overdue_activitiesA
List a deal's overdue activities, most-overdue first.
Args: deal_id: The Nimble deal ID. limit: Max activities to return.
Inputs: deal_id (required), limit. Returns: result
list_deal_pipelinesA
List all deal pipelines and their stages in Nimble CRM.
Inputs: no named parameters. Returns: result
list_dealsA
List all of the current user's deals.
Args: sort: Sort spec as ":", e.g. "name:asc". limit: Max deals to return.
Inputs: sort, limit. Returns: result
list_deal_tagsA
List deal tags, optionally filtered by prefix.
Args: starts_with: Only return tags starting with this string. limit: Max tags to return.
Inputs: limit, starts_with. Returns: result
list_message_draftsA
List draft messages in Nimble CRM.
Args: recipients: Comma-separated recipient filter. page: Page number (starts at 0). per_page: Results per page.
Inputs: page, per_page, recipients. Returns: result
list_notesA
List notes for a specific contact.
Args: contact_id: The Nimble contact ID. per_page: Results per page (default 5). page: Page number (starts at 1).
Inputs: contact_id (required), page, per_page. Returns: result
list_pipeline_deals_by_ownerA
List a pipeline's deals grouped by owner.
Args: pipeline_id: The Nimble pipeline ID. sort: Sort spec as ":". limit: Max deals per owner.
Inputs: pipeline_id (required), sort, limit. Returns: result
list_pipeline_deals_by_stageA
List a pipeline's deals grouped by stage.
Args: pipeline_id: The Nimble pipeline ID. sort: Sort spec as ":". limit: Max deals per stage.
Inputs: pipeline_id (required), sort, limit. Returns: result
move_lead_to_stageC
Move a lead (contact) into a pipeline stage.
Args: lead_id: The contact/lead ID. pipeline_id: The pipeline ID. stage_id: The target stage ID.
Inputs: lead_id (required), stage_id (required), pipeline_id (required). Returns: result
rename_deal_tagA
Rename a deal tag.
Args: tag_name: Current tag name. new_tag: New tag name.
Inputs: new_tag (required), tag_name (required). Returns: result
replace_tagsA
Replace all tags on a contact.
WARNING: This is a full replace — tags not in the list will be REMOVED. To add a tag, first get current tags with get_contact, then include all existing tags plus the new one.
Args: contact_id: The Nimble contact ID. tags: Comma-separated list of tags to set.
Inputs: tags (required), contact_id (required). Returns: result
search_contactsA
Search contacts with an advanced NSE query.
Args: query_json: JSON string with search criteria. Format: {"and": [{"field name": {"operator": "value"}}]} Operators: is, is_not, contain, not_contain, starts_with, is_empty, in, range, gt, gte, lt, lte, in_the_last, not_in_the_last, day_month_range. Example: {"and": [{"first name": {"is": "Jack"}}, {"company name": {"contain": "Acme"}}]} per_page: Results per page (default 30). page: Page number (starts at 1).
Inputs: query_json (required), page, per_page. Returns: result
unarchive_deal_pipelineB
Un-archive a deal pipeline.
Args: pipeline_id: The Nimble pipeline ID.
Inputs: pipeline_id (required). Returns: result
undo_lead_transitionC
Undo a recent won/lost transition for a lead.
Args: lead_id: The contact/lead ID. pipeline_id: The pipeline ID.
Inputs: lead_id (required), pipeline_id (required). Returns: result
update_contactA
Update an existing contact's fields.
Args: contact_id: The Nimble contact ID. fields_json: JSON string of fields to update. Format: {"field name": [{"value": "val", "modifier": "mod"}]} Example: {"email": [{"value": "new@example.com", "modifier": "work"}]} Set a field to an empty list to remove all values for it. replace: If true, replaces all values for each field type. If false, merges with existing values.
Inputs: contact_id (required), fields_json (required), replace. Returns: result
update_contact_fieldA
Update an existing custom contact field.
Args: field_id: The field ID. name: New field name. presentation_json: JSON string for new presentation settings. group_id: New group ID to move the field into. tab_id: New tab ID. insert_after: Field/group ID to move this field after.
Inputs: field_id (required), name, tab_id, group_id, +2 more. Returns: result
update_dealA
Update an existing deal.
Args: deal_id: The Nimble deal ID. fields_values_json: JSON string keyed by field id, each a list of {"value": ...} dicts. Send an empty list to clear a field. pipeline_id: Move the deal to a different pipeline. stage_id: Move the deal to a different stage. owner_id: Reassign the deal owner. tags: Comma-separated new tag list (replaces existing tags).
Inputs: deal_id (required), tags, owner_id, stage_id, +2 more. Returns: result
update_deal_noteB
Update a deal note.
Args: deal_id: The Nimble deal ID. note_id: The note ID. title: New title. body: New body text.
Inputs: deal_id (required), note_id (required), body, title. Returns: result
update_deal_pipelineA
Update an existing deal pipeline's name, description, or color.
Args: pipeline_id: The Nimble pipeline ID. name: New pipeline name. description: New pipeline description. color: New pipeline color.
Inputs: pipeline_id (required), name, color, description. Returns: result
update_noteA
Update an existing note.
Args: note_id: The Nimble note ID. contact_ids: Comma-separated contact IDs (1-10). note: Updated full note text. note_preview: Updated short preview. If empty, first 100 chars of note are used.
Inputs: note (required), note_id (required), contact_ids (required), note_preview. Returns: result
update_pipeline_stageA
Update an existing pipeline stage.
Args: pipeline_id: The Nimble pipeline ID. stage_id: The stage ID to update. name: New stage name. description: New stage description. expected_days: New expected days (pass -1 to leave unchanged). default_probability: New default probability 0-100 (pass -1 to leave unchanged).
Inputs: stage_id (required), pipeline_id (required), name, description, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 62 tools
Most tools target distinct resource-action pairs, but a few like create_note/create_contact_note and get_contacts_by_ids/get_contact could cause misselection. Descriptions generally clarify the differences, though the sheer number of tools increases the chance of confusion.
All tool names consistently use snake_case with a verb_noun or verb_noun_qualifier pattern. Even exceptions like exit_lead_successful and get_won_deals_last_month follow the verb-first convention.
At 62 tools, the server is far beyond the typical well-scoped range. While the broad CRM domain partly justifies the count, the sheer number creates unwieldy navigation and includes redundant variants like delete_contact, delete_contacts, and delete_contacts_by_query.
Contact, deal, pipeline, and note coverage is robust, but tasks and activities only support create/list with no update/delete, and message drafts lack update/delete/send. These are notable lifecycle gaps for a CRM.
Related MCP Connectors
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.
MCP server for SmartAgent CRM: leads, tasks, sales pipelines, property listings
MCP server for Getfly CRM — customers, opportunities, orders, tickets and tasks.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides an interface to the Copper CRM API for managing contacts, companies, activities, and opportunities. It enables users to search for people, log meetings or notes, and track sales deals directly through MCP-compatible clients.9MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Nimble CRM API, enabling management of contacts, deals, notes, tasks, and tags through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the HubSpot CRM API with tools for managing contacts, companies, deals, tickets, and CRM workflows. Generated with MCPForge. Sensitive operations can be protected with permissions, audit logs, and approval workflows.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Pipedrive API v2, enabling management of deals, persons, organizations, products, activities, and pipelines through natural language in MCP clients like Cursor and Claude Desktop.14 npm2MIT