SingleOps MCP Server and API by Cotlet vs io.github.brilliantdirectories/brilliant-directories-mcp
SingleOps MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.brilliantdirectories/brilliant-directories-mcp is an MCP server published by brilliantdirectories. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  SingleOps MCP Server and API by Cotlet |  io.github.brilliantdirectories/brilliant-directories-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 6.58.616 Downloads/month (npm): 6 253 Downloads/week (npm): 1 593 Forks (GitHub): 4 Stars (GitHub): 20 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 Forks (GitHub): 4 Stars (GitHub): 20 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 6.58.616 Downloads/month (npm): 6 253 Downloads/week (npm): 1 593 Forks (GitHub): 4 Stars (GitHub): 20 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 | SingleOps MCP Server and API by Cotlet | io.github.brilliantdirectories/brilliant-directories-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 20 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release (differs) | 2026-11-10 (better) | 2026-11-10 (worse) |
| Where it runs (differs) | Remote server (cotlet.dev/mcp/v1/singleops/connect) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/brilliantdirectories/brilliant-directories-mcp |
| Changes in the last 7 days (differs) | 7 | 6 |
| First seen (differs) | 2026-11-09 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Status out of date: last check 32 h ago returned HTTP 401 |
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
SingleOps MCP Server and API by Cotlet
SingleOps tree care business management MCP server: create lead, list proposals, schedule visit.
io.github.brilliantdirectories/brilliant-directories-mcp
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.
How to run each
SingleOps MCP Server and API by Cotlet As a remote MCP server
claude mcp add --transport http singleops https://cotlet.dev/mcp/v1/singleops/connectio.github.brilliantdirectories/brilliant-directories-mcp As a remote MCP server
claude mcp add --transport http brilliant-directories-mcp https://brilliantmcp.com/mcp --header "X-Api-Key: <YOUR_X_API_KEY>" --header "X-BD-Site-URL: <YOUR_X_BD_SITE_URL>"Requires: BD_API_KEY (secret), BD_SITE_URL, X-Api-Key header, X-BD-Site-URL header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.brilliantdirectories/brilliant-directories-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of SingleOps MCP Server and API by Cotlet publish no settings it asks for, so we do not compare settings.
What it can do: SingleOps MCP Server and API by Cotlet · What it can do: io.github.brilliantdirectories/brilliant-directories-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). 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.