Livespace CRM MCP Server vs Salesforce Cloud
A side-by-side look at the Livespace CRM MCP Server and Salesforce Cloud MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Livespace CRM MCP Server for customer data platforms work as a local process; choose Salesforce Cloud for customer data platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
Choose Salesforce Cloud when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SF_CLIENT_ID, SF_CLIENT_SECRET, SF_USERNAME, SF_PASSWORD, SF_LOGIN_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 55/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LIVESPACE_SUBDOMAINLIVESPACE_API_KEYLIVESPACE_API_SECRET | SF_CLIENT_IDSF_CLIENT_SECRETSF_USERNAMESF_PASSWORDSF_LOGIN_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View Livespace CRM MCP Server | View Salesforce Cloud |
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.
Salesforce Cloud 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": {
"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"
}
}
}
}
Salesforce Cloud
{
"mcpServers": {
"salesforce-cloud": {
"command": "npx",
"args": [
"-y",
"@aaronsb/salesforce-cloud-mcp"
],
"env": {
"SF_CLIENT_ID": "YOUR_SF_CLIENT_ID_HERE",
"SF_CLIENT_SECRET": "YOUR_SF_CLIENT_SECRET_HERE",
"SF_USERNAME": "YOUR_SF_USERNAME_HERE",
"SF_PASSWORD": "YOUR_SF_PASSWORD_HERE",
"SF_LOGIN_URL": "YOUR_SF_LOGIN_URL_HERE"
}
}
}
}
Frequently asked questions
Livespace CRM MCP Server is categorized under Customer Data Platforms and uses a local stdio subprocess. Salesforce Cloud belongs to Customer Data Platforms and uses a local stdio subprocess. Pick Livespace CRM MCP Server for customer data platforms work and Salesforce Cloud for customer data platforms.
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. Salesforce Cloud has no declared pricing — check the project's own site. 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 salesforce-cloud 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 1 views, 0 installs and 0 GitHub stars. Salesforce Cloud has 43/100 (Fair) with 0 views, 0 installs and 6 GitHub stars.
