MCP server
MCP server
Let an AI assistant read your forms and responses: ask it to summarize this week’s answers or find a response, without exporting anything.
Read-only by design
Every tool reads; none can create, change or delete a form or a response. Tools come in two scopes, forms:read and submissions:read.
Text written by owners and respondents comes back marked as untrusted, so the assistant treats an answer as data and not as instructions.
Sign in and choose a workspace
Connecting starts an OAuth flow: you sign in with your formweave account and choose the one workspace the assistant may read. The assistant gets a short-lived access token for that workspace only.
You can see and revoke the connections you approved at any time.
Standard transport
The server speaks stateless Streamable HTTP at /mcp and publishes OAuth protected resource metadata (RFC 9728), so MCP clients discover how to sign in on their own. Clients identify themselves with a client ID metadata document.
- Transport
- Streamable HTTP, POST /mcp
- Auth
- OAuth, one workspace per connection
- Access token lifetime
- 10 minutes
- Tools
- 5, all read-only
Tools
- 01
list_forms
Lists the forms of the workspace the connection is authorized for: title, status, response counts and version ids.
- 02
get_form
One form of the authorized workspace, by id.
- 03
get_form_version
One version of a form: its questions, jump rules, and intro and thank-you text.
- 04
list_submissions
Submissions of one form, newest first, up to 50 per page, with search over answer text.
- 05
get_submission
One submission with its answers, the questions of its form version and its notification deliveries.