FlowCastle
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http flowcastle 'https://api.flowcastle.ai/api/mcp' --header 'Authorization: <Bearer <application API key> — create one in the FlowCastle dashboard: application, API page, MCP tab (keys start with app_)>'
{
"mcpServers": {
"flowcastle": {
"type": "http",
"url": "https://api.flowcastle.ai/api/mcp",
"headers": {
"Authorization": "<Bearer <application API key> — create one in the FlowCastle dashboard: application, API page, MCP tab (keys start with app_)>"
}
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Telegram bot templates + MCP server for AI bot development
Ready-to-use Telegram bot templates and an MCP server — build, edit, and deploy Telegram bots from Claude Code, Codex, Cursor, or any MCP-capable AI agent. No SDK boilerplate: describe the bot, and your agent assembles the flow.
FlowCastle is a visual workflow builder for Telegram bots and web chat: flows, triggers, conditions, AI steps, payments (Stripe / YooKassa / Telegram Stars), broadcasts, drip sequences, and integrations (Gmail, Google Sheets, Notion, OpenAI, …) — with a REST API and an MCP server, so bot development works straight from your AI coding agent. Every block an agent creates through MCP is the same block you can drag, wire, and edit visually.
This repo is for developers. It contains:
| Path | What it is |
|---|---|
templates/ | 23 production bot templates as JSON — the same source that powers the template gallery and the MCP get_flow_example tool |
mcp/ | MCP server reference: endpoint, auth, all 16 tools, and a snapshot of the flow-action schema used by apply_actions |
Build a bot from your AI agent (MCP)
FlowCastle exposes an MCP server over Streamable HTTP:
POST https://api.flowcastle.ai/api/mcp
Authorization: Bearer <your-application-api-key> # starts with app_
Get a key: sign up → create an application → API page → MCP tab.
Claude Code
export FLOWCASTLE_MCP_TOKEN='<your-application-api-key>'
claude mcp add --transport http flowcastle https://api.flowcastle.ai/api/mcp \
--header "Authorization: Bearer $FLOWCASTLE_MCP_TOKEN"
Codex
codex mcp add flowcastle \
--url https://api.flowcastle.ai/api/mcp \
--bearer-token-env-var FLOWCASTLE_MCP_TOKEN
Cursor / any MCP client (JSON config)
{
"mcpServers": {
"flowcastle": {
"type": "http",
"url": "https://api.flowcastle.ai/api/mcp",
"headers": {
"Authorization": "Bearer <your-application-api-key>"
}
}
}
}
Then just ask your agent things like:
"Look at my FlowCastle workspace and add a lead-qualification flow: greet on /start, ask three button questions, save answers to contact variables, and notify me."
The agent reads your workspace with get_workspace_summary / get_flow_context, drafts a batch of flow-builder actions, checks it with validate_actions, and applies it with apply_actions. See mcp/README.md for the full tool reference.
Templates
Each JSON file in templates/ is a complete bot: metadata (title, summary, use-cases, suggested variables, required modules) plus a schemaExample.actions array — an ordered batch of create_flow / create_block / create_link / create_variable operations in the exact format apply_actions accepts.
Three ways to use them:
- One-click install from the gallery: flowcastle.ai/templates
- Via MCP — ask your agent to
search_flow_examples/get_flow_exampleand apply one (optionally customized) to your workspace - As reference — study how real flows wire triggers, conditions, wait-for-reply steps, payments, and AI blocks
Full index and format description: templates/README.md.
REST Public API
Application-scoped REST API for contacts, contact variables, goal events, flow sends, and broadcasts:
- Base URL:
https://api.flowcastle.ai/api/public/v1 - Interactive docs (Swagger): https://api.flowcastle.ai/api/public/docs
- OpenAPI spec: https://api.flowcastle.ai/api/public/openapi.json
Auth uses the same app_… application key (Authorization: Bearer or X-API-Key).
Guides
Step-by-step builds on the FlowCastle blog:
- Build a Lead Bot in Telegram in 10 Minutes
- Build an AI Support Bot for Telegram
- I Replaced My Morning Apps With One Telegram Bot
Links
- Product: https://flowcastle.ai
- Dashboard: https://dashboard.flowcastle.ai
- Template gallery: https://flowcastle.ai/templates
- API docs: https://api.flowcastle.ai/api/public/docs
Contributing
Found a bug in a template, or built a flow worth sharing? Open an issue or PR — templates are plain JSON, and validate_actions (via MCP) will tell you if a batch is well-formed.
License
The contents of this repository are licensed under the MIT License.
Questions fréquentes
Qu'est-ce que FlowCastle ?
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.
Comment installer FlowCastle ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http flowcastle 'https://api.flowcastle.ai/api/mcp' --header 'Authorization: <Bearer <application API key> — create one in the FlowCastle dashboard: application, API page, MCP tab (keys start with app_)>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour FlowCastle ?
Oui. Il attend Authorization, à renseigner dans sa configuration.
FlowCastle est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient FlowCastle ?
Il est publié par FlowCastle. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.