Livespace CRM MCP Server

Livespace CRM MCP Server

Unofficial MCP server for Livespace CRM. It exposes 11 intent-shaped tools instead of mirroring the raw API and targets the stateless Streamable HTTP transport in MCP spec 2026-07-28.

Version 0.1.1 is available on npm, in the official MCP Registry, and as a GitHub Release.

The v1 implementation is complete in this repository. It has six read tools and five optional write tools, read-only defaults, bounded API access, sanitized errors and an elicitation-first confirmation flow. Use a test Livespace account while evaluating it.

Why this shape?

Livespace's RPC API has about 80 methods, but it does not provide sorting, aggregation or a direct operation for setting a deal stage. The server groups those lower-level calls into tasks an MCP client can use safely:

• discovery before IDs are used;
• bounded search, record reads and analysis;
• batch previews before writes;
• per-item outcomes and post-write checks;
• explicit handling of Livespace-specific stage moves and notifications.

Tools

movedealsto_stage works by checking and unchecking process steps because Livespace has no "set stage" call. A deal stands at its furthest checked step. A backward move therefore unchecks completed steps and can change the historical meaning of those checkboxes.

notify_user validates the recipient and can add a deep link to a record. Livespace provides no notification read-back, so the tool reports a successful request as dispatched, never as delivered.

Requirements

Use a dedicated Livespace API user with only the permissions this MCP needs. Every API operation inherits that user's permissions.

• A Livespace plan with API access, currently Automation or higher.
• One Livespace API key and secret from Account settings -> API -> Users.

Bun.serve and has no Node.js or Cloudflare Workers adapter.

• Bun 1.3.14 or newer (bun.sh). The current server uses

The v1 deployment model is single-user: one Livespace credential pair and, if enabled, one MCP bearer token protects the server. There is no OAuth or multi-user credential routing.

Install and run from npm

Shortened. The full README is on GitHub.