Chatpack MCP vs Fifty50

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

Chatpack 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
F
Fifty50Agreements & Coordination
Find a co-founder and split equity fairly — partnership analysis + co-founder marketplace.37FairAuth: not declared

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

Which MCP server should you choose?

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

F
Choose Fifty50 when

  • You need dedicated capabilities in the Agreements & Coordination domain.
Explore Fifty50

Feature & specification comparison

Rows where the two servers differ are marked.

SpecChatpack MCP logoChatpack MCP
F
Fifty50
CategoryDeveloper ToolsAgreements & Coordination
Quality signal87/100 · Excellent37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars224—
Directory activity 4 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools5Not listed

Tools & capabilities

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.

Fifty50 tools

No tool names declared yet. Check the project README from the listing page.

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.

Chatpack MCP

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

Fifty50

No confirmed install command for Fifty50 yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. Fifty50 belongs to Agreements & Coordination and uses an install path we have not confirmed yet. Pick Chatpack MCP for developer tools work and Fifty50 for agreements & coordination.

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. Fifty50 has no confirmed install command yet — follow its own setup instructions.

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

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