Livespace CRM MCP Server

io.github.proAutomator/livespace-crm-mcp

Unofficial local MCP server for Livespace CRM with read tools and guarded writes.

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "livespace-crm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp@0.1.2"
      ],
      "env": {
        "MCP_PORT": "3020",
        "LIVESPACE_SUBDOMAIN": "<your LIVESPACE_SUBDOMAIN>",
        "LIVESPACE_API_KEY": "<your LIVESPACE_API_KEY>",
        "LIVESPACE_API_SECRET": "<your LIVESPACE_API_SECRET>",
        "MCP_AUTH_TOKEN": "<your MCP_AUTH_TOKEN>",
        "LIVESPACE_MCP_ENABLE_WRITES": "false",
        "MCP_REQUEST_STATE_KEY": "<your MCP_REQUEST_STATE_KEY>"
      }
    }
  }
}
Environment variables
  • MCP_PORTLoopback port used by the local MCP server.
  • LIVESPACE_SUBDOMAINrequiredBare Livespace workspace subdomain, without protocol or domain suffix.
  • LIVESPACE_API_KEYrequiredsecretPer-user Livespace API key.
  • LIVESPACE_API_SECRETrequiredsecretPer-user Livespace API secret.
  • MCP_AUTH_TOKENrequiredsecretRandom bearer token of at least 32 bytes, also sent by the client.
  • LIVESPACE_MCP_ENABLE_WRITESExpose write tools. Keep false unless writes are deliberately required.
  • MCP_REQUEST_STATE_KEYsecretRandom HMAC key of at least 32 bytes. Required when writes are enabled.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.1.2
Registry
active
Published
10/5/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that Livespace CRM MCP Server is listed here — it’s also the link we check for a free listing.

Livespace CRM MCP Server — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-proautomator-livespace-crm-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Livespace CRM MCP Server — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Livespace CRM MCP Server — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-proautomator-livespace-crm-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.