Rams vs Chatpack MCP

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

R
RamsArchitecture & Design · Remote HTTP/SSE
Design review for UI code: 258 rules across 9 categories, scored 0-100 with concrete fixes.43FairAuth: no auth required
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

Verdict: choose Rams for architecture & design work over a hosted endpoint; 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?

R
Choose Rams when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Rams

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.

Spec
R
Rams
Chatpack MCP logoChatpack MCP
CategoryArchitecture & DesignDeveloper Tools
Quality signal43/100 · Fair87/100 · Excellent
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars—224
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed5

Tools & capabilities

Rams tools

No tool names declared yet. Check the project README from 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.

Rams

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "rams": {
      "url": "https://www.rams.ai/mcp"
    }
  }
}

Chatpack MCP

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

Frequently asked questions

Rams is categorized under Architecture & Design and uses a remote HTTP/SSE transport. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Rams for architecture & design 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.

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

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