← ClaudeAtlas

formio-mcp-setuplisted

Connects the Form.io MCP server (`@formio/mcp`) to whatever coding agent is running, so the Form.io skills have tools to call. Use when a Form.io skill's preflight finds the MCP tools missing, when Form.io tool calls fail because no Form.io tools are available, or when the user asks to install, connect, configure, or fix the Form.io MCP server. Also use when the user has installed the Form.io skills on their own but nothing has wired the server yet. Writes the MCP configuration for the client it is running in — Claude Code, Cursor, VS Code, or Codex — behind an approval gate, falling back to all four when the host cannot be established, then asks the server which Form.io project this directory resolves to and captures only whichever URL it reports missing, so the first tool call works, and tells the user how to reload. Not for: authenticating to Form.io (see `formio-auth`); building anything with Form.io — return to the skill that sent you here once the server is connected.
formio/ai · ★ 7 · AI & Automation · score 75
Install: claude install-skill formio/ai
# 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