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. Read-only. Use this first to find a form's id before calling get_form, list_submissions or delete_form; use get_form when you need the field definitions. |
| get_formA | Get one form with its full field and settings definition. Read-only. Fetched from the tenant's form list, so an unknown id returns a not-found error rather than another tenant's form. Use list_forms to discover ids; use list_submissions for responses. |
| create_formA | 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. Returns the created form (including its id) and its publicUrl, the shareable link respondents use. This tool only creates: it never edits an existing form, so call it once per new form and check list_forms first if a form with the same name may already exist. If the FormVault API rejects the input or the key, the tool returns an error result with the API's message and nothing is created. 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. Use list_forms to find the id first. 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. Read-only. Returns up to |
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 maps to a distinct resource+action: list_forms (discovery/metadata) vs get_form (full field definitions), create_form, delete_form, and list_submissions. Descriptions explicitly cross-reference each other and state when to prefer one over the other, leaving no realistic misselection path.
All five names follow the same snake_case verb_noun pattern (list_forms, get_form, create_form, delete_form, list_submissions). Verb choice is predictable (list/get/create/delete) and resource nouns are consistent between singular and plural forms.
Five tools is a tight, well-scoped surface for a form service and every tool earns its place with no redundancy. It leans slightly thin, since form authoring realistically spans more than a single create operation.
Create, read (list + get) and delete are covered, but there is no update_form at all — create_form explicitly states it never edits an existing form — so agents cannot modify a form or its fields once created. Submissions are also read-only with no single-submission fetch, export, or delete, leaving notable lifecycle gaps.