Brieform

io.github.silentdanyPublished by GitHub account silentdanyv1.0.0Updated Oct 24, 2026

AI-native form builder: create, publish & read responses from Claude, ChatGPT & MCP.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Brieform is a remote, AI-native form builder that lets an assistant create and publish forms and read their responses.

What you can do
Create forms through the assistant and publish them for respondents to fill in. Read the responses collected from published forms. Manage the form-building workflow from within Claude, ChatGPT or another MCP client.
When to use it
Useful when you want an assistant to draft, publish and collect answers for forms without switching to a separate form-building tool.
Requirements
A remote MCP endpoint at brieform.app over streamable HTTP. OAuth authentication is required, so a Brieform account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Brieform account, so review the scopes requested during sign-in. Publishing forms and reading responses act on live data in your account; check what the assistant creates or exposes before sharing a form.

Installation

In SourceWeft

  1. Open Brieform in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.silentdany%2Fbrieform/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "brieform": {
      "type": "http",
      "url": "https://brieform.app/api/mcp/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.