What the Formhaus MCP server does
The Formhaus MCP server gives AI agents a way to inspect and test Formhaus form definitions without manually running a rendered form. It focuses on two tasks: checking whether a definition is valid and simulating user paths through the form engine.
Formhaus definitions are JSON documents that describe fields, labels, validation rules, visibility conditions, steps, routes, and submission controls. The MCP package is useful when an agent is creating these files, reviewing changes in a repository, or checking that a branching flow reaches the intended destination.
The Formhaus MCP server belongs to the broader Formhaus ecosystem, which also includes a framework-independent engine and React and Vue adapters. It does not replace those rendering packages or provide an application submission handler; it checks and exercises the definition used by them.
How it works
The local server is started with the @formhaus/mcp npm package and communicates with an MCP client over the command configured by that client. An agent can then send a form definition for validation or provide test inputs for a simulated path. Path simulation uses the same Formhaus engine behavior that evaluates validation, visibility, navigation, and branching decisions.
This makes it possible to test more than the shape of the JSON. A definition can be checked against scenarios such as a business account seeing an additional company step, a user skipping a conditional step, or different answers selecting different routes. The README describes the local checks as requiring no account and no key.
Setup and configuration
Register the local server with an MCP client that supports command-based servers:
claude mcp add formhaus -- npx -y @formhaus/mcp
The command uses npx to obtain and run the package. No environment variables, hosted account, or API credential are documented for this local validation and simulation workflow.
Formhaus also documents a separate hosted MCP endpoint for Formhaus Cloud:
claude mcp add --transport http formhaus https://api.formhaus.dev/mcp
That remote service is distinct from the local package and is intended for cloud operations such as publishing and editing hosted forms. Use the local Formhaus MCP server when the goal is definition checking or path simulation in a development workflow.
Tools and capabilities
The documented capabilities are:
- Validate Formhaus JSON form definitions.
- Simulate multi-step paths through the real Formhaus engine.
- Exercise conditional fields and visibility behavior.
- Check branching routes and skippable steps with test scenarios.
- Support agent-generated definitions before they are rendered in React, Vue, or another application.
The underlying form format supports field validation, conditional fields, multi-step navigation, branching routes, and skippable steps. The MCP package exposes checks for definitions and paths; the README does not document additional tools or operations by name.
Limitations and notes
The local package is a development and verification interface, not a hosted form backend. It does not, based on the provided material, submit responses, provide a dashboard, send webhooks, or create hosted links. Those capabilities belong to Formhaus Cloud.
The README does not list configuration environment variables, authentication settings, or a detailed tool schema for @formhaus/mcp. Client setup details may therefore vary by MCP client. The package is intended for Formhaus JSON definitions and its behavior depends on the rules implemented by the Formhaus engine.