Figma Context MCP vs Livespace CRM MCP Server
A side-by-side look at the Figma Context MCP and Livespace CRM MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Context MCP for architecture & design work as a local process; choose Livespace CRM MCP Server 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 Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIGMA_API_KEY, PORT. - You want tools like
get_figma_data, download_figma_images.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Customer Data Platforms |
| Quality signal | 71/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | FIGMA_API_KEYPORT | LIVESPACE_SUBDOMAINLIVESPACE_API_KEYLIVESPACE_API_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16,061 | 0 |
| Directory activity | 10 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | 11 |
| Full listing | View Figma Context MCP | View Livespace CRM MCP Server |
Tools & capabilities
Figma Context MCP tools 2
get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
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.
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.
Figma Context MCP
{
"mcpServers": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. Livespace CRM MCP Server belongs to Customer Data Platforms and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design work and Livespace CRM MCP Server 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.
Figma Context MCP is listed as free. Auth: api key required. Livespace CRM MCP Server 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 glips-figma-context-mcp and livespace-crm-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma Context MCP has a quality signal of 71/100 (Great) with 10 views, 0 installs and 16,061 GitHub stars. Livespace CRM MCP Server has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.