		@@ -20,4 +20,8 @@ import { z } from 'zod';
		const cfg = resolveProjectConfig(cwd, config);
		// The API answers this DELETE with the plain text body `OK`, so the
		// response is read as text. Left to default to `res.json()` it threw
		// "Unexpected token 'O'" and the delete reported failure after succeeding.
		await formioFetch(`form/${formId}/action/${actionId}`, {}, cfg, {
		method: 'DELETE',
		responseType: 'text',
		});
		@@ -24,0 +28,0 @@ // Text stays 'OK' — the payload carries the detail, and a bare

+1

-1

package.json

		{
		"name": "@formio/mcp",
		"version": "0.12.2",
		"version": "0.12.3",
		"mcpName": "io.form/formio-mcp",
		@@ -5,0 +5,0 @@ "description": "Form.io MCP Server",

+3

-3

README.md

		@@ -22,3 +22,3 @@ ## Formio MCP server
		\| --- \| --- \| --- \|
		\| stdio \| `npx -y @formio/mcp@0.12.2` (or `node dist/stdio.js`) \| Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf, Cline — anything that speaks MCP over stdio \|
		\| stdio \| `npx -y @formio/mcp@0.12.3` (or `node dist/stdio.js`) \| Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf, Cline — anything that speaks MCP over stdio \|

		@@ -36,3 +36,3 @@ There is no HTTP or SSE transport. The server's only HTTP listener is the temporary browser-login page described under [Authentication](#authentication), which carries no MCP traffic.
		"command": "npx",
		"args": ["-y", "@formio/mcp@0.12.2"],
		"args": ["-y", "@formio/mcp@0.12.3"],
		"env": {
		@@ -292,3 +292,3 @@ "FORMIO_PROJECT_URL": "https://your-project.form.io"

		<sub>\* Not at startup — the server starts, lists every tool, and answers `hello` without it; only the tools that read or write Form.io data error, naming `project_set` and this variable. The alternative is the `project_set` tool, which maps a working directory to a project in `~/.formio/projects.json`. Resolution runs by scope, narrowest first: a committed `formio.json` found by walking up from the caller's `cwd`, then the mapping for that `cwd`, then `FORMIO_PROJECT_URL` in the environment as the weakest source, then the error. Map a directory before any client connects with `npx -y @formio/mcp@0.12.2 project set --project-url <url> --cwd <path>` — the deployment is derived from the project URL wherever it can be, so add `--base-url <url>` only when the server says it cannot be determined. `project get --cwd <path>` prints what resolves and which source won. It exits `0` when it resolved, `1` when nothing is mapped for that directory, `2` when the command could not answer (a usage error, a malformed URL, an unreadable `~/.formio/projects.json`), and `3` when a project resolved but its Base URL could not be determined — so a caller can tell "nothing here yet" from "this failed" from "half configured, and here is the one value missing". `project set --cwd <path>` exits `0` when the directory is ready to serve a call, `1` when a named value is still missing, `2` when the command could not answer, and `3` when the record WAS written and the directory still resolves no Base URL — a committed `formio.json` governs it and supplies none, so the remedy is an edit to that file rather than another write.</sub>
		<sub>\* Not at startup — the server starts, lists every tool, and answers `hello` without it; only the tools that read or write Form.io data error, naming `project_set` and this variable. The alternative is the `project_set` tool, which maps a working directory to a project in `~/.formio/projects.json`. Resolution runs by scope, narrowest first: a committed `formio.json` found by walking up from the caller's `cwd`, then the mapping for that `cwd`, then `FORMIO_PROJECT_URL` in the environment as the weakest source, then the error. Map a directory before any client connects with `npx -y @formio/mcp@0.12.3 project set --project-url <url> --cwd <path>` — the deployment is derived from the project URL wherever it can be, so add `--base-url <url>` only when the server says it cannot be determined. `project get --cwd <path>` prints what resolves and which source won. It exits `0` when it resolved, `1` when nothing is mapped for that directory, `2` when the command could not answer (a usage error, a malformed URL, an unreadable `~/.formio/projects.json`), and `3` when a project resolved but its Base URL could not be determined — so a caller can tell "nothing here yet" from "this failed" from "half configured, and here is the one value missing". `project set --cwd <path>` exits `0` when the directory is ready to serve a call, `1` when a named value is still missing, `2` when the command could not answer, and `3` when the record WAS written and the directory still resolves no Base URL — a committed `formio.json` governs it and supplies none, so the remedy is an edit to that file rather than another write.</sub>

		@@ -295,0 +295,0 @@ ---

@formio/mcp - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics