Guesty MCP Server vs Liongard MCP
Guesty MCP Server is an MCP server published by DLJRealty. Marketplaces we read that list it: 1 (Official MCP Registry). Liongard MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. 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 |   Liongard MCP | |
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 0.11.2 Downloads/month (npm): 1 169 Downloads/week (npm): 52 Not marked · First seen |
Listed Version: 0.1.7 Forks (GitHub): 13 Stars (GitHub): 62 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 | Guesty MCP Server | Liongard MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 62 |
| Forks (GitHub) (differs) | No figure on GitHub | 13 |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | On your machine (guesty-mcp-server) | On your machine (https://github.com/Servosity/msp-skills/releases/download/liongard-v0.1.7/liongard-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 3 | 5, secrets among them: 3 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/dljrealty/guesty-mcp-server | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 0 | 9 |
| 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
Guesty MCP Server
Guesty MCP server. 43 Guesty tools, read and write, free. Grounded replies, message-policy screen.
Liongard MCP
Liongard config visibility: sync your estate offline, then drift-check and search it from one CLI.
How to run each
Guesty MCP Server As a local MCP server: npm package
claude mcp add --env "GUESTY_CLIENT_ID=<YOUR_GUESTY_CLIENT_ID>" --env "GUESTY_CLIENT_SECRET=<YOUR_GUESTY_CLIENT_SECRET>" --env "GUESTY_MCP_LICENSE_KEY=<YOUR_GUESTY_MCP_LICENSE_KEY>" --transport stdio guesty -- npx -y guesty-mcp-serverRequires: GUESTY_CLIENT_ID (secret), GUESTY_CLIENT_SECRET (secret), GUESTY_MCP_LICENSE_KEY (secret)
Liongard MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install liongard@msp-skillsRequires: LIONGARD_ACCESS_KEY_ID (secret), LIONGARD_ACCESS_KEY_SECRET (secret), LIONGARD_API_KEY (secret), LIONGARD_INSTANCE
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 Guesty MCP Server asks for
GUESTY_CLIENT_ID (secret)GUESTY_CLIENT_SECRET (secret)GUESTY_MCP_LICENSE_KEY (secret)
Only Liongard MCP asks for
LIONGARD_ACCESS_KEY_ID (secret)LIONGARD_ACCESS_KEY_SECRET (secret)LIONGARD_API_KEY (secret)LIONGARD_BASE_URLLIONGARD_INSTANCE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Guesty MCP Server · What it can do: Liongard MCP · 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.