Split Forms

What Split Forms MCP server does

The Split Forms MCP server provides an MCP connection to Split Forms, a hosted backend for web forms. It is intended for AI agents that need to work with a form-processing service rather than requiring an application team to build and operate submission handling from scratch.

A form can be directed to the Split Forms endpoint from several supported front-end contexts: plain HTML, React, Next.js, WordPress, or forms produced with AI tools. Once a submission reaches the service, Split Forms applies spam filtering, stores the submission in a dashboard, and emails it to you.

How it works

The integration centers on the hosted endpoint at https://splitforms.com/api/mcp. An AI agent connects to the MCP server, while the form itself sends submissions to Split Forms. The hosted service then handles the processing steps described in the listing: filtering likely spam, retaining submissions in a dashboard, and sending email notifications.

This arrangement separates the form interface from submission infrastructure. The front end can remain an HTML page or use a framework such as React or Next.js; WordPress sites and AI-built forms are also named as supported sources. The available information does not explain whether agents create forms, query stored submissions, or perform other operations, so those capabilities should not be assumed.

Setup and configuration

Use the published MCP endpoint as the connection target: https://splitforms.com/api/mcp.

For the form side, point the supported form implementation at the Split Forms endpoint. The listing specifically names HTML, React, Next.js, WordPress, and AI-built forms.

The free plan is described as allowing 500 submissions and not requiring a card. The material does not state whether that allowance is monthly, cumulative, or subject to other limits, so treat the figure as a plan-level indication rather than a complete quota specification.

Limitations and notes

The Split Forms MCP server is documented here only through a short product description; no README is available. As a result, there is no grounded list of MCP tools, supported client applications, authentication steps, error behavior, schemas, rate limits, retention policy, or deployment options.

The service is a fit for teams seeking hosted form submission handling with spam filtering, dashboard storage, and email notification.

The endpoint and product capabilities are the concrete integration points currently documented. Confirm operational and security requirements, including how submissions are protected and who can access dashboard data, before using the service for sensitive information.