Bouncewatch MCP vs Livespace CRM MCP Server
A side-by-side look at the Bouncewatch 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.
Bouncewatch MCPCustomer Data PlatformsTrack company events such as funding, senior hires, partnerships and expansion, with dated, weighted signals, natural-language queries and watch alerts.45FairAuth: not declaredVerdict: choose Bouncewatch MCP for customer data platforms work; 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 Bouncewatch MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You have the keys it needs:
BOUNCEWATCH_API_KEY. - You want tools like
search_signals, search_companies, find_company.
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 | Bouncewatch MCP | |
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 45/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | BOUNCEWATCH_API_KEY | LIVESPACE_SUBDOMAINLIVESPACE_API_KEYLIVESPACE_API_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | 11 |
| Full listing | View Bouncewatch MCP | View Livespace CRM MCP Server |
Tools & capabilities
Bouncewatch MCP tools 10
search_signalsThe latest signals across the whole index — which companies did something recently, what it was, and whensearch_companiesFind companies by country, headcount and funding stagefind_companyLook up a company by name and get its domainget_companyFirmographic profile of one companyget_company_signalsThe dated signal timeline for one companyrefresh_companyQueue a fresh scan of one companyget_refresh_statusCheck a queued scan. Free to callwatch_companyPut a standing watch on a companycheck_watchesWhat happened at the companies this key already watchesget_signal_taxonomyEvery signal type, grouped by category. Free to call
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.
Bouncewatch MCP
No confirmed install command for Bouncewatch MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
Bouncewatch MCP is categorized under Customer Data Platforms and uses an install path we have not confirmed yet. Livespace CRM MCP Server belongs to Customer Data Platforms and uses a local stdio subprocess. Pick Bouncewatch MCP for customer data platforms 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. Bouncewatch MCP has no confirmed install command yet — follow its own setup instructions.
Bouncewatch MCP is listed as freemium — a free tier with paid plans. 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 bouncewatch-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, Bouncewatch MCP has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Livespace CRM MCP Server has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.