Sherweb MCP vs Livespace CRM MCP Server
Sherweb MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Livespace CRM MCP Server is an MCP server published by proAutomator. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Sherweb MCP |  Livespace CRM MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.8 Forks (GitHub): 13 Stars (GitHub): 64 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (npm): 312 Downloads/week (npm): 26 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Sherweb MCP | Livespace CRM MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 64 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/sherweb-v0.1.8/sherweb-mcp.mcpb) | On your machine (livespace-crm-mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 7, secrets among them: 4 | 7, secrets among them: 4 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/servosity/msp-skills | github.com/proautomator/livespace-crm-mcp |
| Changes in the last 7 days (differs) | 7 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Sherweb MCP
Every Sherweb Partner API capability, plus a local SQLite store, offline analytics, and
Livespace CRM MCP Server
Unofficial local MCP server for Livespace CRM with read tools and guarded writes.
How to run each
Sherweb MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install sherweb@msp-skillsRequires: SHERWEB_CLIENT_ID (secret), SHERWEB_CLIENT_SECRET (secret), SHERWEB_OAUTH_SCOPE (secret), SHERWEB_SUBSCRIPTION_KEY (secret)
Livespace CRM MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: LIVESPACE_API_KEY (secret), LIVESPACE_API_SECRET (secret), LIVESPACE_SUBDOMAIN, MCP_AUTH_TOKEN (secret), MCP_REQUEST_STATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Sherweb MCP asks for
SHERWEB_BASE_URLSHERWEB_CLIENT_ID (secret)SHERWEB_CLIENT_SECRET (secret)SHERWEB_NO_CONFIG_WRITESHERWEB_OAUTH_SCOPE (secret)SHERWEB_SUBSCRIPTION_KEY (secret)SHERWEB_TOKEN_URL
Only Livespace CRM MCP Server asks for
LIVESPACE_API_KEY (secret)LIVESPACE_API_SECRET (secret)LIVESPACE_MCP_ENABLE_WRITESLIVESPACE_SUBDOMAINMCP_AUTH_TOKEN (secret)MCP_PORTMCP_REQUEST_STATE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Sherweb MCP · What it can do: Livespace CRM MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.