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

1. In Yacrum, an Admin opens Customization → 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

Related MCP server: mcp-pipedrive

Tools

There is also a summarize_deal prompt that reads a deal's context and asks for a summary and next steps.

Limits

Every call counts against your workspace plan's monthly API calls. One key may make 120 requests a minute. When a limit is reached, Yacrum's refusal says so, and the server passes it on to the AI as a tool error.

Development

npm install
npm test        # against a fake Yacrum; nothing leaves the machine
npm run build
YACRUM_API_KEY=yk_… node dist/index.js

The Yacrum API is described at <YACRUM_URL>/api/v1/openapi.json.

Licence

MIT