Formio-mcp Server

Formio-mcp is an MCP integration. Create and manage Form.io forms, resources, actions, roles, and projects from your AI agent.

Packages and local setup

The published npm package is @formio/mcp, version 0.14.1. Its declared MCP transport is stdio.

The package declares FORMIO_PROJECT_URL: Optional, and the WEAKEST of the three project sources: a committed formio.json found by walking up from the working directory wins, then the per-directory mapping project_set writes, then this. It pins nothing — project_set can redirect a directory whose environment names a different project. Useful for a launch with nowhere to record a project, such as CI or a container (e.g. https://examples.form.io on the hosted cloud; self-hosted it is either https://your-project.your-domain.com or https://your-host/project-name, depending on how that deployment routes projects). Leave it unset and the agent asks for a project and records it per directory.; FORMIO_BASE_URL: Optional, and usually unnecessary: the base URL is DERIVED from the project URL — https://api.form.io for a project on a form.io host, the parent path for a project addressed as a sub-directory — and is asked for only when it cannot be derived, which is a path-less project URL on a customer domain. There is no default. Like FORMIO_PROJECT_URL it is the weakest source, behind a committed formio.json and the per-directory mapping.; FORMIO_API_KEY: Form.io project API key. Optional — when omitted the server uses a browser-based portal login flow to obtain a JWT.; FORMIO_LOGIN_FORM: URL of a custom login form used by the browser-based portal login flow. Defaults to the deployment's portal login form.; FORMIO_FORCE_BROWSER: Set to 1 to attempt the browser login even where the server detects it cannot present one (CI, a container, a remote shell with no display). Use it when the login page is reachable from a browser elsewhere.; FORMIO_INSECURE_TLS: Set to 1 to skip TLS certificate verification. For local development against self-signed certificates only — never enable in production..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.14.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.