Chatpack MCP vs Formgong — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Chatpack MCP vs Formgong
In-depth architectural comparison of the Chatpack MCP and Formgong MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Chatpack MCP
Developer Tools · Local stdio
Quality: 83/100 (Excellent) | Auth: No auth required
Formgong
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Chatpack MCP if you need specialized Developer Tools tools running via a local process. Choose Formgong if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
C
Choose Chatpack MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
Create contact forms, get HTML/React/Next.js snippets and read recent submissions on Formgong.
Category & Scope
Tools & Capabilities Breakdown
Chatpack MCP Tools (5)
search_docs
Search bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.
get_document
Read a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.
get_integration_guide
Retrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
list_ui_blocks
List public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.
get_ui_block
Retrieve 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 Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Formgong belongs to Developer Tools using local stdio subprocess. Select Chatpack MCP when you need capabilities focused on developer tools and Formgong when you require tools for developer tools.
Lists your forms: id, name, public access key (`fk_…`) and submissions this month.
create_form
Creates a form (`name`, `notify_email`). Submissions are emailed to your account address. It returns the form id, the access key and dashboard links for connecting Telegram and extra recipients. Limit: 10 new forms per hour.
get_form_snippet
Returns code for one form (`form_id`, `framework`: `html` / `react` / `next`, `lang`), with its access key, the `_lang` field, the `botcheck` honeypot, and Turnstile when it's enabled.
list_recent_submissions
Read-only and opt-in. Returns up to 50 recent submissions with time and submitted fields only (no IP or user agent). Spam is excluded by default. Field values are marked as untrusted visitor input.
list_webhooks
Lists a form's webhooks (`form_id`): id, URL and creation time, never the signing secret.
create_webhook
Adds a public `https` webhook to a form, so n8n, Make or Zapier can register their trigger URL. Returns the form's signing secret. Plan limit per form.
delete_webhook
Removes one webhook from a form you own.
list_website_templates
Lists free, MIT-licensed website templates (complete sites with the contact form already wired to Formgong): niche, live demo, source, HTML download and a start command. Optional `topic`. Start a new site from one instead of generating every page.