yacrum-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
yacrum-mcp
An MCP server for the Yacrum CRM. It lets Claude Desktop, Claude Code and other MCP clients search, create and update your CRM records, log activity, read the pipeline and the forecast, and summarise a deal. Your own AI does the thinking; this server only fetches from Yacrum.
It talks to Yacrum through its public REST API, with your own API key. A key acts as the member it was made for, with that member's role: the server can do exactly what that person could do in the app, and nothing more. A read key cannot change anything.
Setup
In Yacrum, an Admin opens Administration → API Keys, makes a key for you, and copies it. The key is shown only once. Choose Read and write if you want the AI to create and update records.
Add the server to your MCP client.
Claude Desktop
Edit claude_desktop_config.json:
{
"mcpServers": {
"yacrum": {
"command": "npx",
"args": ["-y", "yacrum-mcp"],
"env": {
"YACRUM_API_KEY": "yk_your_key_here",
"YACRUM_URL": "https://yacrum--yacrum.us-central1.hosted.app"
}
}
}
}Claude Code
claude mcp add yacrum --env YACRUM_API_KEY=yk_your_key_here -- npx -y yacrum-mcpVariable | |
| Required. A key from Administration → API Keys ( |
| Your Yacrum address. Defaults to the Yacrum staging site. |
Related MCP server: pipedrive-mcp
Tools
Tool | What it does |
| The workspace, the member the key acts as, its scope, and this month's API usage |
| Companies, contacts, opportunities and open leads by name |
| Companies |
| Contacts |
| Deals |
| A deal's Sales Health (G on track, Y at risk, R off track) and the note saying why, always together |
| A note on a company, contact, deal or lead: a call, a meeting, a decision |
| Tasks, optionally on a record, with a due date; complete or reopen one |
| Quotes, with their lines, totals, taxes and status (read only) |
| What is worth doing now, and why: quiet and expiring quotes, stale and slipping deals, lost and paused deals to revisit, dormant customers, renewals and referrals |
| Hide a signal from yourself until a day, or bring it back. Works with a read key |
| The address to BCC on a draft so the sent mail is logged, and the workspace's style guide |
| What changed since last week's pipeline snapshot: new, advanced, slipped, won, lost and the totals then and now |
| The stages, and open deals by stage (totals kept per currency) |
| Bookings, billings and cash by month (Admin, Management and Sales) |
| A deal's score: answers, scores, percent of its template's maximum, and tier |
| The workspace's scoring templates: questions, choices, weights, tiers, maximums and stage gates |
| Score a deal, or change its answers or template (switching template deletes the old answers) |
| The stage gates ahead of a deal, met or not, and the next stage when all of its gates are met |
| Everything about one deal in one read, to summarise it or draft to it, with the CASL consent facts for its contacts |
| The seven Profiles, and how far the workspace is set up (Admin) |
| Apply a Profile. |
| Show or hide Quotes, Forecast, Deal team and CASL. Hiding authorizes nothing (Admin) |
| The spreadsheet templates, and what each CRM's export looks like (Admin) |
| Upload an export or spreadsheet from this computer, save the answers, and see what the import would do. Nothing reaches the workspace's records (Admin) |
| Run an import (call again while |
There is also a summarize_deal prompt that reads a deal's context and asks for a summary and next steps.
Every tool says what it does, so your AI client can ask before a write:
Kind | Tools | Annotations |
Reads |
| read only |
Additions |
| not destructive |
Updates |
| not destructive, idempotent |
A stage move |
| destructive: a lost or paused stage records a reason and changes the forecast. A stage gate can refuse it (409 |
Scoring |
| destructive, idempotent: switching a scored deal's template deletes its answers |
Setup and imports |
| destructive: each changes the workspace's stages or many records at once. Show the diff or preview and get a yes first |
Files for an import are read from your computer. preview_import takes full paths and reads only regular .csv
and .xlsx files, never through a symlink, at most 12 files, 10 MB each and 25 MB together. Anything else is refused
before a byte is read or sent.
Yacrum never sends email. To draft outreach, pair this server with your own Gmail or Microsoft 365
connector: draft in your mailbox with the BCC from get_outreach_settings, and log it with log_activity.
The Claude plugin
plugin/ packages this server with five sales routines: morning signals, re-engaging a deal,
an account pulse before a meeting, the weekly pipeline review and qualifying an opportunity. Outreach is drafted
in your own mailbox with your workspace's logging address in BCC. Nothing is sent.
It also has two for an Admin: /yacrum:setup interviews you, shows a Profile's diff and applies it once you agree,
and /yacrum:import brings in a Pipedrive or HubSpot export or a spreadsheet. Both need an Admin's write key and a
local server, so they work in Claude Code and Claude Desktop, and not on claude.ai on the web.
claude plugin marketplace add david-loadman/yacrum-mcp
claude plugin install yacrum@yacrumSetup, including the Gmail and Microsoft 365 connectors and email logging, is in
plugin/SETUP.md.
Limits
Every call counts against your workspace plan's monthly API calls. One key may make 120 requests a minute. An import uses about one call per 200 records. When a limit is reached, Yacrum's refusal says so, and the server passes it on to the AI as a tool error.
Releasing
npm releases are staged and need a maintainer's approval with 2FA. A version goes live in three steps:
Bump the version in
package.jsonandVERSIONinsrc/index.ts, and merge.Publish a GitHub release tagged
v<version>. The Stage on npm workflow checks that the tag matches, builds, tests, and runsnpm stage publish. It has no token: it authenticates through npm's trusted publishing, and npm attaches provenance automatically.Approve it with 2FA, either on the package's page at npmjs.com, or with:
npm stage list npm stage approve <stage-id>npm stage reject <stage-id>discards a staged version instead.
The trusted publisher on npmjs.com (user david-loadman, repository yacrum-mcp, workflow publish.yml)
does not allow npm publish. Leave it that way: a compromised workflow can then stage a version but never
ship one.
Development
npm install
npm test # against a fake Yacrum; nothing leaves the machine
npm run build
YACRUM_API_KEY=yk_… node dist/index.jsThe Yacrum API is described at <YACRUM_URL>/api/v1/openapi.json.
⚠️ npx yacrum-mcp fails inside a clone of this repository, including when Claude Code is started in it:
npm resolves yacrum-mcp to the local package instead of the published one, and finds no command to run. Start
Claude Code, or npx, from another directory, or point the MCP config at node <clone>/dist/index.js.
Licence
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Native MCP access to CRM contacts, organizations, deals and tasks with user permissions.
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Read deals, persons, organizations, activities and pipelines; create and update CRM records.
CRM1
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceWraps the Pipedrive REST API v1 to manage deals, contacts, and search across CRM entities via MCP tools.287 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables reading and managing Pipedrive CRM records—deals, people, organizations, activities, and notes—over MCP, including searching, writing, and moving deals through pipelines.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to search and view CRM customers, deals, contracts, tasks, calendars, and outbound jobs, and to propose opt-in write actions that require human approval in the CRM.Apache 2.0
- AlicenseBqualityBmaintenanceEnables MCP clients to read and manage CRM data through the SalesSuite API — contacts and contact persons, deals and pipelines, notes, calls, emails, forms, action button executions and webhook subscriptions — with toolset filtering, a read-only mode, and support for tenant-specific custom properties.53347 npmMIT