Formbase

What formbase MCP server does

The formbase MCP server gives an AI client access to a hosted Formstep workspace through MCP. Its primary workflow is sending a published form to one recipient, optionally including known values, locked fields, context, delivery settings, an expiry, and a callback URL. The recipient can complete the form and return answers keyed by the form's field keys.

Agents can inspect a request's status and timeline, list requests across a form or workspace, and filter results by status, outcome, or an external identifier. Pending requests can be cancelled, and reminder emails can be sent manually. If a callback did not reach its endpoint, the callback can be replayed.

The available read operations also cover form structure, completed submissions, drafts when requested, and analytics such as views, submissions, completion rate, unique visitors, device, country, browser, and source.

How it works

The service is available at https://api.formstep.io/api/mcp; this repository contains connection documentation and configuration examples rather than a local runtime. An MCP client connects to that URL and authenticates with Formstep OAuth or an API token.

OAuth opens a browser for sign-in, workspace selection, and authorization. Each connection reaches one workspace. Headless agents and scripts can send an Authorization: Bearer header with a token beginning with fs_. API tokens expire 30 days after creation and cannot be extended.

For a request workflow, an agent should first call fields_list for the selected published form, then use request_create. Later, it can locate the request with request_list and inspect the response with request_get. Completed answers are returned under the form's field keys. A callback can notify an external endpoint when the recipient submits.

Setup and configuration

No package installation or local process is required. Configure an MCP client with the hosted endpoint. The README documents connections for Claude Code, Claude Desktop and claude.ai, Cursor, Cline, and Grok Build. Cline and other headless clients can use the API-token header instead of browser-based OAuth.

For Claude Code, the documented transport is HTTP. Cursor uses an MCP JSON configuration containing the server URL, while Cline uses a streamable HTTP entry with an authorization header. Keep API tokens out of source control. To use another workspace, create a separate connection and select that workspace during authorization.

Tools and capabilities

The formbase MCP server exposes these capabilities:

• fields_list identifies addressable fields on a published form.
• request_create, request_get, and request_list create and inspect recipient requests.
• request_cancel, request_remind, and request_replayCallback manage pending requests and delivery callbacks.
• document_create reserves an upload for a file handled by a request; one upload can support multiple requests.
• editor_getDocument returns a form's complete structure, while editor_formatText formats text inside a block.
• formSubmission_list lists completed submissions and, when requested, drafts.
• formAnalytics_get returns form usage and completion metrics segmented by available dimensions.
• workspace_list returns the single workspace available to the connection.

Limitations and notes

The connection is restricted to one workspace. A token lasts 30 days and must be replaced rather than renewed. The agent is not automatically told when a recipient submits unless a callback is configured; otherwise, it must check later with the request tools. ChatGPT developer mode is web-only, and on Pro it can read but not use tools that change data, such as sending requests or editing forms.