Skip to content
Back to search

yacrum

MarketplaceWorks with Claude CodeGitHub

Yacrum CRM for Claude: the MCP server and the sales routines that run on it

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/david-loadman--yacrum-mcp/badge.svg)](/listings/david-loadman--yacrum-mcp)

HTML

<a href="/listings/david-loadman--yacrum-mcp"><img src="/api/listings/david-loadman--yacrum-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. 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. 2. 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-mcp

| Variable | | |---|---| | `YACRUM_API_KEY` | Required. A key from Administration → API Keys (`yk_…`). | | `YACRUM_URL` | Your Yacrum address. Defaults to the Yacrum staging site. |

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "name": "yacrum",
  3. "description": "Yacrum CRM for Claude: the MCP server and the sales routines that run on it",
  4. "owner": {
  5. "name": "David Loadman",
  6. "url": "https://github.com/david-loadman"
  7. },
  8. "plugins": [
  9. {
  10. "name": "yacrum",
  11. "source": "./plugin",
  12. "description": "Morning signals, re-engaging an opportunity, an account pulse before a meeting, the weekly pipeline review, and qualifying an opportunity, on your Yacrum data. For Admins: setting up a workspace step by step, choosing the Qualification questions and gates, building a Fit template, and importing. Drafts go to your own mailbox; nothing is sent.",
  13. "version": "0.7.0"
  14. }
  15. ]
  16. }
