formio-mcp-setup

Connect the Form.io MCP server

The Form.io skills call tools — form_list, form_create, project_import, project_set, project_get, and the rest. Those tools come from the @formio/mcp server. Skills installed on their own (npx skills add formio/ai) arrive without it, because that installer handles skills only and never touches MCP configuration.

Your job here is to write that configuration, get it approved, and hand control back.

What you are NOT doing

• Not collecting an API key. Nothing you write into a client configuration file contains a URL, a key, or any other secret.
• Not continuing the user's original request. Configuration only takes effect after a reload, so this skill ends by asking them to reload and ask again.

You are offering to capture which Form.io project to use — see Step 4. That is one errand for the user rather than two, and it means the first Form.io tool call after the reload works instead of failing with "no project configured". It is an offer, never a requirement.

Step 1 — Confirm the server really is missing

Check whether tools named form_list, form_create, project_import, project_set, and project_get are available to you.

• All available → nothing to do. Say so in one line and return to the skill that sent you here.
• All missing → continue to Step 2.
• Present, but no project_get → the connected server predates that tool, which shipped after the rest of the Form.io tool surface. Skip to "Already connected, but too old" below; the configuration exists, and whether its pinned version can be moved forward is the first thing that branch checks. Decide this from the tool list you can actually call, never from a version number written in prose: the launch commands in this document are restamped on every release and sentences about them are not, so a number here goes stale by one release the moment project_get ships.

Already connected, but too old

Do not write a fresh configuration and do not treat this as a missing server. First ask where the server came from, because a plugin install has no file for you to edit: if the user installed the plugin through a marketplace (Claude Code /plugin install, Cursor's Customize panel, copilot plugin install, VS Code's Install Plugin From Source, or the Codex plugin directory), the pinned version belongs to the plugin, so tell them to update the plugin through the same route they installed it and then reload — do not go hunting for an mcpServers entry nothing wrote, and do not write one, which would leave two servers configured.