io.form/formio-mcp

Est-ce que io.form/formio-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.form/formio-mcp » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Versions auditées & empreintes

Vérifiez la version que vous utilisez : son empreinte doit correspondre à celle listée ici — sinon vous n'utilisez pas la version auditée.

Vous utilisez ce serveur ? Suivez-le (créez un compte) pour être alerté dès qu'une nouvelle version paraît ou que le verdict change.

Les 21 outils

• hello≈ 95 tokens

  Say hello — a connectivity check that confirms the server is running and reachable. Needs no Form.io project or credentials, so it is the first thing to try when other tools fail.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · optionnel
    Name to greet

  Exemple d'appel

  {"name": "hello", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• form_create≈ 657 tokens

  Create a new form in the Form.io project mapped to the user's current working directory. IMPORTANT: Before calling this tool, use the formio-schema skill to construct a properly structured Form.io form JSON definition based on the user's requirements. The skill documents all component types, validation options, layout patterns, and conditional logic available in Form.io. New forms default to `revisions: 'original'` so form change history is preserved. NOT for: creating a draft revision of an existing form. When the user says "create/save a draft", "draft <change>", call form_update with `formId` and `draft: true` instead.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • form · object · requis
    Form.io form JSON definition
  • note · string · optionnel
    Note describing the initial revision

  Exemple d'appel

  {"name": "form_create", "arguments": {"form": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• form_get≈ 353 tokens

  Fetch a single form definition from the Form.io project mapped to the user's current working directory, by form ID or path. Pass `draft: true` to fetch the form's current in-flight draft instead of the published form.

  Paramètres, retour & exemple (4)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • draft · boolean · optionnel
    When true, fetch the form's current draft (GET /<form>/draft)
  • select · string · optionnel
    Comma-separated fields to return (omit for full form JSON)
  • formIdOrPath · string · requis
    Form ID (_id) or path (e.g. "user/login")

  Exemple d'appel

  {"name": "form_get", "arguments": {"formIdOrPath": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• form_list≈ 388 tokens

  List forms from the Form.io project mapped to the user's current working directory with optional filtering and pagination.

  Paramètres, retour & exemple (7)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • skip · number · optionnel
    Number of forms to skip for pagination
  • sort · string · optionnel
    Sort field and direction (e.g. "-created")
  • tags · array · optionnel
    Filter by tags
  • type · string · optionnel · form | resource
    Filter by form type
  • limit · number · optionnel
    Maximum number of forms to return (default: 20)
  • select · string · optionnel
    Comma-separated fields to return (default: _id,title,name,path,type,tags)

  Exemple d'appel

  {"name": "form_list", "arguments": {"cwd": "texte", "skip": 1, "sort": "texte", "tags": [], "type": "form", "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• form_revision_get≈ 359 tokens

  Fetch a single immutable form revision from the Form.io project mapped to the current working directory. `version` accepts either the revision `_vid` (e.g. "3") or the revision document `_id` (24-character hex). To revert the live form to this revision, pass its `form` body to `form_update` with a `note` like `Revert to v<vid>`.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • version · string · requis
    Revision _vid (e.g. "3") or revision document _id
  • formIdOrPath · string · requis
    Form ID (_id) or path alias (e.g. "user/login")

  Exemple d'appel

  {"name": "form_revision_get", "arguments": {"version": "texte", "formIdOrPath": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• form_revisions_list≈ 361 tokens

  List immutable published revision summaries for a single form in the Form.io project mapped to the current working directory. Returns compact revision metadata (_vid, _id, modified, user, _vnote) for the form identified by `formIdOrPath`. To inspect a specific revision body, call `form_revision_get` with the desired `_vid`. To revert the live form to a prior revision, pass that revision body to `form_update` with a `note` like `Revert to v<vid>`.

  Paramètres, retour & exemple (2)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • formIdOrPath · string · requis
    Form ID (_id) or path alias (e.g. "user/login")

  Exemple d'appel

  {"name": "form_revisions_list", "arguments": {"formIdOrPath": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• form_update≈ 942 tokens

  Update an existing form in the Form.io project mapped to the user's current working directory. IMPORTANT: Before calling this tool, first use form_get to fetch the current form definition, then use the formio-schema skill to understand the schema so that you can apply the requested modifications (add, remove, or modify fields and settings), and finally call this tool with the complete updated form JSON. `draft`, `publish`, and `revert` are mutually exclusive — pass at most one. If `revisions` in the response differs from the stored value, the per-form revisions-mode gate prompted the USER and they chose.

  Paramètres, retour & exemple (8)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • form · object · requis
    Complete updated Form.io form JSON definition
  • note · string · requis
    Required note describing the diff (live form vs updated body) — no action preambles ("Published draft:", "Saved draft:", "Reverted:"). For `revert: true`, default to "Reverted to version {version}" unless the user explicitly provides a different note.
  • draft · boolean · optionnel
    When true, create or update a draft (PUT /form/{formId}/draft) instead of publishing. Caller `form` fields merge on top of existing draft fields, preserving prior unpublished draft edits.
  • formId · string · requis
    The _id of the form to update
  • revert · boolean · optionnel
    When true, revert the live form to a prior revision. Requires `version`. Caller `form` body is ignored; only allowlisted revision fields flow from the revision to live.
  • publish · boolean · optionnel
    When true, publish the current draft. Caller `form` body is ignored; only allowlisted revision fields flow from existing draft to live (PUT /form/{formId}).
  • version · string · optionnel
    Revision identifier for `revert: true` — either the revision `_vid` (e.g. "3") or the revision document `_id` (24-char hex).

  Exemple d'appel

  {"name": "form_update", "arguments": {"form": {}, "note": "texte", "formId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project_export≈ 269 tokens

  Export the complete template (roles, resources, forms, actions) of the Form.io project mapped to the user's current working directory as a portable JSON document. Use this to snapshot a project before importing changes.

  Paramètres, retour & exemple (1)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.

  Exemple d'appel

  {"name": "project_export", "arguments": {"cwd": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project_get≈ 415 tokens

  Report which Form.io project the given working directory resolves to, which deployment hosts it, and which layer supplied each — the preflight to run before the first tool call that reads from or writes to a deployment. Answers from inside this server, using the same resolver every other tool uses, so what it reports is what the next call targets. There is no need to run any shell command to ask this. Branch on `status`. "ok" means both URLs resolved and you may proceed. "not-configured" means nothing is mapped for this directory: relay the message, ask the user for the single value it names, record it with project_set, and call this again. "base-url-unresolved" means the project IS recorded and only its deployment is missing — ask for the Base URL alone and do NOT re-ask for the Project U

  Paramètres, retour & exemple (1)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.

  Exemple d'appel

  {"name": "project_get", "arguments": {"cwd": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project_import≈ 338 tokens

  Import a template JSON into the existing Form.io project mapped to the user's current working directory, merging roles, resources, forms, and actions in one call. Use the formio-resource-planner skill to construct the template before calling this tool. WARNING: import merges into the existing project — use project_export first to snapshot.

  Paramètres, retour & exemple (2)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • template · object · requis
    The template JSON object to import

  Exemple d'appel

  {"name": "project_import", "arguments": {"template": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project_set≈ 901 tokens

  Set the active Form.io project for the given working directory by recording its URL in ~/.formio/projects.json You MUST call this tool whenever the user asks to set, change, or switch the active Form.io project — do not merely acknowledge the request in text. Persisting the choice requires the tool call. The chosen URL is persisted to ~/.formio/projects.json keyed by the cwd argument when provided (or the MCP server process cwd otherwise). Pass the `cwd` argument whenever you know the user's current working directory — the server process cwd is fixed at spawn and may not match where the user actually is. Every Form.io tool resolves its project on each call, so a mapping written here needs no restart. It takes effect only where the mapping is the record that WINS, though: under a committed

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory to key the persisted mapping against, as an absolute path. Pass whenever known (e.g. from UserPromptSubmit hook context). Falls back to the MCP server's process.cwd() when omitted, which is fixed at spawn and may not be where the user is.
  • baseUrl · string · optionnel
    Deployment URL for the Form.io Enterprise Server that hosts this project. It builds the portal-login URL and keys the cached token, so a wrong one fails at login rather than on the request. Usually omitted: it is derived from projectUrl wherever it can be. Supply it when the server reports that it cannot be determined — a project URL with no path on a customer domain, whose deployment is a sibling sub-domain. It MAY carry a path of its own when the deployment is mounted at a sub-path. Never pass it for a project on a form.io host: those are served by https://api.form.io and by nothing else, so any other value is refused. Persisted per-cwd alongside the project URL, and bound to the project recorded with it, so each directory can target a different deployment and no deployment answers for another project. When omitted and this call does not change the project, the base URL already mapped for this directory is kept — but a call that re-points the directory to a different project keeps nothing, because that value belonged to the project being replaced.
  • projectUrl · string · optionnel
    Full URL of the Form.io project to activate. Optional when THIS DIRECTORY'S OWN MAPPING already holds a project: omitting it then updates that record's baseUrl alone, which is how the "Base URL cannot be determined" error is repaired without re-asking for a project URL. Where the project is held by another record, a baseUrl alone is refused rather than split from its project — for a committed formio.json the deployment is added to that file by hand (this server never writes one), and for FORMIO_PROJECT_URL in the environment the call must carry BOTH projectUrl and baseUrl, which records the pair here. Required when nothing configures a project at all. On the Form.io hosted cloud it is the project name as a sub-domain of form.io, e.g. https://examples.form.io — never https://api.form.io, which is the Base URL every hosted project shares. On a customer-hosted deployment it is either a sibling sub-domain of that customer’s domain, e.g. https://myproject.mysite.com, or a sub-directory of the deployment, e.g. https://forms.mysite.com/myproject — whichever that deployment uses.

  Exemple d'appel

  {"name": "project_set", "arguments": {"cwd": "texte", "baseUrl": "texte", "projectUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• role_create≈ 322 tokens

  Create a new role in the Form.io project mapped to the user's current working directory.

  Paramètres, retour & exemple (5)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • admin · boolean · optionnel
    When true, holders bypass access checks
  • title · string · requis
    Role title
  • default · boolean · optionnel
    When true, role is assigned to every new authenticated user
  • description · string · optionnel
    Role description

  Exemple d'appel

  {"name": "role_create", "arguments": {"title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• role_list≈ 256 tokens

  List all roles defined in the Form.io project mapped to the user's current working directory.

  Paramètres, retour & exemple (2)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • select · string · optionnel
    Comma-separated fields to return

  Exemple d'appel

  {"name": "role_list", "arguments": {"cwd": "texte", "select": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• role_update≈ 402 tokens

  Update an existing role in the Form.io project mapped to the user's current working directory. This is a full replacement — include all fields you want to preserve.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • role · object · requis
    Role document with updated fields
  • roleId · string · requis
    The _id of the role to update

  Exemple d'appel

  {"name": "role_update", "arguments": {"role": {}, "roleId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_types_list≈ 268 tokens

  List available action types for a form. Returns the catalog of action types the server supports.

  Paramètres, retour & exemple (2)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • formId · string · requis
    The form ID to list available action types for

  Exemple d'appel

  {"name": "action_types_list", "arguments": {"formId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_type_get≈ 306 tokens

  Get action type info and settings form schema. Call this before action_create to discover the required settings for the action type.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • formId · string · requis
    The form ID to get the action type for
  • actionName · string · requis
    The action type name (e.g. "email", "save", "login")

  Exemple d'appel

  {"name": "action_type_get", "arguments": {"formId": "texte", "actionName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_create≈ 628 tokens

  Create a new action on a form. Call action_type_get first to discover the required settings schema for the action type.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • action · object · requis
    Action definition
  • formId · string · requis
    The form ID to attach the action to

  Exemple d'appel

  {"name": "action_create", "arguments": {"action": {}, "formId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_list≈ 280 tokens

  List the actions configured on a form — the server-side handlers that run when a submission is saved, such as save-to-resource, email, login, and role assignment.

  Paramètres, retour & exemple (2)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • formId · string · requis
    The form ID to list actions for

  Exemple d'appel

  {"name": "action_list", "arguments": {"formId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_get≈ 300 tokens

  Get a single action by ID from a form, including its handler, method, condition, and type-specific settings. Call action_list first to find the action ID.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • formId · string · requis
    The form ID the action belongs to
  • actionId · string · requis
    The action ID to retrieve

  Exemple d'appel

  {"name": "action_get", "arguments": {"formId": "texte", "actionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_update≈ 664 tokens

  Update an existing action on a form. This is a full replacement of the action document — include every field you want to keep, and call action_get first if you do not already have it.

  Paramètres, retour & exemple (4)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • action · object · requis
    Action definition
  • formId · string · requis
    The form ID the action belongs to
  • actionId · string · requis
    The action ID to update

  Exemple d'appel

  {"name": "action_update", "arguments": {"action": {}, "formId": "texte", "actionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• action_delete≈ 303 tokens

  Delete an action from a form. The action stops running on submissions immediately and is not recoverable — call action_get first if the settings may be needed again.

  Paramètres, retour & exemple (3)

  Paramètres

  • cwd · string · optionnel
    User's current working directory as an absolute path. Selects the Form.io project that directory resolves to, by scope, narrowest first: a committed formio.json found by walking up from it, then the working-directory mapping project_set writes, then FORMIO_PROJECT_URL in the environment, which is the weakest of the three. Pass it on EVERY call whenever you know it: omitting it resolves against the MCP server's own working directory, which is fixed at spawn and may resolve to a different project. No environment variable removes the need for it — the environment is the source a file or a mapping overrides, not the one that overrides them.
  • formId · string · requis
    The form ID the action belongs to
  • actionId · string · requis
    The action ID to delete

  Exemple d'appel

  {"name": "action_delete", "arguments": {"formId": "texte", "actionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

[![Vérifié par MCP Hub](https://dokore.fr/badge/io.form--formio-mcp.svg)](https://dokore.fr/serveur/io.form--formio-mcp)

<a href="https://dokore.fr/serveur/io.form--formio-mcp"><img src="https://dokore.fr/badge/io.form--formio-mcp.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

npm:@formio/mcp@0.14.1