Agents Index

FlowCastle

Online

Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.

Visit publisherConnectJSON

What it can do: 65 tools

  • list_applications read-onlyList 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 other tool needs an explicit applicationId, which this tool sup
  • create_applicationCreate a new application (workspace) owned by the caller. Requires a personal API key (usr_...) — application-scoped keys cannot create applications. Seeds default flows unless skipDefaultFlows is true. Creates persisten
  • update_applicationUpdate application-level settings (name, active state, default language, language for everyone else, incoming-message behavior, the member notice when AI credits run out). Requires the manage_settings permission in that
  • import_website_knowledgeCrawl 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. Honours robots.txt, skips junk and duplicate pages, keeps blog pos
  • get_knowledge_base_document read-onlyReturn the FULL text of one knowledge-base document, with contentSha256 — the hash edit_knowledge_base_text_document quotes as expectedSha256. Read-only. get_workspace_summary and get_application_context show each docume
  • get_website_import read-onlyStatus of a website import started by import_website_knowledge or an import_website_into_knowledge_base action: stage, progress, counters, warnings and the pages that were not imported. Read-only. Poll until status is DO
  • list_watched_groups read-onlyList 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 processes: messages from unlisted group/channel chats are dropped (f
  • list_telegram_operations read-onlyDiscover supported Telegram MTProto account operations, input schemas, permissions and limits. Requires manage_broadcasts. All current operations read public data; this catalog does not connect to Telegram. botId may be
  • execute_telegram_operationSubmit 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 until completed, error or timed_out. Req
  • get_telegram_operation read-onlyRead a Telegram operation status and result using its requestId and the same applicationId/botId used for submission. Requires manage_broadcasts for the owning application. Poll every two seconds. Results expire one hour
  • set_watched_groupsReplace a telegram_mtproto userbot's watched-groups list — the chats it monitors. Requires the manage_settings permission. SET semantics: send the COMPLETE desired list every time (call list_watched_groups first and incl
  • sync_dialog_contactsImport a telegram_mtproto userbot's existing chats as contacts — DM partners, groups, and channels — so everything the account already talks to becomes a contact send_message can target without waiting for each chat to m
  • get_workspace_summary read-onlyReturn a compact application, flow, sequence, operation, and bot summary — the cheapest way to orient in a workspace. Read-only, no side effects. Deliberately omits variables and full flow graphs: use get_variable_contex
  • get_variable_context read-onlySearch variable definitions by scope and keyword, or read one variable by id. Read-only. Returns { variables, total, returned, truncated } — compare returned against total to detect a cut-off result set and re-call with
  • get_application_context read-onlyReturn the full application-level automation context in one read-only call: every flow (with folders), connected bots, variables, sequences, and operations. This is the broad orientation call — prefer get_workspace_summa
  • get_module_catalog read-onlyReturn a compact index of both installed and available marketplace modules, with each module's key, versions, description, actions, and triggers. Read-only. Start here when you need a capability the core action kinds do
  • get_module_details read-onlyReturn everything needed to use one module: action input fields and their types, trigger configuration, manual setup fields (credentials an operator must fill in the dashboard), and references to already-installed action
  • install_moduleInstall an exact marketplace module version into an application and create any missing installed-template actions. Requires the manage_automation permission. Call get_module_catalog first to select the module and version
  • search_flows read-onlyFind every flow and block whose contents contain a keyword. Read-only. Searches message text and its translations, button labels and URLs, action names and configs, action input/output field paths and values, condition o
  • get_flow_context read-onlyReturn one flow's graph topology: its blocks in reading order from the start block, a short summary per block, and where each block and each menu button leads (links[].to, menu.buttons[].to). Read-only. Deliberately omit
  • get_block_details read-onlyReturn the complete contents of one block: block data, action configs, HTTP request bodies, custom-code files, triggers, menu payloads, and media paths. Read-only. This is the heaviest read in the API — call get_flow_con
  • get_action_schema read-onlyRead-only, needs no API key. The action-authoring contract apply_actions batches are validated against. With NO arguments, returns an INDEX of block types, actions, action kinds and topics with descriptions and sizes. Th
  • get_design_guidelines read-onlyReturn 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 examples. Read-only, needs no API key. Called with NO arguments
  • get_funnel_analytics read-onlyReturn the measured conversion funnels of the workspace's ENTRY flows over the last 14 days, busiest first: how many new contacts entered, which blocks they reached, the share who stop at each block, which buttons lead n
  • get_flow_analytics read-onlyMeasure how NAMED flows are actually used over the last 14 days: how many contacts entered each one, where inside it they stop (per block, with the stop RATE), how many were answered by a human agent afterwards, and how
  • get_survey_results read-onlyRead what customers ANSWERED in this workspace's surveys. A survey is any flow marked isSurvey: its choice questions record which option each contact tapped, and its free-text questions store the reply the contact typed.
  • search_flow_examples read-onlySearch the library of reusable flow examples covering common business cases (lead capture, onboarding, payments, reminders). Read-only, needs no API key. Returns summaries to choose by — id, title, summary, useWhen, tags
  • get_flow_example read-onlyReturn 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 search_flow_examples first to find the id.
  • validate_actions read-onlyDry-run validation of a proposed batch of flow-builder actions. Mutates nothing and is safe to repeat. OPTIONAL: apply_actions runs this exact validation itself and applies nothing when invalid, so calling validate_actio
  • apply_actionsValidate and apply a batch of flow-builder actions — the single write path for editing flows, blocks, variables, broadcasts, sequences, and folders. Call this directly; a separate validate_actions call beforehand is unne
  • deploy_applicationPublish 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 DRAFT graph. Until this runs the connected bots keep serving th
  • run_flow_autotest read-onlyRuns deterministic behavioural tests against flows that are ALREADY applied (compiles them to an AST and simulates a user). Call after apply_actions to verify a build; read `summary` and the failed checks, patch with app
  • send_messageSend a message to ONE contact right now, outside any flow. For reaching many contacts use a broadcast instead. Target the contact with contactId (globally unique — preferred), or with platformId (the platform-side id, e.
  • send_flow_to_contactsRun 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 message is the flow — its first block's text, media and buttons ar
  • read_messages read-onlyRead 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 as it handled each turn — inbound messages are recorded before
  • list_contacts read-onlyList and search contacts in the application, paginated, newest first. Read-only. Filters combine as AND; search matches name, username, email, phone, and platformId; `tags` / `tagIds` keep only contacts carrying at least
  • list_bot_chats read-onlyList the groups and channels the application's bots were added to, newest first: title, kind, the numeric chatId a flow uses to address the chat, when the bot was added, and the bot's status and rights there (is it an ad
  • list_contact_tags read-onlyList 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 tags ("utm: <slug>", set by ?start=utm--<slug> deep links, one
  • get_contact read-onlyReturn 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 always redacted. Call list_contacts first to find the contactId.
  • get_contact_activity read-onlyReturn one contact's engagement history: goals they achieved and buttons they clicked, newest first, plus all-time goal totals. Read-only. This is the per-contact companion to get_broadcast_analytics (which is aggregate)

…and 25 more.

Connect it

Claude Code
claude mcp add --transport http flowcastle https://api.flowcastle.ai/api/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.flowcastle.ai/api/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "flowcastle": {
      "url": "https://api.flowcastle.ai/api/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "flowcastle": {
      "type": "http",
      "url": "https://api.flowcastle.ai/api/mcp"
    }
  }
}

Questions

What does FlowCastle do?

Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. It exposes 65 tools to AI assistants.

What tools does FlowCastle provide?

65 tools, including list_applications, create_application, update_application, import_website_knowledge, get_knowledge_base_document, get_website_import, list_watched_groups, list_telegram_operations, execute_telegram_operation, get_telegram_operation, set_watched_groups, sync_dialog_contacts….

How do I connect FlowCastle to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.flowcastle.ai/api/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does FlowCastle require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is FlowCastle online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes FlowCastle?

flowcastle.ai. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Productivity & Docs