Nimble MCP server
Nimble in any MCP client, through Memtro: Nimble does not publish this server. Memtro's Nimble connector reads Nimble through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Nimble CRM contacts (people and companies) with their fields and notes, the activity timeline of tasks, calls and events, and the deal pipelines; can add notes to contacts and deals, create tasks, create, update and delete contacts and deals, and set a contact's tags.
Reads
nimble_list_contactsNimble contacts, people or companies: name, email, title, company, tags, owner.nimble_get_contactOne Nimble contact by id with all its non-private fields by name (email, title, company, website, description…nimble_list_contact_notesNotes on one Nimble contact: author, text (cut to 800 characters) and dates.nimble_list_activitiesThe Nimble activity timeline: tasks, calls, meetings and events, either still to come (pending) or already past…nimble_list_deal_pipelinesNimble deal pipelines with their stages in order (ids, names, default probability, and whether a stage is a won or lost one)…
Acts, when you ask
These change something in Nimble. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
nimble_add_contact_noteAdds a note to a Nimble contact — what was discussed or learned.nimble_create_taskCreates a task in Nimble, optionally linked to contacts and with a due date.nimble_add_deal_noteAdds a note to a Nimble deal: a title and an optional body.nimble_create_contactCreates a Nimble contact: a person (first or last name required) or a company (company name required), with optionally an email, title…nimble_update_contactChanges fields on a Nimble contact by id: a person's first and last name, company (works_at) and title, a company's name, an email…nimble_set_contact_tagsSets a Nimble contact's tags to exactly the list given, removing any tag not in it…nimble_create_dealCreates a Nimble deal with a name in a pipeline or at a stage (ids from nimble_list_deal_pipelines), and optionally an amount, probability…nimble_update_dealEdits a Nimble deal by id: name, amount, probability, description, stage (within its pipeline), owner, currency, tags or contacts.nimble_delete_contactPermanently deletes a Nimble contact by id; the API documents no restore.nimble_delete_dealPermanently deletes a Nimble deal by id; the API documents no restore.
Connect it
First connect Nimble on Dashboard → Connections, then add Memtro to your client once. The Nimble tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Nimble connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What do we know about Priya Nair at Brightwave Ltd?
- › Which calls and meetings are coming up with Acme?
- › What were the last notes on Dan Fletcher?
- › Create a task to send BigCo the onboarding plan by Friday
- › Move the Globex renewal deal to the proposal stage at 12,000 pounds
Questions
- Is this an official Nimble MCP server?
- No. It is Memtro's MCP server with Memtro's Nimble connector behind it: the connector reads Nimble through its API with the credentials you connect on Dashboard → Connections, and Nimble publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Nimble?
- Only when you ask, and only what it has been granted: add a note to a contact; create a task, optionally linked to contacts; add a note to a deal; create a contact (person or company); update a contact's fields; set a contact's tags to a given list; create a deal; update a deal; delete a contact permanently; delete a deal permanently. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.