Livespace CRM MCP Server vs Hindsight

A side-by-side look at the Livespace CRM MCP Server and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Livespace CRM MCP Server logoLivespace CRM MCP ServerCustomer Data Platforms · Local subprocess (stdio)Unofficial local MCP server for Livespace CRM with read tools and guarded writes.55GoodAuth: not declaredHindsight logoHindsightKnowledge & Memory · Local subprocess (stdio)Hindsight: Agent Memory That Works Like Human Memory - Built for AI Agents to manage Long Term Memory57GoodAuth: api key required

Verdict: choose Livespace CRM MCP Server for customer data platforms work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Livespace CRM MCP Server logoChoose Livespace CRM MCP Server when

  • You need dedicated capabilities in the Customer Data Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: LIVESPACE_SUBDOMAIN, LIVESPACE_API_KEY, LIVESPACE_API_SECRET.
  • You want tools like health, crm_metadata, search_crm.
Explore Livespace CRM MCP Server

Hindsight logoChoose Hindsight when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Explore Hindsight

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLivespace CRM MCP Server logoLivespace CRM MCP ServerHindsight logoHindsight
CategoryCustomer Data PlatformsKnowledge & Memory
Quality signal55/100 · Good57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsLIVESPACE_SUBDOMAINLIVESPACE_API_KEYLIVESPACE_API_SECRETHINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD
Verified ownerCommunity listingCommunity listing
GitHub stars053,323
Directory activity 2 views 0 installs 0 upvotes 14 views 0 installs 0 upvotes
Tools11Not listed

Tools & capabilities

Livespace CRM MCP Server tools 11

  • healthChecks the server; `checkLivespace: true` also makes one lightweight Livespace API call.
  • crm_metadataReturns 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_crmFinds persons, companies or deals, with record links even in lightweight results. Sorted deal searches use one 200-record sort window and report truncation.
  • get_recordsReads one record kind and up to 25 ids; walls for at most 5 persons, companies or deals.
  • get_activityReads one record wall, one bounded CRM feed range or bounded task pages per call.
  • analyzeRuns one named aggregation over bounded windows and reports whether its source window was truncated.
  • create_recordsCreates persons, companies, deals or tasks. Up to 10 items per call, with exact-match contact deduplication by default.
  • update_recordsUpdates persons, companies, deals or tasks. Up to 10 items per call.
  • log_activitiesAdds public notes or phone calls. Up to 15 notes or calls per call.
  • move_deals_to_stageMoves deals by applying the minimal process-step diff. Up to 10 items per call; backward moves need an explicit allowlist.
  • notify_userDispatches one in-app notification, limited to 5 per 10 minutes and 1 per recipient per minute.

Hindsight tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Livespace CRM MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "livespace-crm-mcp-server": {
      "command": "bunx",
      "args": [
        "livespace-crm-mcp"
      ],
      "env": {
        "LIVESPACE_SUBDOMAIN": "YOUR_LIVESPACE_SUBDOMAIN_HERE",
        "LIVESPACE_API_KEY": "YOUR_LIVESPACE_API_KEY_HERE",
        "LIVESPACE_API_SECRET": "YOUR_LIVESPACE_API_SECRET_HERE"
      }
    }
  }
}

Hindsight

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vectorize-io-hindsight": {
      "command": "npx",
      "args": [
        "-y",
        "@vectorize-io/hindsight-coding-agents"
      ],
      "env": {
        "HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
        "HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
        "HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
      }
    }
  }
}

Frequently asked questions

Livespace CRM MCP Server is categorized under Customer Data Platforms and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Livespace CRM MCP Server for customer data platforms work and Hindsight for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Livespace CRM MCP Server has no declared pricing — check the project's own site. Hindsight is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add livespace-crm-mcp-server and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Livespace CRM MCP Server has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Hindsight has 57/100 (Good) with 14 views, 0 installs and 53,323 GitHub stars.