Download for macOS
Skill

formio-mcp-setup

@formio Updated 2026-10-19

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, then asks the server which Form.io project this directory resolves to and captures only whichever URL it reports missing, and tells the user how to reload. Not for: logging in to Form.io — the server opens that in the browser on the first tool call; an application's end-user auth (see `formio-auth`); building anything with Form.io — return to the skill that sent you here once the server is connected.

agent-skillsai-agentsclaudeclaude-codeclaude-pluginformioformsmcp

Install

With your agent

Install OMGSkills skill "formio/ai:plugin/skills/formio-mcp-setup" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/formio/ai /tmp/ai && ln -s /tmp/ai/plugin/skills/formio-mcp-setup ~/.claude/skills/formio-mcp-setup

From README

Connect the Form.io MCP server The Form.io skills call tools — formlist, formcreate, projectimport, projectset, projectget, 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. Not logging the user in to Form.io. The server opens the Form.io login in the browser on the first tool call that needs it and caches the token, so there is no login step to run here. formio-auth is about how an application's own users sign in, not about this.