FlowCastle

What FlowCastle MCP server does

The FlowCastle MCP server gives AI agents an interface to FlowCastle, a hosted visual workflow builder for Telegram bots and web chat. An agent can work with flows, triggers, conditions, AI steps, payments, broadcasts, drip sequences, and connected services exposed by the platform. The repository also includes 23 JSON bot templates that serve as installable examples and references for flow structure.

The server is intended for developers who want to describe bot behavior in natural language while keeping the resulting workflow editable in FlowCastle’s visual editor. Actions created through MCP use the same block-based model as workflows built manually in the dashboard.

How it works

FlowCastle MCP server is exposed through Streamable HTTP at https://api.flowcastle.ai/api/mcp. Requests use an application-scoped API key in an Authorization: Bearer header. The key begins with app_ and is created from the FlowCastle dashboard by registering for an account, creating an application, and opening its API and MCP settings.

A typical agent workflow starts by reading the workspace with get_workspace_summary and get_flow_context. It can then draft an ordered batch of flow-builder operations, check that batch with validate_actions, and submit it through apply_actions. This supports both inspecting an existing workspace and making structured changes to it.

Setup and configuration

Set the application key in an environment variable such as FLOWCASTLE_MCP_TOKEN, or place the key directly in the MCP client configuration. Claude Code can register the remote endpoint with an HTTP transport and an authorization header. Codex can use the endpoint with its bearer-token environment-variable option. Other MCP clients can use a configuration containing the endpoint URL and authorization header.

The repository documents configurations for Claude Code, Codex, Cursor, and any MCP-capable client. No local server process or SDK installation is described in the provided setup; the MCP endpoint is hosted by FlowCastle.

Tools and capabilities

The documented server exposes 16 tools. The provided material identifies these capabilities:

• Read workspace and flow state with get_workspace_summary and get_flow_context.
• Search available bot examples with search_flow_examples.
• Retrieve a selected template with get_flow_example.
• Validate an ordered action batch with validate_actions.
• Apply flow-builder actions with apply_actions.
• Create or update flows using operations such as create_flow, create_block, create_link, and create_variable.

Templates cover complete bot definitions, including metadata, suggested variables, required modules, and action schemas. They can be installed from the template gallery, accessed through MCP, or used as examples when designing a custom flow.

Limitations and notes

The MCP interface manages FlowCastle workflows; it does not replace the FlowCastle dashboard or visual editor. The repository describes the public REST API separately for contacts, contact variables, goal events, flow sends, and broadcasts, so those functions should not be assumed to be MCP tools unless the tool reference confirms them.

An application key is required for authenticated access. The supplied material does not document a local or self-hosted deployment, offline operation, rate limits, or the complete list of all 16 tool names. Review the server’s MCP reference before depending on undocumented operations or schemas.