MCP-Typebot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPEBOT_TOKEN | Yes | Your Typebot API token | |
| TYPEBOT_WORKSPACE_ID | Yes | Your Typebot workspace ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createBotB | Crea un nuevo Typebot. Requiere “name”, opcional “description” |
| listBotsC | Lista todos los Typebots de un workspace |
| getBotC | Recupera un Typebot por su ID |
| updateBotC | Actualiza un Typebot existente (p.ej. cambia nombre) |
| deleteBotC | Elimina un Typebot por su ID |
| publishBotC | Publica un Typebot existente |
| unpublishBotC | Despublica un Typebot existente |
| listResultsC | Lista resultados de un Typebot |
| startChatC | Inicia un chat con un Typebot. Requiere botId, opcional chat.context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Typebot domain. For example, createBot, getBot, updateBot, and deleteBot handle the bot lifecycle, while publishBot/unpublishBot manage publication status, and startChat/listResults cover interaction aspects. No tools appear to overlap in functionality.
All tool names follow a consistent verb_noun pattern with camelCase styling (e.g., createBot, listBots, updateBot). The verbs are descriptive and aligned with CRUD operations (create, get, update, delete, list) or specific actions (publish, unpublish, start), making the set predictable and readable.
With 9 tools, this server is well-scoped for managing Typebots, covering core operations like bot lifecycle (create, read, update, delete), listing, publishing, and interaction features (start chat, list results). Each tool earns its place without redundancy or obvious gaps in the domain.
The tool surface provides complete coverage for the Typebot management domain, including full CRUD operations for bots (createBot, getBot, updateBot, deleteBot), listing (listBots), publication control (publishBot, unpublishBot), and interaction capabilities (startChat, listResults). There are no apparent gaps that would hinder agent workflows.