Form.io MCP란?
MCP 도구와 SKILL을 통해 Form.io Enterprise Server와 상호작용하여 AI 에이전트가 완전한 애플리케이션, 양식 및 워크플로우를 구축할 수 있도록 지원합니다. 25개 도구를 제공합니다. 예: form_create, form_get, form_list.
프로젝트 README에서 생성된 요약
Form.io MCP server 정보
개발자는 AI 에이전트를 Form.io Enterprise Server에 연결하여 완전한 애플리케이션, 양식 및 워크플로우를 구축할 수 있습니다. 이 MCP server는 에이전트 기반 코딩 환경이 프로덕션급 데이터 모델, 비즈니스 로직 및 RBAC 인프라와 상호작용할 수 있도록 다양한 도구 세트를 제공합니다. 이 server를 사용하면 에이전트가 JSON-schema 작성부터 복잡한 액션 구성까지 모든 것을 관리하는 컴포저블 백엔드 역할을 수행할 수 있습니다.
설정은 터미널 명령어나 Claude Code 및 Cursor와 같은 클라이언트용 에이전트 전용 플러그인을 통해 이루어집니다. server에는 Project URL이 필요하며, SaaS 환경의 경우 Base URL을 자동으로 도출하거나 셀프 호스팅 배포를 위해 수동으로 구성할 수 있습니다. 사용자는 캐시된 토큰과 작업 디렉토리별로 해결되는 프로젝트 설정을 통해 인증을 관리할 수 있어, 구성 정보가 코드와 함께 유지되도록 보장합니다. 시스템에는 양식, 역할, 액션 및 프로젝트를 관리하기 위한 전용 도구와 연결성을 확인하기 위한 진단 기능이 포함되어 있습니다.
활용 사례
- 1완전한 애플리케이션 구축에이전트가 비즈니스 요구사항에 대한 자연어 설명을 Form.io 백엔드를 갖춘 실행 가능한 애플리케이션으로 변환할 수 있습니다.
- 2복잡한 양식 및 위저드 생성AI에게 단일 웹 양식이나 다중 페이지 위저드를 처음부터 설계하고 배포하도록 지시할 수 있습니다.
- 3엔터프라이즈 데이터 구조 관리개발자는 에이전트를 사용하여 JSON schema를 작성하고 REST API를 통해 비즈니스 로직을 구성할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Form.io MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Form.io MCP 설치
$ claude mcp add ai -- npx -y @formio/mcpCursor에 Form.io MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"ai": {
"command": "npx",
"args": [
"-y",
"@formio/mcp"
]
}
}
}VS Code에 Form.io MCP 설치
.vscode/mcp.json
{
"servers": {
"ai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@formio/mcp"
]
}
}
}VS Code CLI에 Form.io MCP 설치
$ code --add-mcp '{"name":"ai","type":"stdio","command":"npx","args":["-y","@formio/mcp"]}'Claude Desktop에 Form.io MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"ai": {
"command": "npx",
"args": [
"-y",
"@formio/mcp"
]
}
}
}Codex에 Form.io MCP 설치
$ codex mcp add ai -- npx -y @formio/mcpCodex config.toml에 Form.io MCP 설치
~/.codex/config.toml
[mcp_servers.ai] command = "npx" args = ["-y", "@formio/mcp"]
Gemini CLI에 Form.io MCP 설치
$ gemini mcp add -s user ai npx -- -y @formio/mcpGemini settings.json에 Form.io MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"ai": {
"command": "npx",
"args": [
"-y",
"@formio/mcp"
]
}
}
}Form.io MCP 도구 25
README에서 감지됨form_createform_getform_listform_updateform_publishform_revertform_revision_listform_revision_getrole_createrole_listrole_updateaction_type_list
| form_create | — | |
| form_get | — | |
| form_list | — | |
| form_update | — | |
| form_publish | — | |
| form_revert | — | |
| form_revision_list | — | |
| form_revision_get | — | |
| role_create | — | |
| role_list | — | |
| role_update | — | |
| action_type_list | — |
도구 25개 모두 보기도구 수 줄이기
action_type_getaction_createaction_listaction_getaction_updateaction_deleteproject_exportproject_importproject_tag_listproject_tag_createproject_getproject_setserver_status
| action_type_get | — | |
| action_create | — | |
| action_list | — | |
| action_get | — | |
| action_update | — | |
| action_delete | — | |
| project_export | — | |
| project_import | — | |
| project_tag_list | — | |
| project_tag_create | — | |
| project_get | — | |
| project_set | — | |
| server_status | — |
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨통과
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
README
GitHub에서 보기The Form.io Agentic Coding Plugin
@formio/ai is what brings Form.io into your agentic coding environment. It provides a series of tools that enable any developer to perform a number of complex actions against the Form.io Enterprise Server using their favorite Agentic Coding toolsets. This turns the Form.io Enterprise Server into a Composable Backend for Agentically Coded Applications.
- Getting Started
- What you get
- Why this exists
- Agentic Skill Library
- Examples and Use Cases
- Using the MCP server without the skills
- MCP server tools
- Authentication
- Environment variables
- Contributing
- License
Getting Started
To get started, open up your Terminal within your application folder, and then use one of the following methods to install this plugin within your application folder.
Option 1: Skills.sh Installation
npx skills add formio/ai
The command installs the skill library into .agents/skills/ folder within your application, which every skills-capable agent reads. It installs skills only — the Form.io MCP server, which is what gives the agent tools like form_create, form_list, and project_import, is connected on first use by the bundled formio-mcp-setup skill: it writes the MCP configuration for your client, asks you to approve it, and tells you to reload.
Option 2: Agent Plugin Installation
If your agent supports plugins, installing the plugin is an alternative to the command above. A plugin install already includes the skills and the MCP server:
Claude Code
/plugin marketplace add https://github.com/formio/ai.git
/plugin install formio-ai@formio
Cursor
Plugin installation coming soon
Codex
Plugin installation coming soon
Copilot
Plugin installation coming soon
Project Setup
Neither install route asks for a URL. Both are resolved per working directory, so one install can serve several projects, and the answer travels with the code rather than with your machine. The first Form.io tool call that needs a project reports what is missing and names the command that supplies it:
# What does this directory resolve to?
npx -y @formio/mcp@1.0.1 project get --cwd "$(pwd)"
# Record it for this machine…
npx -y @formio/mcp@1.0.1 project set --project-url "<project url>" --cwd "$(pwd)"
# …or commit it with the application, tracked in git and shared with everyone who clones it:
# write a formio.json in the application's own folder (the server reads it, never writes it)
echo '{ "projectUrl": "<project url>" }' > formio.json
The skills do this for you: each one calls the project_get tool before its first call — over the connection the server already has, not through a shell — and asks only for whichever value the server says is missing. Two values can be involved:
- Project URL — the endpoint for your project. On our SaaS environment (https://portal.form.io) that is a sub-domain such as
https://myproject.form.io. Self-hosted, it depends on how your deployment routes projects: a sub-directory (https://forms.mysite.com/myproject) or a sub-domain of your own domain (https://myproject.mysite.com). - Base URL — the endpoint for the deployment. On our SaaS environment it is always
https://api.form.io— never your project's*.form.iosub-domain. Self-hosted, it is the deployment host, often a sub-domain of your own domain, e.g.https://forms.mysite.com.
You usually only supply the first. The Base URL is worked out from the Project URL wherever it can be — https://api.form.io for a *.form.io project, and the parent path for a sub-directory-routed one. The exception is the sub-domain routing case, where the project host and the deployment host differ by design and neither can be derived from the other; there the server asks for the Base URL explicitly rather than guessing.
Those derivations are also enforced: a *.form.io project paired with anything but https://api.form.io is refused, because for every project on our SaaS environment that pairing is a mistake that surfaces later as unexplained 404s or a portal login sent to a deployment you do not use. One deployment shape is indistinguishable from that mistake — an internal, non-SaaS deployment served from a *.form.io domain, which our QA team tests — so project set takes a --force flag for it:
npx -y @formio/mcp@1.0.1 project set --force \
--project-url "https://myproject.form.io" --base-url "https://api.internal.example" --cwd "$(pwd)"
--force requires both URLs in the same call: it records the pair you state, never one half completed from the record or by derivation. Every check is skipped for that pair — including the ones about a Project URL on its own — so what is recorded is exactly what you type. The pair is then honoured on every later read — project get reports it as forced rather than refusing it. It is deliberately a shell-only flag: the project_set tool does not take it, so no agent decides to waive a check.
The override belongs to the pair, not to the directory. Re-pointing the directory at a different project drops it and the checks apply again, while a write that leaves both halves untouched keeps it — an agent re-recording the project it already resolved must not undo your decision. That also means re-recording the same pair without --force changes nothing, so clearing the record is the way back:
npx -y @formio/mcp@1.0.1 project set --reset --cwd "$(pwd)"
--reset removes this directory's entry from ~/.formio/projects.json — nothing else — and prints what the directory resolves to afterwards, which may still be a committed formio.json or the environment. It takes no URLs, exits 0 whenever the record was cleared (run project get to see whether the directory is serviceable), and is what every forced report names as the way to put the checks back.
To sign out, or to switch accounts, remove the cached login for the directory's deployment:
npx -y @formio/mcp@1.0.1 project logout --cwd "$(pwd)"
project logout removes one deployment's token from ~/.formio/mcp-tokens.json — the deployment the directory resolves to, exactly as project get resolves it, or the one --base-url <url> names — and leaves every other entry in place. A running server notices on its next call there and opens the login page again, so no restart is needed. It exits 0 whether a token was removed or none was cached, and says which; 2 when the command could not answer, including a token cache it cannot read or write; 1 when nothing is mapped for the directory, as project get reports it, or when --base-url is not a valid URL; and 3 when a project resolved but its deployment could not be determined. In both of those cases --base-url names the deployment directly.
What you get
- Agent plugin:
@formio/ai. One-command install wherever the agent has a marketplace — Claude Code, Cursor, GitHub Copilot CLI, VS Code, Codex. Bundles the MCP server and the skill library, and each client reads the manifest it understands. - MCP server:
@formio/mcp. Form.io operations (form_*,role_*,action_*,project_*) as MCP tools. Works with any MCP-aware client: Claude Code, Claude Desktop, VS Copilot, and whatever comes next. - Skills library: Coding agent skills covering app orchestration, form building (webforms and wizards), form embedding, resource planning, JSON-schema authoring, action configuration, authentication & authorization, the
@formio/jsSDK surface, and the full Form.io REST surface.
Why this exists
Form.io has been the data standardization layer for enterprise data for a decade. With the proliferation of AI coding agents, that standardization matters more, not less.
Build on the Form.io platform, not from scratch. The agent builds complete applications including the data models, forms, workflows, and business logic. Form.io is the platform it builds on. The APIs, data patterns, RBAC, audit infrastructure, and form management capabilities are production-grade and already there. The agent uses them as tools to build applications better.
Standardization across every AI-built app. One model, one set of rules, one audit trail, regardless of which team or which agent built it. With a standardization layer, multiple teams ship multiple applications, all with defensible, reconcilable data layers across the enterprise.
Governance built in. RBAC, group permissions, change history, audit trails — all emitted on the first pass. Every app lands inside the same compliance envelope the enterprise already runs on.
Agentic Skill Library
The plugin ships an activatable skill library. Claude loads the relevant skill on demand based on what you ask — you rarely need to name one explicitly.
How it all works together
For the full picture — the skills architecture, how the orchestration skills dynamically load the other skills as an agent works through your prompt, how each flow reaches the Form.io Enterprise Server through the MCP server, and Mermaid diagrams of every process flow (building an application, extending one, building a form, embedding a form, changing a project, configuring auth) — read PROCESS.md.
Orchestration skills
Orchestration skills are special skills that serve as the entry point for most prompts. Rather than covering a single capability, they coordinate the other skills (planning, schema authoring, actions, deployment, framework scaffolding) to fulfill a broad, plain-language request end to end. When you describe what you want instead of which tool to use, an orchestration skill picks it up and drives the whole pipeline.
| Skill | What it does |
|---|---|
formio-application |
Framework-agnostic "build me an app" orchestrator. Turns plain-language intent into a running application backed by a Form.io project — planning resources, importing the template, and handing off to a framework implementor. Also handles adding new features to an existing app. |
formio-form-builder |
"Build me a form" orchestrator. Builds a single form end to end — webform or multi-page wizard — from intent through schema authoring to a saved form in your deployment, with an optional embed handoff. Also handles field edits to an existing form. |
All skills
| Skill | What it does |
|---|---|
formio-application |
Orchestration entry point for building or extending an application on the Form.io platform (see above). |
formio-form-builder |
Orchestration entry point for building a single form — webform or wizard — end to end (see above). |
formio-form |
Embeds and renders Form.io forms in any web application with the @formio/js renderer — pre-fill, conditional fields, calculated values, custom validation, and conditional wizard pages. |
formio-uag |
Makes forms agent-ready with the Form.io Universal Agent Gateway (UAG) 2.0 — designs tasks and their uag* properties, deploys the UAG and its model engines, and wires applications to it: conversation forms over MCP, the chat widget, Agentic Formflow (the Agent API and @formio/uag-js), and agentic workflows with the "Agent: Run task" action. |
formio-resource-planner |
Plans the resource structure, field configuration, and access/permission model from high-level requirements, then emits a ready-to-import template.json. |
formio-schema |
Reference for Form.io JSON schema — the document shapes for projects, forms/resources, and submissions. Used when constructing, editing, or interpreting any Form.io JSON. |
formio-actions |
Reference for configuring Form.io actions — the server-side behavior layer for email notifications, authentication, webhooks, role assignment, and form-to-form saves. |
formio-auth |
Authentication and authorization specialist — login/registration, RBAC, SSO (OIDC/SAML/LDAP), Token Swap, Custom JWT, passwordless email tokens, and JWT/session mechanics. |
formio-api |
Comprehensive Form.io REST API reference — every endpoint across platform admin, project admin, runtime, and PDF scopes. |
formio-sdk |
Reference for the @formio/js JavaScript SDK and @formio/js/utils Utilities — static and instance methods, VanillaJS rendering, plugins, and helpers. |
formio-mcp-setup |
Connects the Form.io MCP server to whichever coding agent is running, and captures the project URL, when the skills were installed without it. |
formio-angular |
Angular framework implementor. Turns an approved template.json plus a target project into a working Angular app using @formio/angular. Delegated to by formio-application. |
formio-react |
React framework implementor. A router over three branches — greenfield build, add CRUD to an existing app, and embed a form — generating a resource kernel over React Router data routers with @formio/react. Delegated to by formio-application. |
Many skills installed? Claude Code lists every installed skill's description within a budget of 1% of the model's context window (about 8,000 characters on a 200k-token model) and, over it, keeps only the names of the skills you use least, so it is less likely to choose them on its own. This library keeps its descriptions to about 9,000 characters combined, but every other skill and plugin you have installed shares that budget. If Form.io requests stop reaching the right skill, check the Skills row in
/context, and raise the budget with theskillListingBudgetFractionsetting (for example0.02) or theSLASH_COMMAND_TOOL_CHAR_BUDGETenvironment variable.
Examples and Use Cases
Ready-to-paste example prompts live in examples/ — each file is one self-contained prompt plus notes on what it should exercise. To try one, create a new folder, start Claude Code inside it, and paste the prompt:
mkdir form-app
cd form-app
claude
/plugin marketplace add https://github.com/formio/ai.git
/plugin install formio-ai@formio
Build complete applications
Create a brand-new 'greenfield' form-based application — or introduce a new form-based feature within an existing one — using the formio-application orchestration skill. The agent plans the data model, imports it into your Form.io project, and scaffolds the front end, using the Form.io platform as the composable backend for the full application logic.
- CRM Application — clients, deals, and activity logs with owner-scoped access.
- Help Desk — customer tickets, agent workflows, internal notes, and email notifications.
- Storyboard — Trello-style board → swimlane → story kanban with drag-and-drop ordering and team-based access.
This library currently only supports the Angular application framework for new 'greenfield' applications. It generally supports other frameworks using the Vanilla JS @formio/js javascript renderer. Full support for other frameworks are coming soon.
Build forms and wizards
Create complex forms and multi-page conditional wizards with the formio-form-builder skill. The agent authors the form JSON and automatically creates the form within any stage of your deployment — including forms whose submission data must adhere to well-defined external schemas such as FHIR.
- College Application Wizard — multi-page wizard with program-driven conditional pages.
- FHIR-Compliant Patient Form — submission data that conforms to the FHIR Patient resource.
- Customer Feedback Form — conditional follow-up fields and a conditional email notification.
- Student Onboarding Wizard — create a wizard and embed it within your application in one pass.
Embed forms in existing applications
Embed an existing form or wizard within any HTML-based application using the formio-form skill.
- Embed an Existing Form — render a saved form with
@formio/js, pre-fill it, and handle submit events.
Make forms agent-ready
Put AI agents in front of your forms with the Form.io Universal Agent Gateway (UAG) using the formio-uag skill. The agent tags and configures your forms for agents, designs their tasks, deploys the UAG and its model engines, and wires your application to it: conversation forms over MCP, a chat widget, forms that fill themselves in from a description, and agents that work on every submission. Each prompt below builds one of the live demos on the UAG's site, the UAG's own documentation is at ai.form.io/developers, and ai.form.io/developers/agentic-coding walks through building with this plugin.
- A claim wizard that fills itself in — Agent Input decides the wizard's pages and prefills them; the server re-decides before the save. Live demo
- Two agents that review every application — chained "Agent: Run task" actions with an agent role and owned fields. Live demo
- A chat that files service requests — the chat widget on a public form, on Form.io Open Source with no license. Live demo
Work the REST API via prompt
The formio-api skill knows the full REST surface of your Form.io deployment — create any Resource, Form, Submission, or other entity via prompt.
- Create a Patient Resource — create a new resource through the MCP server's first-party tools.
Using the MCP server without the skills
The bundled MCP server is also published standalone as @formio/mcp — you do not need the agent plugin or the skill library to use it. Any MCP-aware client (Claude Code, Claude Desktop, Cursor, VS Code Copilot) can spawn the server directly and call the tools below.
It is also listed in the official MCP Registry as io.form/formio-mcp, so clients that browse the registry can discover and install it without any manual configuration.
Manual configuration
{
"mcpServers": {
"formio-mcp": {
"command": "npx",
"args": ["-y", "@formio/mcp@1.0.1"]
}
}
}
That is the JSON mcpServers shape — what Claude Code (.mcp.json), Cursor (.cursor/mcp.json), Claude Desktop, Windsurf, and Cline expect. Both the filename and the top-level key vary by client, so there is no universal .mcp.json.
Copilot uses servers, not mcpServers. In .vscode/mcp.json the top-level key is servers — everything inside the entry is identical.
{
"servers": {
"formio-mcp": {
"command": "npx",
"args": ["-y", "@formio/mcp@1.0.1"]
}
}
}
Codex takes TOML, and has no JSON equivalent:
[mcp_servers.formio-mcp]
command = "npx"
args = ["-y", "@formio/mcp@1.0.1"]
Authentication is the same everywhere: the first authenticated tool call opens the browser portal-login flow, or set the FORMIO_API_KEY environment variable beside FORMIO_PROJECT_URL — the key applies only to that project — to skip the browser entirely — required on any host with no browser, such as a cloud agent, a container, or CI.
Once connected, prompt the tools directly — no skill activation involved:
Using the formio-mcp tools, show me every form and role in my Form.io project, then export the full project template and save it to ./backup/template.json.
Using the formio-mcp form_create tool, create a new form called "Contact Us" with fields for full name (required), email (required), subject, and message, plus a submit button.
Ready-to-paste versions of these live in examples/mcp/: Inspect and Export a Project and Create a Form Directly.
One caveat: without the skills, the agent authors Form.io JSON (form schemas, action settings, access arrays) from its own general knowledge instead of the conventions the skill library encodes — every operation the tools cover still works, but you give up the guardrails. For other transports (Streamable HTTP for remote clients, SSE for Claude Desktop) and running the server from a clone of this repo, see the MCP server README.
MCP server tools
The bundled @formio/mcp server exposes these 25 tools. Skills prefer these over raw HTTP whenever an operation is covered.
Form.io MCP 질문
Form.io MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add ai -- npx -y @formio/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Form.io MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Form.io MCP는 어떤 도구를 제공하나요?
25개 도구를 제공합니다. 예: form_create, form_get, form_list, form_update, form_publish.
직접 호스팅하는 Form.io 인스턴스에서도 사용할 수 있나요?
네, Project URL과 Base URL을 설정하여 Form.io SaaS 환경과 셀프 호스팅 배포 환경 모두 지원합니다.
오케스트레이션 SKILL은 어떻게 작동하나요?
오케스트레이션 SKILL은 광범위한 요청을 수행하기 위해 계획, 스키마 작성, 배포와 같은 다른 SKILL들을 조정하는 엔트리 포인트 역할을 합니다.