FormVault MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORMVAULT_API_KEY | Yes | Your FormVault API key. Create it at https://formvault.eu/app/api-keys | |
| FORMVAULT_API_URL | No | The FormVault API URL | https://api.formvault.eu |
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 |
|---|---|
| list_formsA | List every form belonging to the API key's tenant. Returns id, name, description, field count and timestamps. |
| get_formA | Get one form with its full field and settings definition. Fetched from the tenant's form list, so an unknown id reports not found rather than another tenant's form. |
| create_formB | Create a form for the API key's tenant. Field types: text | email | phone | date | select | checkbox | consent | textarea | number | rating | multiselect | hidden | file | page_break | calculated Each field needs: id (unique within the form), type, label, required. Optional per field: placeholder, options (select/multiselect), min/max (number/rating), defaultValue (hidden), accept and maxSizeMb (file). Settings (all optional): successMessage, redirectUrl, closeAt (ISO date), maxResponses. Keep public-facing forms short — every extra question costs responses. |
| delete_formA | Permanently delete a form belonging to the API key's tenant. Irreversible, and the form's public URL stops working immediately. Confirm with the user before calling this — do not delete a form on your own initiative. |
| list_submissionsA | List decrypted submissions for a form. This returns respondents' personal data — only call it when the user has asked for submission content, and do not repeat it further than needed to answer. |
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 5 tools
Each tool targets a distinct resource+action: list_forms and list_submissions return different collections, get_form retrieves a single form definition, and create/delete are unambiguous write operations. There is no meaningful overlap between any pair.
All five tools follow a strict snake_case verb_noun pattern (list_forms, get_form, list_submissions, create_form, delete_form). The convention is applied uniformly with no deviations.
Five tools is well-scoped for a form-management server, with each tool earning its place across form listing, retrieval, creation, deletion, and submissions. No redundancy or padding.
The surface covers create/read/delete for forms and read for submissions, but there is no update_form (editing an existing form is a core workflow) and no submission-level operations beyond listing. These gaps will force agents to work around missing lifecycle steps.