Log inSubmit server
Livespace CRM MCP Server logo

Livespace CRM MCP Server

Connects MCP clients to Livespace CRM for bounded reads, analysis, and guarded record updates.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Livespace CRM MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "livespace-crm-mcp-server": {
      "command": "bunx",
      "args": [
        "livespace-crm-mcp"
      ],
      "env": {
        "LIVESPACE_SUBDOMAIN": "YOUR_VALUE_HERE",
        "LIVESPACE_API_KEY": "YOUR_VALUE_HERE",
        "LIVESPACE_API_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

bunx livespace-crm-mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

Livespace CRM MCP Server MCP server connects MCP clients to Livespace CRM through a local Streamable HTTP endpoint. It groups CRM operations into bounded tools for metadata discovery, searching, record and activity reads, aggregation, and optional writes. Reach for it when an agent needs controlled access to Livespace data without exposing the raw RPC API. The deployment uses one Livespace credential pair and can require a bearer token when write tools are enabled.

Use cases

  • Search Livespace contacts, companies, and deals
  • Inspect CRM metadata before choosing record IDs
  • Analyze bounded CRM windows
  • Create or update CRM records in batches
  • Move deals between process stages with safeguards

Key features

  • Bounded CRM search and record reads
  • Metadata discovery for users, processes, and dictionaries
  • Named aggregation over bounded windows
  • Guarded batch writes with validation
  • Deal-stage movement using process-step diffs
  • Streamable HTTP transport

Tools11

What Livespace CRM MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~330 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · livespace-crm-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads312Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed11Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Livespace CRM MCP Server works

What Livespace CRM MCP Server MCP server does

Livespace CRM MCP Server MCP server exposes Livespace CRM operations as 11 intent-focused MCP tools. The read tools cover server and CRM health, metadata dictionaries, searches, record retrieval, activity history, and bounded analysis. The write tools can create or update persons, companies, deals, and tasks; add public notes or phone calls; move deals between stages; and send one in-app notification.

The design is intended for agents that need CRM context before acting. Metadata can provide process, user, group, source, task, product, and current-user information before an operation uses an ID. Search results can include record links, while full deal reads can include checked process steps and status-related details.

How it works

Livespace CRM MCP Server MCP server runs as a local Bun application and serves the Streamable HTTP transport at http://127.0.0.1:3020/mcp by default. A client sends JSON-RPC requests to that endpoint while the process remains running. The package does not expose stdio and does not provide a Node.js or Cloudflare Workers adapter.

Read operations are bounded. Searches and analyses report when their source window is truncated, and activity or record reads impose limits per request. Batch writes also have caps: creation and updates allow up to 10 items, activity logging allows up to 15 entries, and deal-stage changes allow up to 10 deals.

Deal-stage changes are implemented by checking or unchecking process steps because Livespace does not provide a direct stage-setting operation. Backward moves require an explicit allowlist and may alter the historical interpretation of completed steps. Notification requests are reported as dispatched; Livespace does not provide delivery read-back.

Setup and configuration

To run Livespace CRM MCP Server MCP server, use Bun 1.3.14 or newer and a Livespace plan with API access, currently Automation or higher. Create a dedicated Livespace API user with only the permissions required by the server, then provide these variables:

  • LIVESPACE_SUBDOMAIN: the account subdomain without protocol or .livespace.io.
  • LIVESPACE_API_KEY: the API key for the Livespace user.
  • LIVESPACE_API_SECRET: the API secret for the Livespace user.

Install and start the published package with bunx livespace-crm-mcp; version 0.1.2 can be pinned explicitly. Keep credentials in a protected .env file. Configure the MCP client with the local /mcp URL. If write tools are enabled, set MCP_AUTH_TOKEN and have the client send it as a Bearer token. The deployment uses one credential pair and does not support OAuth or multiple user-specific credential routes.

Limitations and notes

Livespace CRM MCP Server MCP server starts in read-only mode as the recommended evaluation posture, with writes treated as optional. Use a test Livespace account while evaluating it. Run health first, then use crm_metadata to resolve users, processes, stages, groups, or dictionary IDs before making dependent requests.

Clients must handle both structuredContent and the short text result. Empty search and activity pages can contain a cursor hint, so an empty page should not be treated as proof that no records match until the cursor is followed. Returned null or empty values do not prove that a CRM field is empty or inaccessible. Invalid input parameters are rejected, and invalid date filters are checked before an API call.

The server is unofficial and inherits the permissions of its configured Livespace API user. Notifications are rate-limited to five per 10 minutes and one per recipient per minute. Tasks do not have record URLs, and locally generated phrase-search links may be empty when an ID cannot produce a usable destination.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Livespace CRM MCP Server

Livespace CRM MCP Server is an MCP server that connects AI clients to Livespace CRM through a local Streamable HTTP endpoint. Its main tools check health, inspect metadata, search and read CRM records, retrieve activity, analyze bounded windows, create or update records, log activities, move deals, and send notifications.

Install it with Bun by running `bunx livespace-crm-mcp`; Bun 1.3.14 or newer is required. Set the three Livespace credential variables in a protected `.env` file, then connect an MCP client to `http://127.0.0.1:3020/mcp`.

It requires `LIVESPACE_SUBDOMAIN`, `LIVESPACE_API_KEY`, and `LIVESPACE_API_SECRET`. `MCP_AUTH_TOKEN` is additionally needed when write tools are enabled so the client can authenticate with a Bearer token.

No, it supports Streamable HTTP rather than stdio. Start the Bun process separately and configure the MCP client with the server URL. Clients that only accept stdio are not supported.

Yes, but backward movement requires an explicit allowlist. The tool changes checked process steps because Livespace has no direct stage-setting method, and unchecking completed steps can affect the historical meaning of those steps.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLivespace CRM MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/livespace-crm-mcp-server?style=directory)](https://allmcps.com/mcp/livespace-crm-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/livespace-crm-mcp-server"><img src="https://allmcps.com/api/badge/livespace-crm-mcp-server?style=directory" alt="Livespace CRM MCP Server on AllMCPs" /></a>