MCP server

What an MCP server for your forms would let an AI assistant do, and where it stands today.

Tinyform does not run an MCP server yet. This page describes what one would add, so you know what to expect when it lands.

What it would do

MCP (Model Context Protocol) is an open standard that lets an AI assistant call into another product on your behalf. An MCP server on your Tinyform install would sit beside the existing REST API and let an assistant such as Claude, Cursor or any other MCP-capable client work with your workspace through a conversation instead of the editor.

With it connected, you would be able to ask an assistant to:

• Build a form from a plain description, questions and logic included.
• Change a form you already have: add a field, make one required, reorder a page.
• List and search the forms in your workspace.
• Pull a form's submissions into the conversation and chart, summarise or group them.

What exists today

The REST API already covers forms, questions, submissions, webhooks and workspaces behind an API key, and webhooks push each new submission out as it arrives. An MCP server would be a second door onto the same data, written for assistants rather than for code you write yourself.

The only thing an assistant would reach is the Tinyform you point it at, and nothing else.