News

SPIP MCP Server Update: Formidable Forms, 36 Tools

Share via
Kimoun’s SPIP MCP server grows to 36 tools: Formidable forms driven by AI, a listing on the official MCP registry, managed hosting or your own servers.
SPIP MCP Server Update: Formidable Forms, 36 Tools

🇫🇷 Lire en français : SPIP MCP server : mise à jour et formulaires Formidable

The SPIP MCP server that Kimoun publishes has just shipped two versions in one week: 0.4.0, which brings ten tools dedicated to Formidable forms, then 0.5.0, which rounds out multilingual support. The connector grows from 25 to 36 tools, with an up-to-date listing on the official Model Context Protocol registry. Here is what changes, and the ways to use it: free trial, hosted by Kimoun, or on your own servers.

Two versions in one week  

  Tip

An MCP server that does not follow the protocol’s evolutions ends up no longer speaking the same language as Claude or ChatGPT. Maintenance is not an option: it is what keeps a connector alive. For the background, see my guide on what an MCP server is and what it costs.

A few words about SPIP, for those who have never worked with it: it is a high-end free and open-source CMS, born in the French online press more than twenty years ago. You find it wherever publishing is a real craft: French local authorities, government services, media, nonprofits and companies. That is the demanding readership this connector serves.

Kimoun’s SPIP MCP connector is now official  

Its com.kimoun/spip entry has been active on the official Model Context Protocol registry since 2 August; versions 0.4.0 then 0.5.0 followed each other there, with 0.5.0 as the latest listed. Along the way, the scope widens markedly: from 25 to 36 tools to drive a site running SPIP 4.4 or newer. Write a SPIP article from ChatGPT or Claude, translate it, manage sections, the media library and now forms, always within the permissions of the SPIP account that connects.

Another improvement: the features page is generated from the server code itself, through a machine export (/outils.json). The documentation cannot drift: the 36 tools on display are exactly the ones the agent can call.

  Note

This connector was born from a production need: written first to answer our own needs, then extended and industrialised for the daily use of a client SPIP agency on its own sites. Forms support followed exactly the same path: another project’s need brought it to life, and the use case is common enough to be merged into the connector’s main branch rather than kept in that project’s instance. Every site using the connector benefits.

Formidable forms, driven by AI  

Version 0.4.0 brings the most visible novelty: ten tools dedicated to Formidable forms, the reference forms plugin for SPIP (registrations, contact forms, applications). The assistant now handles the full cycle: create a form (create_form), modify it (update_form), manage its status, then review the responses received, moderate them, delete them and export them to CSV (export_form_responses).

Until now, you could already tell the assistant: “write and publish the article about the September workshop”. You can now follow up with: “create the matching registration form (name, email, phone) and attach it to the article”, then, the following week: “export the registrations to CSV”. All in a single conversation.

You : Write and publish the article about the September workshop.

Assistant : Article written and published.

You : Create the matching registration form (name, email, phone) and attach it to the article.

Assistant : Form created (name, email, phone) and attached to the article.

The following week

You : Export the registrations to CSV.

Assistant : Responses exported to CSV.

For illustration: a simulated conversation.

AI actions are bounded by guardrails: fields cannot be deleted from a form that already has responses without explicit confirmation; reading responses remains subject to Formidable’s real permissions; deletion goes to the trash by default. And Formidable is not a forced dependency: if the plugin is not installed on the site, the connector says so and suggests installing it. Nothing breaks.

Section languages: multilingual support rounded out  

Version 0.5.0 rounds out multilingual support. Articles already knew how to be translated and linked together; the assistant can now assign a language to a section with propagation to its whole subtree, make it inherit again from its parent section, and set the language of a top-level section at creation time.

How to use it: trial, managed hosting or your servers  

