activate_flow — postari MCP Tool
activate_flow
(activate flow) is one of 37 tools on the
postari
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call activate_flow from your client
- Claude Code postari activate_flow run in your project directory
- Claude Desktop postari activate_flow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor postari activate_flow ~/.cursor/mcp.json
- VS Code postari activate_flow .vscode/mcp.json
- Zed postari activate_flow ~/.config/zed/settings.json
- Windsurf postari activate_flow ~/.codeium/windsurf/mcp_config.json
- Cline postari activate_flow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI postari activate_flow ~/.gemini/settings.json
- Grok postari activate_flow .mcp.json (in your project root)
- ChatGPT postari activate_flow Settings → Connectors → Advanced → Developer mode
- Claude.ai postari activate_flow Settings → Connectors → Add custom connector
- LangChain postari activate_flow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http postari https://postari.io/api/mcp
Other tools on this server
- send_transactional_email
- create_subscriber
- get_subscriber
- update_subscriber
- clean_bounced_subscribers
- list_lists
- create_list
- add_subscriber_to_list
- tag_subscribers
- trigger_flow
- account_stats
- list_campaigns
- get_campaign_stats
- launch_campaign
- diagnose_deliverability
- get_agent_activity
- create_launch
- list_launches
- get_launch
- link_campaign_to_launch_stage
- create_flow
- update_flow
- test_flow
- arm_flow
- list_flow_emails
- update_flow_email
- create_form
- update_form
- create_segment
- create_template
- create_tag
- create_landing
- list_landings
- update_landing
- set_campaign_audience
- get_campaign_audience
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.