Backforms MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKFORMS_API_KEY | Yes | Your Backforms secret personal access token (e.g. bf_live_sec_...). Create one in the Backforms dashboard under Settings > API Keys & MCP. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| list_formsB | Lists all form endpoints in the Backforms workspace, including their IDs, action URLs, and security configuration. |
| get_form_submissionsC | Retrieves recent leads, contact inquiries, and submission entries received by a specific form endpoint. |
| update_form_settingsC | Updates settings, redirect URLs, honeypot protection, or CORS domains for an existing form. |
| check_workspace_usageA | Checks the current workspace submission quota, active plan tier, active forms count, and cloud storage usage. |
| delete_formA | Permanently deletes a form endpoint from the Backforms workspace. |
| get_form_detailsB | Retrieves complete configuration details, access keys, security settings, and active integrations for a specific form. |
| setup_webhookC | Configures or updates custom webhook URL forwarding and email notification destinations for a form endpoint. |
| send_test_submissionA | Sends an authenticated test submission to verify that the form endpoint and notification pipeline work end-to-end. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.