Permet aux agents IA de rédiger, valider et réparer des définitions de formulaires JSON pour des applications React, Vue, Swift et Kotlin.
Aussi connu sous formhaus-dev/formhaus, @formhaus/mcp
- Étoiles
- 8
- Outils
- —
- Téléchargements, 30 jours
- 8 002
- Dernière version
- —
- Dernier commit
- 8 nov. 2026
- Licence
- MIT
Qu'est-ce que formhaus MCP ?
formhaus est un serveur MCP. Permet aux agents IA de rédiger, valider et réparer des définitions de formulaires JSON pour des applications React, Vue, Swift et Kotlin.
Résumé généré à partir du README du projet
À propos du MCP server formhaus
Formhaus fournit un système permettant de créer des définitions JSON uniques qui gèrent les champs, la validation et la logique de branchement des formulaires. Cette approche permet aux développeurs de rédiger un formulaire une seule fois et de l'afficher sur diverses plateformes, notamment React, Vue, Swift et Kotlin. Le moteur central est indépendant du framework et peut être utilisé dans des environnements Svelte ou en JavaScript pur.
Les développeurs peuvent utiliser le MCP server localement via npx pour permettre à des agents IA comme Claude Desktop, Cursor ou Claude Code de rédiger, valider et réparer ces définitions JSON. Pour ceux qui ont besoin d'une solution hébergée, Formhaus Cloud propose un MCP server distant qui permet aux agents de publier des formulaires et de lire les réponses directement. Le système prend en charge des fonctionnalités complexes telles que le branchement multi-étapes, les champs conditionnels et l'internationalisation via des catalogues de traduction.
Ce que vous pouvez faire avec
- 1Valider et corriger des définitions JSONLes développeurs peuvent utiliser le MCP server pour s'assurer que leur JSON de formulaire est syntaxiquement correct et logiquement cohérent.
- 2Prototyper des formulaires dans des outils de designLes designers peuvent transformer des définitions JSON en prototypes interactifs ou en cartes de flux au sein de Figma.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer formhaus MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller formhaus MCP dans Claude Code
$ claude mcp add formhaus -- npx -y @formhaus/mcpInstaller formhaus MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"formhaus": {
"command": "npx",
"args": [
"-y",
"@formhaus/mcp"
]
}
}
}Installer formhaus MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"formhaus": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@formhaus/mcp"
]
}
}
}Installer formhaus MCP dans VS Code CLI
$ code --add-mcp '{"name":"formhaus","type":"stdio","command":"npx","args":["-y","@formhaus/mcp"]}'Installer formhaus MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"formhaus": {
"command": "npx",
"args": [
"-y",
"@formhaus/mcp"
]
}
}
}Installer formhaus MCP dans Codex
$ codex mcp add formhaus -- npx -y @formhaus/mcpInstaller formhaus MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.formhaus] command = "npx" args = ["-y", "@formhaus/mcp"]
Installer formhaus MCP dans Gemini CLI
$ gemini mcp add -s user formhaus npx -- -y @formhaus/mcpInstaller formhaus MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"formhaus": {
"command": "npx",
"args": [
"-y",
"@formhaus/mcp"
]
}
}
}Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleformhaus-dev/formhaus is public and reachablegithub.com/formhaus-dev/formhaus ↗Réussi
- Le nom du package correspond au dépôt source@formhaus/mcp names formhaus-dev/formhaus as sourcenpmjs.com/package/@formhaus/mcp ↗Réussi
- Provenance du build (attestation Sigstore)Sigstore attestation for @formhaus/mcpnpmjs.com/package/@formhaus/mcp/v/0.15.3#provenance ↗Réussi
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-08github.com/formhaus-dev/formhaus ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from @formhaus/mcpRéussi
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubAdd Formhaus to your coding agent
npx formhaus
Adds the Formhaus MCP server to Claude Code, Codex, Cursor and Claude Desktop. Writes, checks and repairs definitions locally, with no account · Setup for each client
Two independent ways to use it:
-
Use the library. MIT, no account, no key. The core is framework-agnostic and runs the form in any app; React and Vue renderers are ready to use. Your submit handler sends the data wherever you want. CI tests React 18 and 19, and Vue 3.3 and 3.5.
npm install @formhaus/core # plus @formhaus/react or @formhaus/vue -
Use Formhaus Cloud. A hosted form backend: a submission endpoint with server validation, a dashboard and webhooks, plus hosted links, embeds and a visual builder. The first form needs no account.
Build in the browser at app.formhaus.dev, or add the remote MCP server and ask your agent: "Make me a waitlist form and give me the link."
claude mcp add --transport http formhaus https://api.formhaus.dev/mcp

