Close vs Contact Support
Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Contact Support is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 |  Close |  Contact Support |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace danielrosehill/claude-code-plugins | Not listed | Listed Version: 0.2.0 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 | Close | Contact Support |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.close.com/mcp) | Installs as a plugin bundle |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 8 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/danielrosehill/contact-support-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Responded 6 days ago, requires a key | no remote endpoint we check |
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
Close
Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.
Contact Support
Contact a vendor's support desk from a registry of verified, dated contact routes rather than recalled ones — ticket URLs and which support plans can reach them, abuse and fraud addresses taken from mailto hrefs rather than page text, per-tier response windows, priority vocabulary, escalation ladders with SLA claim deadlines, pre-contact checks, and the plausible routes that turn out to be dead. Records the user's account identity and where credentials live (a pointer, never the secret), drafts the request with the identifiers the desk will demand, sends it through whichever channel is actually reachable, logs the ticket and chases it when the window elapses. Ships verified for Twilio only; extend with support-add-service. Work in progress — concept stage.
How to run each
Close As a remote MCP server
claude mcp add --transport http close https://mcp.close.com/mcpRequires: CLOSE_API_KEY (secret)
Contact Support As a Claude Code plugin
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install contact-support@danielrosehillCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Close 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 Contact Support publish no settings it asks for, so we do not compare settings.
What it can do: Close · What it can do: Contact Support · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.