FlowCastle’s MCP server for Telegram bot development enables building, editing, and deploying Telegram bots on a hosted visual flow platform. It supports integration with Claude Code, Codex, Cursor, or any MCP-capable AI agent, removing boilerplate by describing the bot and letting the agent assemble the flow.

🛠️ Key Features

Ready-to-use Telegram bot templates
MCP server for model-context protocol-based workflows
Visual flow builder for flows, triggers, conditions, and AI steps
No-code approach: describe the bot; agent assembles the flow
Supports payments blocks and external integrations

🚀 Use Cases

Create and deploy Telegram bots from AI agents
Rapid prototyping of chatbot workflows
Visual automation of Telegram bot interactions and logic
Flow-based bot templates for common tasks

⚡ Developer Benefits

No SDK boilerplate required
Interoperability with MCP-capable agents
Centralized server for building and deploying bots
Readme-excerpt-based quick-start guidance

⚠️ Limitations

Data and capabilities depend on FlowCastle hosting and MCP support
Template coverage may vary by bot type and plugin availability

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.

Dragging a connection onto empty canvas to create a payment block, then configuring a Telegram Stars product — no code

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:

code

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

bash

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

bash

codex mcp add flowcastle \
  --url https://api.flowcastle.ai/api/mcp \
  --bearer-token-env-var FLOWCASTLE_MCP_TOKEN

Cursor / any MCP client (JSON config)

json

{
  "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_example and 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:

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.

FlowCastle