Backforms MCP
Backforms MCP Server (backforms-mcp)
Official Model Context Protocol (MCP) server for Backforms. Connect serverless forms, anti-spam shields, and lead telemetry directly to Cursor, Windsurf, Claude Code, and Claude Desktop.
⚡ The Zero-Click Advantage
Instead of leaving your IDE, opening a browser, manually provisioning forms, and copying IDs:
Your AI coding agent executes the complete lifecycle in a single chat prompt:
"Create a Contact Us form in Next.js with honeypot spam protection and connect it to Backforms"
The agent automatically calls create_form, receives the live action URL (https://app.backforms.com/f/[uuid]), and injects ready-to-run HTML or Next.js code directly into your project.
Related MCP server: @lex-tools/codebase-context-dumper
🚀 Quick Setup
1. Get Your API Key
Sign in to your dashboard: Backforms Dashboard → API Keys & MCP.
Click Create API Key and copy your secret personal access token (
bf_live_sec_...).
2. Configure Your IDE
Cursor (.cursor/mcp.json or Settings → Features → MCP)
Add to your project's .cursor/mcp.json:
{
"mcpServers": {
"backforms": {
"command": "npx",
"args": ["-y", "backforms-mcp"],
"env": {
"BACKFORMS_API_KEY": "bf_live_sec_your_token_here"
}
}
}
}Windsurf (~/.codeium/windsurf/mcp_config.json)
{
"mcpServers": {
"backforms": {
"command": "npx",
"args": ["-y", "backforms-mcp"],
"env": {
"BACKFORMS_API_KEY": "bf_live_sec_your_token_here"
}
}
}
}Claude Desktop (claude_desktop_config.json)
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"backforms": {
"command": "npx",
"args": ["-y", "backforms-mcp"],
"env": {
"BACKFORMS_API_KEY": "bf_live_sec_your_token_here"
}
}
}
}Claude Code (CLI)
claude mcp add backforms --env BACKFORMS_API_KEY=bf_live_sec_your_token_here -- npx -y backforms-mcp🛠️ Complete Tool Catalog
Tool | Parameters | Description |
|
| Provisions a new form endpoint with action URL and JSX snippets. |
|
| Lists all forms in the workspace with throughput metrics. |
|
| Retrieves security config, access keys, and active integrations. |
|
| Retrieves leads, contact inquiries, and spam analysis. |
|
| Modifies form settings, allowed CORS origins, or custom redirects. |
|
| Configures webhook endpoints and email notification routing. |
|
| Dispatches an authenticated test submission to verify the live pipeline. |
|
| Permanently deletes a form endpoint from the workspace. |
| (none) | Checks monthly quota consumption, spam blocked, and storage. |
🔒 Security & Privacy Architecture
Stateless & Serverless: Runs locally via standard I/O (
stdio). Zero long-lived streaming overhead.SHA-256 Authentication: Personal Access Tokens are verified with secure hash comparisons.
No Sensitive Credential Storage: Tokens and database credentials are never logged or stored in plain text.
Strict CORS & Domain Origin Locks: Perimeter origin restrictions protect against unauthorized cross-site form posting.
📦 Links & Community
SaaS Platform: https://backforms.com
Web App Console: https://app.backforms.com
NPM Package: https://www.npmjs.com/package/backforms-mcp
Issues & Contributions: https://github.com/Arneld18/backforms-mcp/issues
License
MIT © AC Softworks, LLC (contact: info@acsoftworks.com)
Available Tools
9 toolscheck_workspace_usageA
Checks the current workspace submission quota, active plan tier, active forms count, and cloud storage usage.
Inputs: no named parameters.
create_formB
Creates a new serverless form endpoint in Backforms and returns the public action URL along with ready-to-use HTML and Next.js code snippets.
Inputs: name (required), redirect_url, honeypot_field, allowed_domains, +1 more.
delete_formA
Permanently deletes a form endpoint from the Backforms workspace.
Inputs: form_id (required).
get_form_detailsB
Retrieves complete configuration details, access keys, security settings, and active integrations for a specific form.
Inputs: form_id (required).
get_form_submissionsC
Retrieves recent leads, contact inquiries, and submission entries received by a specific form endpoint.
Inputs: form_id (required), limit, status.
list_formsB
Lists all form endpoints in the Backforms workspace, including their IDs, action URLs, and security configuration.
Inputs: limit, offset.
send_test_submissionA
Sends an authenticated test submission to verify that the form endpoint and notification pipeline work end-to-end.
Inputs: form_id (required), data.
setup_webhookC
Configures or updates custom webhook URL forwarding and email notification destinations for a form endpoint.
Inputs: form_id (required), webhook_url, webhook_enabled, secondary_emails, +1 more.
update_form_settingsC
Updates settings, redirect URLs, honeypot protection, or CORS domains for an existing form.
Inputs: form_id (required), name, is_active, redirect_url, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools target distinct resources and actions (create/list/update/delete form, get submissions, get details, test submission, workspace usage). Minor overlap exists between update_form_settings and setup_webhook (both tweak a form's configuration), and between get_form_details and get_form_submissions, but descriptions clearly separate config from data and add a slight risk of misselection.
All nine tools use a consistent snake_case verb_noun pattern (create_form, list_forms, get_form_submissions, update_form_settings, delete_form, get_form_details, setup_webhook, send_test_submission, check_workspace_usage). The convention is predictable and readable throughout.
Nine tools is well-scoped for a serverless form backend, covering the create/read/update/delete lifecycle plus submissions, webhooks, testing, and usage. Each tool earns its place with no obvious redundancy.
Full form CRUD, submissions retrieval, webhook/email setup, test submission, and usage checking are covered, giving solid lifecycle support. The main gap is submission-level management (e.g., fetching or deleting an individual submission by ID/export), which agents may want but can partly work around.
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1161MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).12 npm3Apache 2.0
- FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that can be deployed locally via stdio or remotely via SSE/HTTP endpoints, supporting multiple MCP clients including VS Code, Cursor, Windsurf, and Claude Desktop.1-
- AlicenseAqualityBmaintenancePersistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based, Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based organization, and team collaboration via Model Context Protocol.15342 npm2MIT