Three paths, depending on where you stand.

  • Try it. The self-service demo lets you test the connector on a sandbox SPIP site: one email, one key, and the assistant works on a demonstration site reset every week, with nothing to install.
  • Adopt it. The connector is built and managed by Kimoun. The standard mode is managed hosting by Kimoun, protocol updates included; if your hosting policy requires it, deployment on your own servers is also possible, with the same managed follow-up.
  • The offer in detail. Scope, prerequisites, public prices and the documentation of all 36 tools are on the SPIP MCP connector site, for organisations running SPIP: agencies, local authorities, nonprofits.

Two versions in one week, an up-to-date registry listing, documentation generated from the code: that is the publisher and managed-services craft in action. The real deliverable of an MCP server is not the server: it is its next update. And for your other business tools, MCP server hosting and maintenance remain the core of Kimoun’s offer, from existing connectors to custom builds.

Frequently asked questions

With Kimoun’s SPIP MCP server, an AI assistant such as Claude or ChatGPT handles Formidable forms end to end, from creating the form to exporting the responses to CSV. Ten dedicated tools were added in version 0.4.0. The assistant creates a form (create_form), modifies it (update_form), manages its status, then reviews the responses received, moderates them, deletes them or exports them (export_form_responses). Guardrails frame these actions. Fields cannot be deleted from a form that already has responses without explicit confirmation. Formidable’s real permissions apply to reading responses, and deletion goes to the trash by default. Formidable is not a forced dependency either: if the plugin is not installed, the connector says so and suggests installing it, without breaking anything.

Kimoun’s SPIP MCP connector is listed on the official Model Context Protocol registry, registry.modelcontextprotocol.io, under the entry com.kimoun/spip, active since 2 August 2026. The current version is 0.5.0, the latest published after 0.4.0. The registry is the public directory where AI clients and their users check available servers and versions. The product site, mcp-spip.kimoun.com, documents the 36 exposed tools and the technical prerequisite. That documentation is generated from the server code itself, through a machine export, so it cannot drift. To try it without installing anything, a self-service demo is open on a sandbox SPIP site. You leave your email, receive a key, and the assistant works on a site that is reset every week.

Kimoun’s SPIP MCP connector requires a site running SPIP 4.4 or newer: that is the only technical prerequisite stated on the product site, mcp-spip.kimoun.com. The Formidable plugin itself is not mandatory. If it is not installed, the connector says so explicitly and suggests installing it, without breaking anything else on the site. The 25 tools unrelated to forms remain available. To check compatibility before committing to anything, the self-service demo lets you test on a sandbox SPIP site. It is reset every week, and nothing is installed on your side. The full scope, the prerequisites and the public prices are documented on the connector’s site.

No: the AI assistant always acts within the permissions of the SPIP account that connects to the connector, exactly like a human editor behind the same login. An editor account that cannot publish will not publish through the AI either. Guardrails complete that framework on the forms side. Deleting fields from a form that has already received responses requires explicit confirmation. Reading responses remains subject to Formidable’s real permissions. And deletion goes to the trash by default, which leaves a way back. That is the founding principle of an MCP server: it only exposes what the administrator decided to expose, with the rights the administrator decided to grant.

Yes: since version 0.5.0, the SPIP MCP connector covers multilingual support all the way to sections, not just articles. Articles already knew how to be translated and linked together in earlier versions. The assistant can now assign a language to a section, with propagation to its whole subtree. It can also make a section inherit again from its parent, and set the language of a top-level section at creation time. This answers a common need among local authorities and nonprofits publishing in several languages. The change is part of the two versions shipped in one week, alongside 0.4.0 for Formidable forms, taking the connector from 25 to 36 tools.

Yes, updating an MCP server at every protocol revision is the condition for it to keep working with up-to-date assistants such as Claude or ChatGPT. The Model Context Protocol is still evolving. The specification has already gone through several major revisions since its release in late 2024, and the official SDKs follow each time. An MCP server that does not apply these changes eventually drops off, not from wear but from obsolescence: it no longer speaks the same language as the AI clients. Maintenance should therefore be planned from the first quote, and the English-speaking market bills it as a monthly retainer. With a software publisher, it is shared: the server is updated once, and every site using it benefits at the same time.