All servers / Developer / Form.io MCP server
Form.io MCP server
Form.io MCP Server
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 1.0.1. Package: @formio/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.8 seconds including download)
- Tools offered: 25
- Last published: 2026-10-14
- Weekly downloads (npm): 1,281
- License: MIT · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
server_status1 of 1 parameter describedReport this server's name and version and how `cwd` resolves to a project, as project_get does. It makes no Form.io request and needs no credentials: call it first when other tools fail.
form_create4 of 4 parameters describedCreate a form in the project `cwd` resolves to. Build the form JSON with the formio-schema skill first. On a deployment licensed for revisions, `revisions` defaults to "original". Not for a draft of an existing form ("save a draft", "draft <change>"): use form_update with `draft: true`.
form_get4 of 4 parameters describedFetch a form definition, by _id or path, from the project `cwd` resolves to. `draft: true` fetches its in-flight draft instead of the published form.
form_list7 of 7 parameters describedList forms from the project `cwd` resolves to, one page at a time, optionally filtered by type and tags.
form_revision_get3 of 3 parameters describedFetch one immutable form revision from the project `cwd` resolves to. Restore it with form_revert, passing its `_vid`.
form_revision_list6 of 6 parameters describedList a form's published revision summaries in the project `cwd` resolves to, newest first, one page at a time. Read one with form_revision_get, or restore one with form_revert, passing its `_vid`.
form_update6 of 6 parameters describedUpdate a form in the project `cwd` resolves to: read it with form_get, apply the change using the formio-schema skill, and send the form. Sent fields overwrite, arrays and objects whole; top-level fields left out keep their value. Pass `draft: true` to save a draft instead of the live form; publish it with form_publish, and restore a prior revision with form_revert.
form_publish3 of 3 parameters describedPublish a form's draft as its live version in the project `cwd` resolves to. Save the draft first with form_update and `draft: true`; a form with no draft fails with NO_DRAFT. Needs the revisions licence (Security Module).
form_revert4 of 4 parameters describedRevert a form in the project `cwd` resolves to back to a prior revision: its components, tags, properties and display replace the live form's. Find it with form_revision_list. Needs the revisions licence (Security Module).
project_export2 of 2 parameters describedExport the project `cwd` resolves to as a template (roles, resources, forms, actions). With `tag`, export the template that version tag stored instead — how a workspace's template.json is refreshed; Form.io does not store project-level access with a tag, so that comes from the project's current access.
project_get1 of 1 parameter describedReport which Form.io project the working directory resolves to, which deployment hosts it, and which layer supplied each — the preflight before the first call that reads from or writes to a deployment. It uses the resolver every tool uses, so no shell command is needed. Branch on `status`: "ok" — proceed. "not-configured" — relay the message, ask the user for the one value it names, record it with project_set, and call this again. "base-url-unresolved" — the project IS recorded: ask for the Base URL alone, never the Project URL again. Reads only; project_set records a choice.
project_import2 of 2 parameters describedImport a template's roles, resources, forms and actions into the project `cwd` resolves to, for a first build: build it with the formio-resource-planner skill. Each form it names is replaced, its actions deleted and recreated, and its `access` replaces the project's; change an existing project with the form, role and action tools instead.
project_tag_list2 of 2 parameters describedReport the version the project `cwd` resolves to is at (`current`) and its version tags, newest first. With `compare: true`, also report the roles, resources, forms and actions changed since `current` — changes made outside the agent.
project_tag_create3 of 3 parameters describedVersion the project `cwd` resolves to: Form.io snapshots its current state under a semver `tag` with a `description`, and the project is then at that version. Ask the user before calling. Export the version with project_export `tag`.
project_set3 of 3 parameters describedSet the active Form.io project for a directory: records its Project URL in ~/.formio/projects.json, keyed by the directory `cwd` resolves to. Call it whenever the user asks to set, change, or switch the project; acknowledging in text persists nothing. No restart is needed. Resolution precedence: a committed formio.json, then this mapping, then FORMIO_PROJECT_URL in the environment, the weakest — so a mapping written here DOES override the environment. `ok` and `projectUrl` on the result report the pair that resolves. Pass projectUrl alone: the Base URL is derived — https://api.form.io for a form.io host, the parent path for a sub-directory project. Pass baseUrl only when the server reports it cannot be derived. A committed formio.json ({"projectUrl": "..."}, plus "baseUrl" only when it cannot be derived) is written by hand in the application's folder; this server reads it and never writes it.
role_create2 of 2 parameters describedCreate a new role in the project `cwd` resolves to.
role_list5 of 5 parameters describedList the roles defined in the project `cwd` resolves to, one page at a time.
role_update3 of 3 parameters describedUpdate an existing role in the project `cwd` resolves to. Sent fields overwrite, arrays and objects whole; top-level fields left out keep their value.
action_type_list2 of 2 parameters describedList the action types available for a form. Returns the whole catalog the server supports in one result.
action_type_get3 of 3 parameters describedGet action type info and settings form schema. Call this before action_create to discover the required settings for the action type.
action_create3 of 3 parameters describedCreate a new action on a form. Call action_type_get first to discover the required settings schema for the action type.
action_list6 of 6 parameters describedList the actions configured on a form, one page at a time — the server-side handlers that run when a submission is saved, such as save-to-resource, email, login, and role assignment.
action_get3 of 3 parameters describedGet a single action by ID from a form, including its handler, method, condition, and type-specific settings. Call action_list first to find the action ID.
action_update4 of 4 parameters describedUpdate an existing action on a form; call action_get first if you do not already have it. Sent fields overwrite, arrays and objects whole; top-level fields left out keep their value.
action_delete3 of 3 parameters describedDelete an action from a form. The action stops running on submissions immediately and is not recoverable — call action_get first if the settings may be needed again.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.