Keel vs Chatpack MCP

A side-by-side look at the Keel and Chatpack MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Keel logoKeelDeveloper Tools · Local subprocess (stdio)Network diagnostics — ping, traceroute, DNS, port scanning, and connectivity testing.47FairAuth: not declaredChatpack MCP logoChatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.87ExcellentAuth: no auth required

Verdict: choose Keel for developer tools work as a local process; choose Chatpack MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Keel logoChoose Keel when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like health, ping, traceroute.
Explore Keel

Chatpack MCP logoChoose Chatpack MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_docs, get_document, get_integration_guide.
Explore Chatpack MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKeel logoKeelChatpack MCP logoChatpack MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal47/100 · Fair87/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars0224
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools145

Tools & capabilities

Keel tools 14

  • healthServer version and status check
  • pingTCP connect ping (port 80) with latency stats
  • tracerouteTrace network route to a host
  • dns_lookupResolve DNS records (A, AAAA, MX, CNAME, TXT, NS)
  • reverse_dnsReverse DNS lookup for an IP address
  • port_checkCheck if a single TCP port is open
  • port_scanScan common TCP ports (rate-limited, max 100)
  • check_ssl_certInspect SSL/TLS certificate details and expiry
  • whois_lookupWHOIS domain registration lookup
  • http_checkHTTP request with status, timing, headers, size
  • subnet_scanDiscover live hosts on a local subnet (RFC 1918 only)
  • get_public_ipGet the machine's public IP address
  • +2 more on the listing page

Chatpack MCP tools 5

  • search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.
  • get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.
  • get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
  • list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.
  • get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.

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.

Keel

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "keel-2": {
      "command": "uvx",
      "args": [
        "sounding-mcp"
      ]
    }
  }
}

Chatpack MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chatpack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chatpack/mcp"
      ]
    }
  }
}

Frequently asked questions

Keel is categorized under Developer Tools and uses a local stdio subprocess. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Keel for developer tools work and Chatpack MCP for developer tools.

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.

Keel has no declared pricing — check the project's own site. Chatpack MCP is listed as free. Auth: no auth required. 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 keel-2 and chatpack-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Keel has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Chatpack MCP has 87/100 (Excellent) with 4 views, 0 installs and 224 GitHub stars.