# FlowCastle (slim) > FlowCastle, an MCP server by flowcastle.ai, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. - Full: https://www.anchorterminal.com/tools/flowcastle.md (~3,200 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/tools/flowcastle.json · canonical https://www.anchorterminal.com/tools/flowcastle - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04 # FlowCastle > Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/ - Kind: MCP server, by flowcastle.ai (https://flowcastle.ai) - Category: Messaging APIs (https://www.anchorterminal.com/categories/messaging.md) - Listed because: It's published in the registry under flowcastle.ai, a namespace the registry only gives to whoever proves they control that domain. - What the official MCP registry says: Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. ## Facts - MCP registry: `ai.flowcastle/flowcastle` 1.0.0 - Endpoint: https://api.flowcastle.ai/api/mcp (streamable HTTP) - Source: https://github.com/FlowCastle/telegram-bot-templates - Website: https://flowcastle.ai - GitHub stars: 2 - Registry entry updated: 2026-07-14 ## Tools - Tools it lists (51, about 23,976 tokens of context, `tools/list` without credentials over MCP 2025-11-25, checked 2026-10-04 22:20 UTC): - `list_applications` (read-only): List the applications this API key can access, with the caller role and the permissions it grants. Start here when using a personal API key (usr_...): every… - `create_application` (writes): Create a new application (workspace) owned by the caller. Requires a personal API key (usr_...) — application-scoped keys cannot create applications. Seeds… - `update_application` (writes): Update application-level settings (name, active state, default language, language for everyone else, incoming-message behavior). Requires the manage_settings… - `import_website_knowledge` (writes): Crawl a website into a knowledge base so an AI_TOOL_ROUTER can answer from it. Creates a new base (named after the host) unless knowledgeBaseId is given.… - `get_website_import` (read-only): Status of a website import started by import_website_knowledge or an import_website_into_knowledge_base action: stage, progress, counters, warnings and the… - `list_watched_groups` (read-only): List the group/channel chats a telegram_mtproto userbot monitors. Read-only. The watched list is the single source of truth for which chats the userbot… - `list_telegram_operations` (read-only): Discover supported Telegram MTProto account operations, input schemas, permissions and limits. Requires manage_broadcasts. All current operations read public… - `execute_telegram_operation` (writes): Submit one supported read operation on the connected telegram_mtproto account. Call list_telegram_operations for the input schema. Returns a requestId; poll… - `get_telegram_operation` (read-only): Read a Telegram operation status and result using its requestId and the same applicationId/botId used for submission. Requires manage_broadcasts for the owning… - `set_watched_groups` (writes): Replace a telegram_mtproto userbot's watched-groups list — the chats it monitors. Requires the manage_settings permission. SET semantics: send the COMPLETE… - `sync_dialog_contacts` (writes): Import a telegram_mtproto userbot's existing chats as contacts — DM partners, groups, and channels — so everything the account already talks to becomes a valid… - `get_workspace_summary` (read-only): Return a compact application, flow, sequence, operation, and bot summary — the cheapest way to orient in a workspace. Read-only, no side effects. Deliberately… - `get_variable_context` (read-only): Search variable definitions by scope and keyword. Read-only. Returns { variables, total, returned, truncated } — compare returned against total to detect a… - `get_application_context` (read-only): Return the full application-level automation context in one read-only call: every flow (with folders), connected bots, variables, sequences, and operations.… - `get_module_catalog` (read-only): Return a compact index of both installed and available marketplace modules, with each module's key, versions, description, actions, and triggers. Read-only.… - `get_module_details` (read-only): Return everything needed to use one module: action input fields and their types, trigger configuration, manual setup fields (credentials an operator must fill… - `install_module` (writes): Install an exact marketplace module version into an application and create any missing installed-template actions. Requires the manage_automation permission.… - `search_flows` (read-only): Find every flow and block whose contents contain a keyword. Read-only. Searches message text and its translations, button labels and URLs, action names and… - `get_flow_context` (read-only): Return one flow's graph topology: its blocks, how they link, and a short summary per block. Read-only. Deliberately omits block data and action configs to stay… - `get_block_details` (read-only): Return the complete contents of one block: block data, action configs, HTTP request bodies, custom-code files, triggers, menu payloads, and media paths.… - `get_action_schema` (read-only): Return the action-authoring contract that apply_actions batches are validated against. Read-only, needs no API key. Called with NO arguments it returns a… - `get_design_guidelines` (read-only): Return the flow-design rules that validation does NOT enforce: when to split a branch into its own flow, how navigation and menus must be wired, and worked… - `get_funnel_analytics` (read-only): Return the measured conversion funnels of the workspace's ENTRY flows over the last 30 days, busiest first: how many new contacts entered, which blocks they… - `get_flow_analytics` (read-only): Measure how NAMED flows are actually used over the last 30 days: how many contacts entered each one, where inside it they stop (per block, with the stop RATE),… - `get_survey_results` (read-only): Read what customers ANSWERED in this workspace's surveys. A survey is any flow marked isSurvey: its choice questions record which option each contact tapped,… - `search_flow_examples` (read-only): Search the library of reusable flow examples covering common business cases (lead capture, onboarding, payments, reminders). Read-only, needs no API key.… - `get_flow_example` (read-only): Return one reusable flow example by id, optionally with a complete action batch you can adapt and pass to apply_actions. Read-only, needs no API key. Call… - `validate_actions` (read-only): Dry-run validation of a proposed batch of flow-builder actions. Mutates nothing and is safe to repeat. OPTIONAL: apply_actions runs this exact validation… - `apply_actions` (writes): Validate and apply a batch of flow-builder actions — the single write path for editing flows, blocks, variables, broadcasts, sequences, and folders. Call this… - `deploy_application` (writes): Publish the workspace to its bots — the API equivalent of the dashboard's Deploy button. This is the step that makes edits live. apply_actions writes to the… - `run_flow_autotest` (read-only): Runs deterministic behavioural tests against flows that are ALREADY applied (compiles them to an AST and simulates a user). Call after apply_actions to verify… - `send_message` (writes): Send a message to ONE contact right now, outside any flow. For reaching many contacts use a broadcast instead. Target the contact with contactId (globally… - `send_flow_to_contacts` (writes): Run an EXISTING interactive flow for each listed contact right now, outside any trigger — as if each of them had just triggered it. Use it when the WHOLE… - `read_messages` (read-only): Read the message transcript: what users sent the bot and what the bot sent back, newest first. Source is the runtime's own message ledger, written by the bot… - `list_contacts` (read-only): List and search contacts in the application, paginated, newest first. Read-only. Filters combine as AND; search matches name, username, email, phone, and… - `list_contact_tags` (read-only): List the contact tags in use in the application (or one bot) with how many contacts carry each, most-used first. Read-only. This is the attribution view: UTM… - `get_contact` (read-only): Return one contact's full profile plus every contact-variable value stored for them. Read-only. Values may hold personal data; variables of type SECRET are… - `get_contact_activity` (read-only): Return one contact's engagement history: goals they achieved and buttons they clicked, newest first, plus all-time goal totals. Read-only. This is the… - `list_event_contacts` (read-only): The reverse lookup: which contacts triggered one analytics event — achieved a goal (kind GOAL + goalKey), clicked a button (BUTTON_CLICK + blockId, optionally… - `create_contact` (writes): Create a contact manually — for imports or externally-sourced audiences; contacts who message a bot are created automatically. Requires the manage_broadcasts… - `update_contact` (writes): Update a contact's profile fields and/or contact-variable values. Requires the manage_broadcasts permission. Only the fields you pass are changed — omitted… - `list_broadcasts` (read-only): List broadcasts in the application with status, schedule, and delivery counts. Read-only. Filters combine as AND. Note that delivery counts report messages… - `get_broadcast_details` (read-only): Return full details for a single broadcast: status, schedule, recurrence rule, linked flow, and delivery breakdown by status. Read-only. Call list_broadcasts… - `get_broadcast_analytics` (read-only): Return engagement analytics for a broadcast: delivery breakdown by status plus per-message-block sent and clicked counts for its flow, over an optional date… - `list_pulse_items` (read-only): List Pulse items — the workspace attention queue. Two kinds: `attention` is an observed problem a detector found (failing flows, a failed broadcast, an… - `get_pulse_item` (read-only): Return one Pulse item in full: the measured evidence, the ids of the conversations and execution-log rows behind it, and the change Apply would build if the… - `update_pulse_item` (writes): Change one Pulse item's state. Every action changes the queue for the WHOLE workspace — an item belongs to the workspace, not to whoever called the tool, so… - `list_follow_up_tasks` (read-only): List follow-up tasks — reminders for a person to get back to a contact. Read-only, ordered by due time so overdue work comes first. A follow-up sends nothing… - `create_follow_up_task` (writes): Create a follow-up reminder for a person to get back to a contact. Creates persistent state and is NOT idempotent: calling it twice creates two reminders.… - `update_follow_up_task` (writes): Close, reopen, snooze, or reschedule one follow-up task. Completing it records that a person handled the reminder — it does not message the contact. Snoozing… - `query_flow_logs` (read-only): Read the bot execution log (flow_execution_log) — the record of what the runtime actually did, and the only place that separates "the action ran" from "the… - How its tools read to an agent (0 errors, 6 warnings, 1 note, about 23,976 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score): - warn TC07 apply_actions: the description is about 672 tokens - warn TC07 send_message: the description is about 550 tokens - warn TC11 execute_telegram_operation: 2 parameters without a description: botId, operation - warn TC11 get_telegram_operation: 2 parameters without a description: botId, requestId - warn TC11 list_telegram_operations: 1 parameter without a description: botId - warn TC23 server: 51 tools, about 23,500 tokens of definitions - note TC24 server: 51 of 51 tools have no outputSchema - JSON: https://www.anchorterminal.com/api/v1/tools/flowcastle.json - Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming