1
MCP server URL
mcp.flowra.dev/mcp
✓ streamable HTTP
Register the URL
Add https://mcp.flowra.dev/mcp as a streamable HTTP server in the client. Exact JSON is on each client page.
One MCP URL for the project
https://mcp.flowra.dev/mcp is streamable HTTP. First request creates a default META server for the project. A pinned server is the same host: https://mcp.flowra.dev/mcp/{serverId}.
Any MCP client
Paste this into your agent
It fetches this page, follows the setup for the client it is running in, and wires itself up.
or add the endpoint yourself
- Sign in with Flowra, or a project API key
- 50,000+ tools over one endpoint
- 1,077 apps on one connection
Pick your client
Connect your agent to Flowra tools
Each page has the exact command or config for that client, then how to check the tools are live.
- ClaudeOne claude mcp add command. Sign in when prompted.
- CursorOne JSON block in .cursor/mcp.json, committed with the repo.
- CodexOne block in ~/.codex/config.toml, shared by every Codex client.
- OpenClawOne gateway-wide server, so every channel gets the tools.
- HermesOne HTTP MCP server, added from Hub or config.yaml.
- GrokOne HTTP connector from the Grok workspace. Nothing to install.
- ChatGPTCustom connector URL. Sign in with Flowra OAuth, or send an API key if the plan requires headers.
How it works
From one URL to live tools
2
Flowra sign-in
Google · GitHub · email
✓ project connected
Sign in with Flowra
Leave headers empty. The client opens Google, GitHub, or email, then you pick a project. An API key is only for CI.
3
your agent · flowra
- FLOWRA_DISCOVER_TOOLS
- FLOWRA_GET_TOOL_SCHEMAS
- ✓ ready to run
Discover, then run
FLOWRA_DISCOVER_TOOLS → FLOWRA_GET_TOOL_SCHEMAS → FLOWRA_MANAGE_CONNECTIONS if an app is disconnected → FLOWRA_MULTI_EXECUTE_TOOL.
Meta tools
Four meta tools. The catalog on demand.
The client does not load the whole catalog. Discover, schema, connect, run.
Discover
FLOWRA_DISCOVER_TOOLS
Search the catalog (Gmail, Slack, GitHub, …) without loading every tool into context.
Schemas
FLOWRA_GET_TOOL_SCHEMAS
Fetch arguments before you call. Do not invent fields.
Connect
FLOWRA_MANAGE_CONNECTIONS
Start OAuth for a toolkit and hand the user the link. App OAuth is not MCP login.
Run
FLOWRA_MULTI_EXECUTE_TOOL
Execute one or more tools. Risky sends can still wait on a Flowra approval gate.
For AI agents
This page is the instruction set. Point your agent at it.
Tell your agent to set up Flowra from this URL. The same text you are reading is what it follows.
flowra.dev/mcp
## For AI agents reading this page You are reading https://flowra.dev/mcp. Flowra is an AI agent and workflow platform: one sentence, connected apps, an approval gate before risky sends, a run ledger. 1. Register the MCP server in the client you are running in. URL: https://mcp.flowra.dev/mcp No headers. The client opens Flowra sign-in (Google, GitHub, or email); the user picks a project. For CI, x-api-key and x-username: project_default_user still work. Do not invent a key. 2. Verify before you continue. List MCP tools. You should see FLOWRA_DISCOVER_TOOLS, FLOWRA_GET_TOOL_SCHEMAS, FLOWRA_MANAGE_CONNECTIONS, FLOWRA_MULTI_EXECUTE_TOOL. If the server is not connected, stop and say so. 3. Find the job with FLOWRA_DISCOVER_TOOLS, load schemas with FLOWRA_GET_TOOL_SCHEMAS, connect with FLOWRA_MANAGE_CONNECTIONS if needed, then FLOWRA_MULTI_EXECUTE_TOOL. 4. Tell the user which apps the connection can reach and what you can do next. Reference: https://mcp.flowra.dev/mcp · https://docs.flowra.dev/guides/mcp · https://flowra.dev/mcp
Frequently asked questions
Give your agent the tools
One URL, sign in, then discover. Start free.
- 50,000+ tools
- One endpoint
- Flowra sign-in