What you get
| Feature | |
|---|---|
| One definition | Fields, validation, conditional fields, steps, branching routes, sections and repeatable groups in one JSON file you keep in git |
| React and Vue | Native renderers with accessible defaults, or your own components through components |
| Validation | Built-in rules and custom validators. validateSubmission() checks the same definition on the server |
| Agents | The MCP server writes, validates and fixes definitions. Remote MCP publishes forms and reads responses |
| i18n | Translation catalogs and keys for labels, messages and options |
| Accessibility | Labels, error summary, focus management and live regions built in |
| Small core | Zero dependencies, tree-shakable ESM |
| Figma | The plugin renders mockups, flow maps and prototypes from the same definition |
| Cloud, optional | Hosted links, embeds, a submission endpoint, CSV export and webhooks |
What it's for
- Multi-step forms with branching in React or Vue.
- Rendering a form from JSON with your own components.
- Designing the form in Figma from the same file.
- Generating and checking definitions with AI agents: Claude Code skills, the MCP server (
claude plugin marketplace add formhaus-dev/formhaus && claude plugin install formhaus@formhaus), the JSON Schema and the format specification. - Translated forms with your own catalogs, or with i18next, vue-i18n and Lokalise keys.
- A headless engine for Svelte or vanilla JS.
Example
Business accounts get a company step; everyone converges on review.
{
"$schema": "https://formhaus.dev/schema/form-definition.json",
"id": "signup",
"title": "Sign up",
"submit": { "label": "Create account" },
"steps": [
{
"id": "account",
"title": "Account",
"fields": [
{ "key": "email", "type": "email", "label": "Email", "validation": { "required": true } },
{ "key": "kind", "type": "radio", "label": "Account type", "autoAdvance": true,
"options": [{ "value": "personal", "label": "Personal" }, { "value": "business", "label": "Business" }] }
],
"routes": [
{ "to": "company", "show": [{ "field": "kind", "eq": "business" }] },
{ "to": "review" }
]
},
{ "id": "company", "title": "Company", "routes": [{ "to": "review" }],
"fields": [{ "key": "company", "type": "text", "label": "Company name", "validation": { "required": true } }] },
{ "id": "review", "title": "Review",
"fields": [{ "key": "terms", "type": "checkbox", "label": "I accept the terms", "validation": { "required": true } }] }
]
}
import { FormRenderer } from '@formhaus/react';
import definition from './signup.json';
<FormRenderer definition={definition} onSubmit={save} />;
Compare with react-hook-form, react-jsonschema-form, JSON Forms and SurveyJS →
Packages
| Package | Description | npm |
|---|---|---|
@formhaus/core |
Zero-dependency form engine: types, validation, visibility, multi-step | npm i @formhaus/core |
@formhaus/react |
React adapter with native HTML defaults and custom component support | npm i @formhaus/core @formhaus/react |
@formhaus/vue |
Vue 3 adapter with native HTML defaults and custom component support | npm i @formhaus/core @formhaus/vue |
@formhaus/mcp |
MCP server: validate definitions and simulate paths from AI agents | claude mcp add formhaus -- npx -y @formhaus/mcp |
@formhaus/figma generates form mockups on the Figma canvas. It is not on Figma Community yet; build it locally, then import packages/figma/manifest.json.
Svelte, Solid, or anything else: use @formhaus/core directly. See the Svelte recipe.
Install
npm install @formhaus/core
If you need a framework adapter:
npm install @formhaus/core @formhaus/react # React
npm install @formhaus/core @formhaus/vue # Vue
Or use @formhaus/core directly with any framework. See the Svelte recipe.
Quick start
Define a form
Write the JSON by hand, or use the /formhaus:formhaus-create-form Claude Code skill to generate it from a text description, a CSV table, or a screenshot of an existing form.
{
"$schema": "https://formhaus.dev/schema/form-definition.json",
"id": "contact",
"title": "Contact Us",
"submit": { "label": "Send" },
"fields": [
{
"key": "name",
"type": "text",
"label": "Name",
"placeholder": "Your name",
"validation": { "required": true, "minLength": 2 }
},
{
"key": "email",
"type": "email",
"label": "Email",
"placeholder": "you@example.com",
"validation": {
"required": true,
"pattern": "^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$",
"patternMessage": "Please enter a valid email address"
}
},
{
"key": "message",
"type": "textarea",
"label": "Message",
"placeholder": "How can we help?",
"rows": 4,
"validation": { "required": true }
}
]
}
React
npm install @formhaus/core @formhaus/react
import { FormRenderer } from '@formhaus/react';
import definition from './contact-form.json';
function ContactPage() {
async function handleSubmit(values: Record<string, unknown>) {
await fetch('/api/contact', {
method: 'POST',
body: JSON.stringify(values),
});
}
return <FormRenderer definition={definition} onSubmit={handleSubmit} />;
}
Vue
npm install @formhaus/core @formhaus/vue
<script setup lang="ts">
import { FormRenderer } from '@formhaus/vue';
import definition from './contact-form.json';
async function handleSubmit(values: Record<string, unknown>) {
await fetch('/api/contact', {
method: 'POST',
body: JSON.stringify(values),
});
}
</script>
<template>
<FormRenderer :definition="definition" @submit="handleSubmit" />
</template>
By default, both adapters render native HTML inputs. A step can hide Next with next: false, and cancellable async hooks run before and after navigation and submission. See lifecycle hooks.
Custom components
Both adapters accept a components prop (a FieldComponentMap) that lets you swap native HTML inputs for your own UI kit.
import type { FieldComponentMap, FieldComponentProps } from '@formhaus/react';
function MyTextInput({ field, value, error, onChange, onBlur }: FieldComponentProps) {
return (
<div>
<label>{field.label}</label>
<input
type={field.type}
value={(value as string) ?? ''}
placeholder={field.placeholder}
onChange={(e) => onChange(e.target.value)}
onBlur={onBlur}
/>
{error && <span className="error">{error}</span>}
</div>
);
}
const components: FieldComponentMap = {
text: MyTextInput,
email: MyTextInput,
};
<FormRenderer definition={definition} onSubmit={handleSubmit} components={components} />;
<!-- MyTextInput.vue -->
<script setup lang="ts">
import type { FieldComponentProps } from '@formhaus/vue';
const props = defineProps<FieldComponentProps>();
const emit = defineEmits<{ (e: 'update:modelValue', value: unknown): void }>();
</script>
<template>
<label>{{ props.field.label }}</label>
<input
:value="(props.modelValue as string) ?? ''"
@input="emit('update:modelValue', ($event.target as HTMLInputElement).value)"
/>
</template>
<!-- Usage -->
<script setup>
import { FormRenderer } from '@formhaus/vue';
import MyTextInput from './MyTextInput.vue';
</script>
<template>
<FormRenderer
:definition="definition"
:components="{ text: MyTextInput, email: MyTextInput }"
@submit="handleSubmit"
/>
</template>
Each field component receives the full FormField descriptor, the current value, and any validation error. Implement as many or as few field types as you need. Unmapped types fall back to native HTML.
Figma plugin
@formhaus/figma renders form definitions in Figma with built-in Material 3 and iOS-like kits or with your own components. Branching forms get a flow map, multi-step forms a clickable prototype, and a generated form can be selected, edited and updated in place.

The /formhaus:formhaus-figma-connect Claude Code skill binds your library's components to the plugin. See the plugin guide for local installation.
Contributing
See CONTRIBUTING.md.
License
Questions sur formhaus MCP
Comment ajouter formhaus MCP à Claude Code ?
Exécutez claude mcp add formhaus -- npx -y @formhaus/mcp dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter formhaus MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Que peut faire le MCP server Formhaus ?
Le MCP server permet aux agents IA de rédiger, vérifier et réparer des définitions de formulaires localement sans nécessiter de compte.
Puis-je utiliser Formhaus avec mes propres composants UI ?
Oui, les adaptateurs React et Vue permettent de remplacer les inputs HTML natifs par vos propres composants personnalisés via une prop components.
Formhaus prend-il en charge les formulaires multi-étapes ?
Oui, la définition JSON prend en charge les formulaires multi-étapes, incluant les champs, la validation, les champs conditionnels, les étapes et les routes de branchement.