get_flow_example — FlowCastle MCP Tool Read-only
get_flow_example
(get flow example) is one of 51 tools on the
FlowCastle
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_flow_example from your client
- Claude Code FlowCastle get_flow_example run in your project directory
- Claude Desktop FlowCastle get_flow_example ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FlowCastle get_flow_example ~/.cursor/mcp.json
- VS Code FlowCastle get_flow_example .vscode/mcp.json
- Zed FlowCastle get_flow_example ~/.config/zed/settings.json
- Windsurf FlowCastle get_flow_example ~/.codeium/windsurf/mcp_config.json
- Cline FlowCastle get_flow_example ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FlowCastle get_flow_example ~/.gemini/settings.json
- Grok FlowCastle get_flow_example .mcp.json (in your project root)
- ChatGPT FlowCastle get_flow_example Settings → Connectors → Advanced → Developer mode
- Claude.ai FlowCastle get_flow_example Settings → Connectors → Add custom connector
- LangChain FlowCastle get_flow_example pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http flowcastle https://api.flowcastle.ai/api/mcpOther tools on this server
- list_applications
- create_application
- update_application
- import_website_knowledge
- get_website_import
- list_watched_groups
- list_telegram_operations
- execute_telegram_operation
- get_telegram_operation
- set_watched_groups
- sync_dialog_contacts
- get_workspace_summary
- get_variable_context
- get_application_context
- get_module_catalog
- get_module_details
- install_module
- search_flows
- get_flow_context
- get_block_details
- get_action_schema
- get_design_guidelines
- get_funnel_analytics
- get_flow_analytics
- get_survey_results
- search_flow_examples
- validate_actions
- apply_actions
- deploy_application
- run_flow_autotest
- send_message
- send_flow_to_contacts
- read_messages
- list_contacts
- list_contact_tags
- get_contact
- get_contact_activity
- list_event_contacts
- create_contact
- update_contact
- list_broadcasts
- get_broadcast_details
- get_broadcast_analytics
- list_pulse_items
- get_pulse_item
- update_pulse_item
- list_follow_up_tasks
- create_follow_up_task
- update_follow_up_task
- query_flow_logs
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.