In addition to tools, the Flow Forms MCP server exposes two resources that your AI assistant can read for reference data. Resources provide context that helps the AI work with your forms more effectively.
Form Definition
URI: forms://{id}
Provides the complete definition of a specific form, including all fields with their types, options, and configurations. The {id} is the form's sqid.
Your AI assistant may read this resource automatically when it needs to understand a form's structure - for example, before creating a submission or suggesting changes to form fields.
The data returned is a lightweight summary: form metadata plus a fields array with each field's ID, name, type, required status, help text, and options. For the full picture - element gids, sections, visibility rules, props, and calculations - use the get-form tool, which is also the only way to open a private form you edit (the resource skips private forms entirely).
Field Type Documentation
URI: form-elements://
Provides documentation for all supported form field types, including:
- Which field types are available
- Which types require options (select, radio, checkbox, autocomplete)
- Which types can be marked as required
- Which types are supported via MCP vs. web-only
- Usage instructions and workflows for complex types (groups, composites, calculated fields)
- The validation-rule vocabulary the element tools accept
This resource helps your AI assistant understand what types of fields it can create and how to configure them correctly.
Web-Only Field Types
A few field types are only available through the web interface and cannot be created via MCP:
- Payment - Stripe payment fields
- Notion - Notion integration fields
- Boundary Finder - Geospatial boundary fields
Meta Field Types
These types are documented as patterns rather than single field types:
- User - expands into first name, last name, email, and a combined full-name field
- Address - expands into street, city, state, and zip fields