Skip to main content
Glama

Backforms MCP Server (backforms-mcp)

npm version License: MIT Model Context Protocol Edge Ready

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

  1. Sign in to your dashboard: Backforms Dashboard → API Keys & MCP.

  2. 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.json

  • Windows: %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

create_form

name, redirect_url?, honeypot_enabled?, allowed_domains?

Provisions a new form endpoint with action URL and JSX snippets.

list_forms

limit?, offset?

Lists all forms in the workspace with throughput metrics.

get_form_details

form_id

Retrieves security config, access keys, and active integrations.

get_form_submissions

form_id, limit?, status? (all, valid, spam)

Retrieves leads, contact inquiries, and spam analysis.

update_form_settings

form_id, name?, redirect_url?, allowed_domains?, is_active?

Modifies form settings, allowed CORS origins, or custom redirects.

setup_webhook

form_id, webhook_url?, webhook_enabled?, notification_email?, secondary_emails?

Configures webhook endpoints and email notification routing.

send_test_submission

form_id, data?

Dispatches an authenticated test submission to verify the live pipeline.

delete_form

form_id

Permanently deletes a form endpoint from the workspace.

check_workspace_usage

(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.



License

MIT © AC Softworks, LLC (contact: info@acsoftworks.com)

Available Tools

9 tools
check_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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers