Typebot Builder MCP

Safe, AI-assisted Typebot engineering through the Model Context Protocol.

Typebot Builder MCP is an independent community implementation for discovering, creating, editing, validating, snapshotting, restoring and publishing Typebot chatbots. Typebot remains the source of truth; no SQL, Redis, GitHub or n8n runtime dependency is required.

Status: v0.1.2. The API contract targets Typebot 3.19.0. Review the verification report and limitations before production adoption. A real ChatGPT Custom App connection has been verified on the IngeWeb deployment; authentication and workspace-admin behavior remain deployment-specific.

Capabilities

• Default stateless Streamable HTTP; optional STDIO with the same tools.

• Independent incoming bearer auth; OAuth resource-server validation of audience-bound RFC 9068 JWT access tokens; explicitly configurable none mode for isolated environments.

• Semantic groups/blocks/edges/variables/settings editing with current-hash preconditions.

• Versioned AI guidance (get_guidance) and Text shorthand normalized to Typebot richText for the tested baseline.

• Official contract and local graph validation, semantic diffs and explicit uncertainty.

• Before/after filesystem snapshots, generic webhook delivery, both or off.

• Verified snapshot inspection, diff and draft rollback.

• Publish/unpublish with validation; published-state inspection.

• Builder API preview conversations and smoke tests, classified as effectful.

• Persisted result search, structured result retrieval, full transcripts and result logs through official Typebot APIs.

• Docker-first non-root runtime, persistent snapshots and health endpoint.

No unrestricted full-bot overwrite tool is exposed. Preview can execute integrations. The server is not a full VCS, a Typebot runtime replacement or a browser-testing framework.

Related MCP server: mcp-typebot

Quick start

cp .env.example .env
# Set separate TYPEBOT_API_TOKEN and MCP_BEARER_TOKEN; use a Builder /api base URL.
docker compose up -d --build

The example binds to loopback. Configure authenticated HTTPS before remote use. For local execution: npm ci --ignore-scripts, npm run check, then node --env-file=.env src/main.js. Set MCP_TRANSPORT=stdio for a spawning client.

Documentation

• MVP specification

• Architecture and security

• Configuration

• Docker, STDIO and HTTP

• Tool reference

• Snapshots and webhook contract

• Results and conversation inspection

• OAuth/OIDC integration

• ChatGPT Custom App procedure and verification status

• Typebot compatibility

• Examples

• Contributing · Security

Important limits

Typebot permits a five-second timestamp conflict margin; hash checks narrow external editor races but cannot provide strict compare-and-swap. Run one writer instance and avoid simultaneous editor changes. Local validation cannot verify runtime integrations. Snapshots contain sensitive bot payloads and require private storage. Webhook delivery has no durable retry/outbox. OAuth is a resource server, not a Google identity platform. See the architecture document for exact failure and security behavior.

Prior art

These community projects demonstrated the Typebot + MCP use case:

• osdeibi/MCP-typebot

• hithereiamaliff/typebot-mcp

This project is not a fork and copies no implementation code from those projects. Official Typebot OpenAPI contract data is preserved with its upstream notice/license in vendor. Original implementation code is Apache-2.0; see LICENSE.

Typebot Builder MCP is not affiliated with, maintained by or endorsed by Typebot.

Ing. Pablo A Pico — IngeWeb — https://www.ingeweb.co/