brieform.app valid

Brieform

Forms your AI builds, publishes, and reads. Brieform is an AI-native form builder with an MCP server: describe a form in Claude, ChatGPT, Cursor, or any MCP client, get a live URL back, and read the responses in the same thread.

For agents: AI-native form builder with an MCP server: build, publish and read forms from Claude, ChatGPT, Cursor or other MCP clients; includes setup guides and tool refer

form buildermcp serverai formsform responsesclaude integration

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T02:41:44.655Z. Cached copy · Source on brieform.app

# Brieform

> Forms your AI builds, publishes, and reads. Brieform is an AI-native form builder with an MCP server: describe a form in Claude, ChatGPT, Cursor, or any MCP client, get a live URL back, and read the responses in the same thread.

Brieform is built conversation-first. The MCP server is the product, not an add-on: every action exists as a tool your AI can call directly. There is no form builder in the dashboard, which is a list and detail view only.

Free to start, no credit card. Hosted in the EU (Frankfurt).

## MCP server

- Endpoint: `https://brieform.app/api/mcp/mcp`
- Transport: Streamable HTTP (MCP 2025-03-26). SSE-only clients are not supported.
- Auth: OAuth 2.1 for chat clients, or an API key (`bf_...`) for scripts, CI, and clients without OAuth.
- Discovery: [/.well-known/mcp](https://brieform.app/.well-known/mcp)

### The 15 tools

| Tool | Access | What it does |
|---|---|---|
| `create_form` | write | Create a form from a prompt or a structure |
| `create_form_from_brief` | write | Create a pre-devis intake form from a pasted client brief |
| `analyze_brief` | read | Analyze a client brief for gaps before building an intake |
| `update_form` | write | Edit an existing form, structured or in natural language |
| `get_form` | read | Full form structure: fields, theme, response count |
| `list_forms` | read | List forms with status filter, search, cursor pagination |
| `publish_form` | write | Publish a form and return its public URL |
| `unpublish_form` | write | Unpublish a form, responses are kept |
| `set_form_theme` | write | Apply a theme by preset, custom hex, or description |
| `get_responses` | read | Read submissions with pagination, date filters, CSV export; optional signed file download URLs |
| `get_upload_url` | read | Mint a short-lived (~15 min) signed download URL for one completed upload |
| `duplicate_form` | write | Clone a form into a new draft, structure and theme only |
| `delete_form` | write | Permanently delete a form and its responses, `confirm: true` required |
| `get_form_analytics` | read | Views, submissions, conversion rate, daily breakdown, top referrers, multi-step funnel (Free and Pro) |
| `get_form_share_assets` | read | Public URL, iframe embed snippet, social preview image, QR code |

Every tool carries MCP annotations so the client knows which calls are safe reads and which are destructive writes. The seven write tools record an entry in the audit log, visible in the Activity tab of a form.

## Setup guides

- [Install overview](https://brieform.app/install): pick your client
- [Claude](https://brieform.app/install/claude)
- [Claude Code](https://brieform.app/install/claude-code)
- [ChatGPT](https://brieform.app/install/chatgpt)
- [Cursor](https://brieform.app/install/cursor)
- [VS Code](https://brieform.app/install/vscode)
- [Le Chat](https://brieform.app/install/lechat)
- [Perplexity](https://brieform.app/install/perplexity)
- [Any other MCP client](https://brieform.app/install/other
…

Related sites

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=brieform.app · GET /v1/domain/brieform.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for brieform.app:
1. POST https://agentwebmap.com/v1/sites/brieform.app/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://brieform.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/brieform.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/brieform.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.