README.md · README · 168 lines
  1. # yacrum-mcp
  2. An [MCP](https://modelcontextprotocol.io) server for the **Yacrum** CRM. It lets Claude Desktop, Claude Code
  3. and other MCP clients search, create and update your CRM records, log activity, read the pipeline and the
  4. forecast, and summarize a deal. Your own AI does the thinking; this server only fetches from Yacrum.
  5. It talks to Yacrum through its public REST API, with **your own API key**. A key acts as the member it was
  6. made for, with that member's role: the server can do exactly what that person could do in the app, and
  7. nothing more. A *read* key cannot change anything.
  8. ## Setup
  9. 1. In Yacrum, an Admin opens **Administration → API Keys**, makes a key for you, and copies it. The key is
  10. shown only once. Choose **Read and write** if you want the AI to create and update records.
  11. 2. Add the server to your MCP client.
  12. ### Claude Desktop
  13. Edit `claude_desktop_config.json`:
  14. ```json
  15. {
  16. "mcpServers": {
  17. "yacrum": {
  18. "command": "npx",
  19. "args": ["-y", "yacrum-mcp"],
  20. "env": {
  21. "YACRUM_API_KEY": "yk_your_key_here",
  22. "YACRUM_URL": "https://yacrum--yacrum.us-central1.hosted.app"
  23. }
  24. }
  25. }
  26. }
  27. ```
  28. ### Claude Code
  29. ```bash
  30. claude mcp add yacrum --env YACRUM_API_KEY=yk_your_key_here -- npx -y yacrum-mcp
  31. ```
  32. | Variable | |
  33. |---|---|
  34. | `YACRUM_API_KEY` | Required. A key from Administration → API Keys (`yk_…`). |
  35. | `YACRUM_URL` | Your Yacrum address. Defaults to the Yacrum staging site. |
  36. ## Tools
  37. | Tool | What it does |
  38. |---|---|
  39. | `whoami` | The workspace, the member the key acts as, its scope, and this month's API usage |
  40. | `search` | Companies, contacts, opportunities and open leads by name |
  41. | `list_companies`, `get_company`, `create_company`, `list_company_types` | Companies |
  42. | `list_contacts`, `create_contact` | Contacts |
  43. | `list_opportunities`, `create_opportunity`, `update_opportunity`, `move_opportunity_stage` | Deals |
  44. | `set_sales_health` | A deal's Sales Health (G on track, Y at risk, R off track) and the note saying why, always together. Yacrum proposes one from Qualification; it is written only on the user's approval |
  45. | `log_activity` | A note on a company, contact, deal or lead: a call, a meeting, a decision |
  46. | `create_action_item`, `list_action_items`, `update_action_item` | Tasks, optionally on a record, with a due date; complete or reopen one |
  47. | `list_quotes`, `get_quote` | Quotes, with their lines, totals, taxes and status (read only) |
  48. | `get_signals` | 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 |
  49. | `snooze_signal`, `unsnooze_signal` | Hide a signal from yourself until a day, or bring it back. Works with a read key |
  50. | `get_outreach_settings` | The address to BCC on a draft so the sent mail is logged, and the workspace's style guide |
  51. | `pipeline_changes` | What changed since last week's pipeline snapshot: new, advanced, slipped, won, lost and the totals then and now |
  52. | `get_pipeline`, `pipeline_summary` | The stages, and open deals by stage (totals kept per currency) |
  53. | `forecast` | Bookings, billings and cash by month (Admin, Management and Sales) |
  54. | `qualification_score` | A deal's two scores, read apart. Qualification: twelve questions (Need, Economic impact, Access to authority, Timeline) answered 0–3 with notes and the people each is about, the score out of 100, the weakest letter and the Sales Health proposal. Fit: answers and their notes, percent of its template's maximum, and tier |
  55. | `list_scoring_templates` | The Qualification questions as the workspace has them (on or off, help text, stage gates) and the Sales Health thresholds; and the Fit templates: questions, choices, weights, tiers and maximums |
  56. | `score_opportunity` | Save a deal's Qualification answers (merged by key), its Fit answers and notes, or both (switching Fit template deletes the old Fit answers) |
  57. | `update_qualification_settings` | Switch Qualification questions on or off, word their help, set or clear a stage gate on one, and change the Sales Health thresholds and late stage (Admin) |
  58. | `stage_readiness` | The stage gates ahead of a deal (Qualification questions and sent quotes), met or not, and the next stage when all of its gates are met. Fit never gates a stage |
  59. | `deal_context` | Everything about one deal in one read, with both scores (`qualification` and `fit`), to summarize it or draft to it, with the CASL consent facts for its contacts |
  60. | `list_scoring_starters`, `get_workspace_setup` | The three Fit starters (Products, Services, Products and services), and how far the workspace is set up (Admin) |
  61. | `apply_setup` | Apply the workspace's setup: the opportunity team, stages, products, forecast, quote settings, the Qualification questions that apply, and a Fit template. `dryRun` is required: `true` answers with the diff and changes nothing (Admin) |
  62. | `set_workspace_features` | Show or hide Quotes, Forecast, the opportunity team, CASL, Products and services, and Scoring. Hiding authorizes nothing (Admin) |
  63. | `get_quote_document` | An external quote's own document: its link, or a short-lived address for its PDF |
  64. | `get_import_templates` | The spreadsheet templates, and what each CRM's export looks like (Admin) |
  65. | `preview_import` | 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) |
  66. | `import_records`, `get_import_status`, `undo_import` | Run an import (call again while `more` is true), see where it has got, and undo it, all or none (Admin) |
  67. | `add_stage`, `update_stage`, `reorder_stages`, `delete_stage` | Add an open stage (at a position, if asked), change, reorder or remove one, with the pipeline editor's rules (Admin) |
  68. | `create_scoring_template`, `set_default_scoring_template` | Create a whole Fit template (questions, choices, tiers; no stage gates), and make one the default. Templates are never edited in place: customize by creating a changed copy (Admin) |
  69. | `list_skus`, `create_sku` | The SKUs, and add one, priced in the workspace's base currency (Admin to add) |
  70. | `list_leads`, `create_lead`, `update_lead` | Leads, open or converted, and add or change one |
  71. There is also a **`summarize_deal`** prompt that reads a deal's context and asks for a summary and next steps.
  72. Every tool says what it does, so your AI client can ask before a write:
  73. | Kind | Tools | Annotations |
  74. |---|---|---|
  75. | Reads | `whoami`, `search`, every `list_…` and `get_…`, `pipeline_summary`, `forecast`, `qualification_score`, `deal_context`, `pipeline_changes`, `stage_readiness` | read only |
  76. | Additions | `create_company`, `create_contact`, `create_opportunity`, `create_action_item`, `log_activity`, `preview_import` | not destructive |
  77. | Updates | `update_opportunity`, `set_sales_health`, `update_action_item`, `snooze_signal`, `unsnooze_signal`, `set_workspace_features` | not destructive, idempotent |
  78. | A stage move | `move_opportunity_stage` | **destructive**: a lost or paused stage records a reason and changes the forecast. A stage gate can refuse it (409 `stage_gate`); an Admin or Management member may override it with `overrideReason` |
  79. | Scoring | `score_opportunity` | **destructive**, idempotent: switching a scored deal's Fit template deletes its Fit answers |
  80. | Qualification settings | `update_qualification_settings` | **destructive**, idempotent: a stage gate holds every opportunity, and clearing one forgets it |
  81. | Setup and imports | `apply_setup`, `import_records`, `undo_import` | **destructive**: each changes the workspace's stages or many records at once. Show the diff or preview and get a yes first |
  82. **Files for an import are read from your computer.** `preview_import` takes full paths and reads only regular `.csv`
  83. and `.xlsx` files, never through a symlink, at most 12 files, 10 MB each and 25 MB together. Anything else is refused
  84. before a byte is read or sent.
  85. Yacrum never sends email. To draft outreach, pair this server with your own Gmail or Microsoft 365
  86. connector: draft in your mailbox with the BCC from `get_outreach_settings`, and log it with `log_activity`.
  87. ## The Claude plugin
  88. [`plugin/`](./plugin) packages this server with six sales routines: morning signals, re-engaging a deal,
  89. an account pulse before a meeting, the weekly pipeline review, qualifying an opportunity and reconciling an external quote. Outreach is drafted
  90. in your own mailbox with your workspace's logging address in BCC. Nothing is sent.
  91. It also has `/yacrum:reconcile-quote`, which checks an external quote's own document against its line items, and three for an Admin: `/yacrum:setup` walks you through the full setup (the opportunity team, stages, products, the forecast, quotes, Qualification and Fit), explaining each, and saves only once you agree;
  92. `/yacrum:scoring-template` settles which Qualification questions apply and any stage gates, and builds a Fit template with you;
  93. and `/yacrum:import` brings in a Pipedrive or HubSpot export or a spreadsheet. All three need an Admin's write key and a
  94. local server, so they work in Claude Code and Claude Desktop, and not on claude.ai on the web.
  95. ```bash
  96. claude plugin marketplace add david-loadman/yacrum-mcp
  97. claude plugin install yacrum@yacrum
  98. ```
  99. Setup, including the Gmail and Microsoft 365 connectors and email logging, is in
  100. [`plugin/SETUP.md`](./plugin/SETUP.md).
  101. ## Limits
  102. Every call counts against your workspace plan's monthly API calls. One key may make 120 requests a minute.
  103. An import uses about one call per 200 records.
  104. When a limit is reached, Yacrum's refusal says so, and the server passes it on to the AI as a tool error.
  105. ## Releasing
  106. npm releases are **staged** and need a maintainer's approval with 2FA. A version goes live in three steps:
  107. 1. **Bump the version** in `package.json` and `VERSION` in `src/index.ts`, and merge.
  108. 2. **Publish a GitHub release** tagged `v<version>`. The *Stage on npm* workflow checks that the tag matches,
  109. builds, tests, and runs `npm stage publish`. It has no token: it authenticates through npm's trusted
  110. publishing, and npm attaches provenance automatically.
  111. 3. **Approve it with 2FA**, either on the package's page at npmjs.com, or with:
  112. ```bash
  113. npm stage list
  114. npm stage approve <stage-id>
  115. ```
  116. `npm stage reject <stage-id>` discards a staged version instead.
  117. The trusted publisher on npmjs.com (user `david-loadman`, repository `yacrum-mcp`, workflow `publish.yml`)
  118. does **not** allow `npm publish`. Leave it that way: a compromised workflow can then stage a version but never
  119. ship one.
  120. ## Development
  121. ```bash
  122. npm install
  123. npm test # against a fake Yacrum; nothing leaves the machine
  124. npm run build
  125. YACRUM_API_KEY=yk_… node dist/index.js
  126. ```
  127. The Yacrum API is described at `<YACRUM_URL>/api/v1/openapi.json`.
  128. ⚠️ **`npx yacrum-mcp` fails inside a clone of this repository**, including when Claude Code is started in it:
  129. npm resolves `yacrum-mcp` to the local package instead of the published one, and finds no command to run. Start
  130. Claude Code, or `npx`, from another directory, or point the MCP config at `node <clone>/dist/index.js`.
  131. ## License
  132. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.