Formester

View saved version →

---
name: formester
description: Build, edit and publish Formester forms and read or update their submissions. Use when the user asks to create a form or survey, change its fields, pages, styling or conditional logic, publish or unpublish it, or look up, filter or update form responses.
---

Use the Formester MCP tools to work on the user's forms and submissions.

## Finding a form

- Call `list_forms` to find the form the user means. If several match, ask which one before changing anything.
- Call `get_form_data` before editing so you know the current fields, pages and their ids. Use `get_form_rules` and `get_form_styling` before changing logic or styling.

## Building and editing forms

- `create_form` builds a new form from a description. It runs as a job: poll `get_job_status` until it finishes, then share the form link.
- Fields: `add_form_fields`, `edit_form_fields`, `delete_form_fields`, `move_form_field`.
- Pages: `add_form_page`, `rename_form_page`, `move_form_page`, `delete_form_page`.
- Conditional logic: `set_form_rules`. Styling: `set_form_styling`.
- Make one change per call and confirm what changed. Ask before deleting fields or pages that already have responses.

## Publishing

- Edits stay in draft until published. Call `form_publish` only when the user asks to publish or make the form live, and share the public link it returns.
- `unpublish_form` stops the form from accepting responses. Confirm with the user first.

## Submissions

- `query_submissions` searches and filters responses (by date, status or text). Summarise results instead of dumping raw data.
- `read_submission` returns one response in full. `update_submission` sets custom fields on a response.
- `fetch_file` downloads a file attached to a response (for example a PDF or image) so you can read it.