nimble-crm-mcp
MCP server for the Nimble CRM API — manage contacts, deals, notes, tasks, and tags from Claude Code or any MCP client.
Installation
pip install nimble-crm-mcp
Or install from source:
git clone https://github.com/cphoskins/nimble-crm-mcp.git
cd nimble-crm-mcp
pip install -e .
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
Add to your Claude Code MCP settings (~/.claude/settings.json or project .claude/settings.json):
{
"mcpServers": {
"nimble-crm": {
"command": "nimble-crm-mcp",
"env": {
"NIMBLE_API_KEY": "your-api-key-here"
}
}
}
}
Generic MCP Client
{
"mcpServers": {
"nimble-crm": {
"command": "python",
"args": ["-m", "nimble_crm_mcp.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)
- delete_contacts — Delete one or more contacts by ID
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
- 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
Deals
- list_deals — List all deals with pagination
- create_deal — Create a deal with name, amount, stage, probability, etc.
- update_deal — Update deal fields
- delete_deal — Delete a deal
Metadata
- list_contact_fields — List all contact field metadata (tabs, groups, fields, types)
Account
- get_myself — Get current authenticated user info
Development
# Clone and install
git clone https://github.com/cphoskins/nimble-crm-mcp.git
cd nimble-crm-mcp
pip install -e .
# Run tests (no credentials needed — all mocked)
pytest tests/ -v
# Run the server locally
NIMBLE_API_KEY=your-key nimble-crm-mcp
License
MIT
Release files for nimble-crm-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nimble_crm_mcp-0.1.0.tar.gz | 19.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nimble_crm_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:29.5 kB
Release files / nimble_crm_mcp-0.1.0.tar.gz
| Download URL | nimble_crm_mcp-0.1.0.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
990c9f7ebf9aef6978dac877db11e2c4bd5427985673ece8aed4fc88afe475a0
|
|
BLAKE2b-256 checksum How to use checksums |
8d2d1803bf3f811f939fd3930f5841ff17565af917ef56121831564e3e66b03b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 3, 2026.
Transparency logRelease files / nimble_crm_mcp-0.1.0-py3-none-any.whl
| Download URL | nimble_crm_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8c2c6b6669039851bb1d6e3d4cf14ea3b2e33c4fed91efa645c69d4c2e83275
|
|
BLAKE2b-256 checksum How to use checksums |
537b44f9c40ac6838a6a22c7e31aac21f8697754645f15d57ce76c0f3cc0985a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 3, 2026.
Transparency log