formslist-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORMSLIST_API_KEY | No | API key for FormsList, created at https://formslist.com/account/api-keys. Required for tools that need an account (create_form, list_forms, get_form, get_submissions, configure_autoresponse). Not needed for instant_provision and get_embed_snippet. | |
| FORMSLIST_BASE_URL | No | Base URL of the FormsList API. Defaults to https://formslist.com. | https://formslist.com |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| instant_provisionA | Create a working form endpoint instantly for any email — no account needed. The owner claims it later via the claim_url. Returns the endpoint URL, claim_url, a ready-to-paste html_snippet, and a curl_example. |
| create_formA | Create a new form in the authenticated FormsList account. Requires FORMSLIST_API_KEY. |
| list_formsA | List all forms in the authenticated FormsList account. Requires FORMSLIST_API_KEY. |
| get_formA | Get details of a single form (settings, endpoint, submission counts). Requires FORMSLIST_API_KEY. |
| get_submissionsA | Get submissions for a form, paginated. Requires FORMSLIST_API_KEY. |
| configure_autoresponseA | Enable, disable, or configure the auto-response email sent to people who submit a form. Requires FORMSLIST_API_KEY. Auto-responses are a paid-plan feature: if the account's plan does not include them, the result contains the upgrade message and upgrade_url to relay to the user. |
| get_embed_snippetA | Build a ready-to-paste HTML form snippet (plus an AJAX fetch example) that posts to a FormsList endpoint. Pure local generation — no API key, no network. Pass either the full endpoint URL (https://formslist.com/f/) or just the form hash. |
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 7 tools
Each tool has a distinct purpose: instant_provision handles anonymous form creation, create_form handles authenticated creation, get_form and list_forms distinguish single vs. list retrieval, and get_submissions, configure_autoresponse, and get_embed_snippet each target a separate concern. The only potential overlap between instant_provision and create_form is clearly resolved by the auth requirement.
All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., create_form, get_submissions, list_forms). There are no mixed conventions, camelCase, or vague standalone verbs, making the set predictable and readable.
Seven tools is well-scoped for a forms management server. The count is sufficient to cover core operations (create, read, list, submissions, configuration, snippet generation) without being heavy or redundant.
The surface covers creation, retrieval, listing, submissions, configuration, and snippet generation. However, there are no update or delete operations for forms, which are common CRUD actions. This is a minor gap that agents can work around but might cause friction in full lifecycle management.