Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Livespace CRM MCP Server

by proAutomatorversion 0.1.3i★ 0iRuns on your computer
Registry nameio.github.proAutomator/livespace-crm-mcp

How to install

What it does

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

  • Connects Runs on your computer
  • Account or key Needs LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY · 2 settings to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES)
  • Category Marketing & social media

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Livespace CRM MCP Server for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "livespace-crm": { "command": "npx", "args": [ "-y", "livespace-crm-mcp" ], "env": { "LIVESPACE_SUBDOMAIN": "your-value", "LIVESPACE_API_KEY": "your-value", "LIVESPACE_API_SECRET": "your-value", "MCP_AUTH_TOKEN": "your-value", "LIVESPACE_MCP_ENABLE_WRITES": "false", "MCP_REQUEST_STATE_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY, LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Livespace CRM MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Livespace CRM MCP Server key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Livespace CRM MCP Server site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LIVESPACE_SUBDOMAIN Bare Livespace workspace subdomain, without protocol or domain suffix.
    • LIVESPACE_MCP_ENABLE_WRITES Expose write tools. Keep false unless writes are deliberately required. · default false

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "livespace-crm": {
          "command": "npx",
          "args": [
            "-y",
            "livespace-crm-mcp"
          ],
          "env": {
            "LIVESPACE_SUBDOMAIN": "your-value",
            "LIVESPACE_API_KEY": "your-value",
            "LIVESPACE_API_SECRET": "your-value",
            "MCP_AUTH_TOKEN": "your-value",
            "LIVESPACE_MCP_ENABLE_WRITES": "false",
            "MCP_REQUEST_STATE_KEY": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Livespace CRM MCP Server and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Livespace CRM MCP Server or shows a Livespace CRM MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_PORT Loopback port used by the local MCP server. · default 3020

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Livespace CRM MCP Server yet

Livespace CRM MCP Server runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Livespace CRM MCP Server

  • You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time)
  • You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time)
  • You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time)

B · Others in Marketing & social media that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Livespace CRM MCP Server for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user livespace-crm --env LIVESPACE_SUBDOMAIN=your-value --env LIVESPACE_API_KEY=your-value --env LIVESPACE_API_SECRET=your-value --env MCP_AUTH_TOKEN=your-value --env LIVESPACE_MCP_ENABLE_WRITES=false --env MCP_REQUEST_STATE_KEY=your-value -- npx -y livespace-crm-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY, LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Livespace CRM MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Livespace CRM MCP Server key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Livespace CRM MCP Server site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LIVESPACE_SUBDOMAIN Bare Livespace workspace subdomain, without protocol or domain suffix.
    • LIVESPACE_MCP_ENABLE_WRITES Expose write tools. Keep false unless writes are deliberately required. · default false

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user livespace-crm --env LIVESPACE_SUBDOMAIN=your-value --env LIVESPACE_API_KEY=your-value --env LIVESPACE_API_SECRET=your-value --env MCP_AUTH_TOKEN=your-value --env LIVESPACE_MCP_ENABLE_WRITES=false --env MCP_REQUEST_STATE_KEY=your-value -- npx -y livespace-crm-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Livespace CRM MCP Server listed as connected

  7. Try it

    Use Livespace CRM MCP Server and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Livespace CRM MCP Server or shows a Livespace CRM MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_PORT Loopback port used by the local MCP server. · default 3020

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Livespace CRM MCP Server for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "livespace-crm": { "command": "npx", "args": [ "-y", "livespace-crm-mcp" ], "env": { "LIVESPACE_SUBDOMAIN": "your-value", "LIVESPACE_API_KEY": "your-value", "LIVESPACE_API_SECRET": "your-value", "MCP_AUTH_TOKEN": "your-value", "LIVESPACE_MCP_ENABLE_WRITES": "false", "MCP_REQUEST_STATE_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY, LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Livespace CRM MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Livespace CRM MCP Server key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Livespace CRM MCP Server site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LIVESPACE_SUBDOMAIN Bare Livespace workspace subdomain, without protocol or domain suffix.
    • LIVESPACE_MCP_ENABLE_WRITES Expose write tools. Keep false unless writes are deliberately required. · default false

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Livespace CRM MCP Server settings, LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY, LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Livespace CRM MCP Server and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Livespace CRM MCP Server or shows a Livespace CRM MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_PORT Loopback port used by the local MCP server. · default 3020

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Livespace CRM MCP Server key (create it on the maker’s site) · 2 setting(s) to fill in (LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Livespace CRM MCP Server for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "livespace-crm": { "type": "stdio", "command": "npx", "args": [ "-y", "livespace-crm-mcp" ], "env": { "LIVESPACE_SUBDOMAIN": "your-value", "LIVESPACE_API_KEY": "your-value", "LIVESPACE_API_SECRET": "your-value", "MCP_AUTH_TOKEN": "your-value", "LIVESPACE_MCP_ENABLE_WRITES": "false", "MCP_REQUEST_STATE_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY, LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Livespace CRM MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Livespace CRM MCP Server key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Livespace CRM MCP Server site ↗

  3. Fill in 2 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LIVESPACE_SUBDOMAIN Bare Livespace workspace subdomain, without protocol or domain suffix.
    • LIVESPACE_MCP_ENABLE_WRITES Expose write tools. Keep false unless writes are deliberately required. · default false

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Livespace CRM MCP Server settings, LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY, LIVESPACE_SUBDOMAIN, LIVESPACE_MCP_ENABLE_WRITES is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Livespace CRM MCP Server and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Livespace CRM MCP Server or shows a Livespace CRM MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_PORT Loopback port used by the local MCP server. · default 3020

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Livespace CRM MCP Server💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user livespace-crm --env LIVESPACE_SUBDOMAIN=your-value --env LIVESPACE_API_KEY=your-value --env LIVESPACE_API_SECRET=your-value --env MCP_AUTH_TOKEN=your-value --env LIVESPACE_MCP_ENABLE_WRITES=false --env MCP_REQUEST_STATE_KEY=your-value -- npx -y livespace-crm-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "livespace-crm": {
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp"
      ],
      "env": {
        "LIVESPACE_SUBDOMAIN": "your-value",
        "LIVESPACE_API_KEY": "your-value",
        "LIVESPACE_API_SECRET": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "LIVESPACE_MCP_ENABLE_WRITES": "false",
        "MCP_REQUEST_STATE_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "livespace-crm": {
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp"
      ],
      "env": {
        "LIVESPACE_SUBDOMAIN": "your-value",
        "LIVESPACE_API_KEY": "your-value",
        "LIVESPACE_API_SECRET": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "LIVESPACE_MCP_ENABLE_WRITES": "false",
        "MCP_REQUEST_STATE_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "livespace-crm": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp"
      ],
      "env": {
        "LIVESPACE_SUBDOMAIN": "your-value",
        "LIVESPACE_API_KEY": "your-value",
        "LIVESPACE_API_SECRET": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "LIVESPACE_MCP_ENABLE_WRITES": "false",
        "MCP_REQUEST_STATE_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • MCP_PORT env
    Loopback port used by the local MCP server.
  • LIVESPACE_SUBDOMAIN required env
    Bare Livespace workspace subdomain, without protocol or domain suffix.
  • LIVESPACE_API_KEY secret required env
    Per-user Livespace API key.
  • LIVESPACE_API_SECRET secret required env
    Per-user Livespace API secret.
  • MCP_AUTH_TOKEN secret required env
    Random bearer token of at least 32 bytes, also sent by the client.
  • LIVESPACE_MCP_ENABLE_WRITES required env
    Expose write tools. Keep false unless writes are deliberately required.
  • MCP_REQUEST_STATE_KEY secret required env
    Random HMAC key of at least 32 bytes. Required when writes are enabled.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
44/wk
Connection
Runs on your computer
Transport
streamable-http
Latest versioni
0.1.3
Published to registryi
Nov 9, 2026
Code last changedi
Nov 14, 2026
Maker
proAutomator
Packages
npm: livespace-crm-mcp
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 15, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account proAutomator, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 3959 servers in this category
  • Published to the registry more recently than 83% of the other 3959 servers in this category
  • Basic checks equal to or better than 100% of the other 3959 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Livespace CRM MCP Server safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LIVESPACE_API_KEY, LIVESPACE_API_SECRET, MCP_AUTH_TOKEN, MCP_REQUEST_STATE_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (0.1.3) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Relaticle

Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.

by relaticleGrowing★ 1.8KUpdated 2 days ago

Runs in the cloud✓ service owner · relaticle.com

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

by ChatbotXIOGrowing★ 1.1K Stars for the whole repoUpdated 9 days ago

Runs in the cloud✓ service owner · chatbotx.io

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

by betterlyticsGrowing★ 180Updated 3 months ago

Runs in the cloud✓ service owner · betterlytics.io

BibiGPT YouTube Video Summarizer

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

by JimmyLvGrowing★ 141Updated 18 days ago

Runs in the cloud✓ service owner · bibigpt.co

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.3 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

ToolModePurpose and bound
healthReadChecks the server; checkLivespace: true also makes one lightweight Livespace API call.
crm_metadataReadReturns nine dictionary sections, including processes, users, groups, sources, task dictionaries, products and the current user. Optional userQuery filters users by name or email before the 500-row cap.
search_crmReadFinds persons, companies or deals, with record links even in lightweight results. Sorted deal searches use one 200-record sort window and report truncation.
get_recordsReadReads one record kind and up to 25 ids; walls for at most 5 persons, companies or deals.
get_activityReadReads one record wall, one bounded CRM feed range or bounded task pages per call.
analyzeReadRuns one named aggregation over bounded windows and reports whether its source window was truncated.
create_recordsWriteCreates persons, companies, deals or tasks. Up to 10 items per call, with exact-match contact deduplication by default.
update_recordsWriteUpdates persons, companies, deals or tasks. Up to 10 items per call.
log_activitiesWriteAdds public notes or phone calls. Up to 15 notes or calls per call.
move_deals_to_stageWriteMoves deals by applying the minimal process-step diff. Up to 10 items per call; backward moves need an explicit allowlist.
notify_userWriteDispatches one in-app notification, limited to 5 per 10 minutes and 1 per recipient per minute.

move_deals_to_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

  • A Livespace plan with API access, currently Automation or higher.
  • One Livespace API key and secret from Account settings -> API -> Users. Use a dedicated Livespace API user with only the permissions this MCP needs. Every API operation inherits that user's permissions.
  • Bun 1.3.14 or newer (bun.sh). The current server uses Bun.serve and has no Node.js or Cloudflare Workers adapter.

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

The package is distributed through npm's public registry, but Bun is its runtime. You do not need Node.js or the npm CLI to run it.

For a first evaluation, create a private working directory outside a Git repository. Add a .env file there with your own Livespace credentials:

LIVESPACE_SUBDOMAIN=

LIVESPACE_API_KEY= LIVESPACE_API_SECRET=

Fill the three empty values, protect the file, then start the published package:

chmod 600 .env

bunx livespace-crm-mcp

The default endpoint is http://127.0.0.1:3020/mcp. Keep the process running while your MCP client is connected. Start in read-only mode, call health, then use crm_metadata before any operation that needs a user, process, stage, group or dictionary ID.

bunx downloads the package from npm and caches it locally. To pin this release, run bunx livespace-crm-mcp@0.1.3.

Connect an MCP client

Configure a client that supports Streamable HTTP with this server URL:

{

"url": "http://127.0.0.1:3020/mcp" }

The exact configuration field differs between clients. Set MCP_AUTH_TOKEN and configure the client to send Authorization: Bearer , even on loopback. Authentication is mandatory when write tools are enabled.

This package exposes Streamable HTTP, not stdio. Some MCP clients can connect to the local URL but cannot launch bunx for you, so start the command in a separate terminal. Clients that accept only stdio are not supported yet. Each HTTP request must contain one JSON-RPC message; top-level batch arrays are rejected before dispatch.

Read results

Record data goes in structuredContent, with a short text summary. Check that your host passes both channels to its model. Empty search_crm and get_activity pages include the same hint in both channels; follow a returned cursor before concluding that no records match. An empty crm_metadata user search also carries a hint in both channels. See the host compatibility checks for tested versions, confirmation limits and a synthetic fixture you can run without CRM access.

Use crm_metadata with userQuery to find a user by part of their name or email. For example, {"userQuery":"synthetic@example.test"} returns only the users section. The query must have 2-100 characters after trimming. Matching ignores case but preserves accents; it does not search team names. If you supply sections, it must include users; other requested sections remain unfiltered. Omitting the query preserves the usual section selection.

The tool returns all matching users up to 500, in dictionary order. Resolve multiple matches before choosing an owner or write recipient. totalItems counts matches in the cached dictionary before that cap. Check asOf, ageMs and stale, especially when a user is missing from the results.

Phrase-search links are generated locally from the API ID, without a separate check of each destination. An unusable ID produces an empty url. Record reads and filtered searches retain the URL supplied by Livespace, including at detail: "minimal" for persons, companies and deals; that URL can also be empty. Tasks have no record URL.

Fields excluded by detail are omitted. An empty or null returned value means the response supplies no value; it does not establish an empty CRM field or an access restriction. For deal value and probability, distinguish numeric zero from null. A zero budget alone does not show whether someone set it intentionally. Some counters and flags normalize missing data to zero or false, so those defaults do not prove an explicitly stored value.

Deal value comes from whichever field the account fills. Accounts that use budget lines keep the line sum in value. Other accounts report value: 0 on every deal and keep the value shown in the UI in value_final. The server returns a non-zero value_final when there is one and value otherwise, so search_crm, get_records and analyze agree with the UI on both kinds of account.

At detail: "full", deals also carry checkedSteps (the process steps marked done, with stage and step ids and names) and the won, lost and outdated reason names and notes. A reopened deal can keep an earlier lost reason, so check status first. search_crm filters accept createdFrom and createdTo for persons, companies and deals, and modifiedFrom for deals, all as inclusive YYYY-MM-DD dates. Livespace ignores a date it cannot read and returns every record, so the server rejects invalid dates before calling it. The deal status filter takes open (the default), won, lost, outdated or all.

All tools reject unsupported input parameters. Correct the arguments when the client reports an input validation error.

Configuration

VariablePurpose
LIVESPACE_SUBDOMAINAccount subdomain without protocol or .livespace.io.
LIVESPACE_API_KEY / LIVESPACE_API_SECRETCredentials for one Livespace user.
MCP_PORTServer port. Default: 3020.
MCP_BIND_HOSTBind address. Default: 127.0.0.1.
MCP_AUTH_TOKENRandom bearer token of at least 32 bytes. Required for writes and on a non-loopback bind; recommended for every server.
LIVESPACE_MCP_ENABLE_WRITESSet to true to expose write tools. Default: false.
LIVESPACE_MCP_READ_ONLYEmergency kill-switch. true removes and blocks write tools even when enabled above.
MCP_REQUEST_STATE_KEYIndependent random secret of at least 32 bytes used to sign write confirmations. Required when writes are enabled.
MCP_ALLOW_UNBOUND_WRITE_CONFIRMATIONUnsafe compatibility mode for clients without form elicitation. Default: false.
MCP_ALLOWED_HOSTSHost-header allowlist for DNS-rebinding protection. Required on a non-loopback bind.
MCP_ALLOWED_ORIGIN_HOSTNAMESOptional additional browser-origin hostnames. On a non-loopback bind it defaults to MCP_ALLOWED_HOSTS.
MCP_RATE_LIMIT_PER_MINUTE / MCP_RATE_LIMIT_BURSTPer-principal request rate. Defaults: 120 per minute and burst 30.
MCP_MAX_CONCURRENT_REQUESTS / MCP_MAX_QUEUED_REQUESTSAdmission limits. Defaults: 8 in flight and 16 queued.
MCP_REQUEST_INGRESS_TIMEOUT_MSAbsolute limit for admission queueing plus body upload, not tool execution. Default: 10000; maximum: 60000.
MCP_REQUEST_EXECUTION_TIMEOUT_MSAbsolute limit for tool execution after upload. Default: 90000; maximum: 180000 (300000 before 0.1.2; a higher value now stops startup). The HTTP idle timeout follows both limits.

The server refuses a non-loopback bind unless MCP_AUTH_TOKEN and MCP_ALLOWED_HOSTS are set. It also refuses to enable writes without both MCP_AUTH_TOKEN and MCP_REQUEST_STATE_KEY. Once MCP_AUTH_TOKEN is configured, every /mcp request needs that Bearer token, including on loopback. Host and Origin checks run before the MCP handler.

Generate independent values for MCP_AUTH_TOKEN and MCP_REQUEST_STATE_KEY by running openssl rand -hex 32 twice. Do not reuse a Livespace credential.

The Bun process does not terminate TLS. Put a TLS-capable reverse proxy in front of every network-exposed deployment. The server reads credentials from environment variables, commonly through Bun's .env loading; protecting .env at rest is the operator's responsibility. Never commit it. The smoke script can also read the sandbox credentials from the macOS Keychain.

Write safety

The normal flow is elicitation-first:

  1. dryRun: true builds a plan without writing or requesting approval.
  2. On a client with form elicitation, a call without dryRun: true asks a human to approve the plan before execution. A confirm: true argument cannot bypass this prompt.
  3. The confirmation exchange uses a signed requestState that is valid for five minutes and consumed after an accepted or declined response. It is bound to the authenticated principal when present, th

Only the beginning is shown; read the rest in the repo