Livespace CRM MCP Server vs Yazio MCP

In-depth architectural comparison of the Livespace CRM MCP Server and Yazio MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Livespace CRM MCP Server when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Livespace CRM MCP Server Details

Choose Yazio MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Yazio MCP Details

Feature & Specification Comparison

Specification	Livespace CRM MCP Server Developer Tools	Yazio MCP Developer Tools
Summary	Unofficial local MCP server for Livespace CRM with read tools and guarded writes.	MCP server for accessing Yazio user & nutrition data (unofficial)
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "livespace-crm-mcp-server": {
      "command": "bunx",
      "args": [
        "livespace-crm-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "yazio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "yazio-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons