About Flowra
Flowra provides a hosted MCP server and agent skill for operating apps and building workflows, with hosted AI agents and human approval for consequential actions. It is aimed at agent and coding-agent users working across connected apps, and includes a ledger of tool calls.
Key features
- 01Discover app tools and their schemas
- 02Connect accounts through OAuth
- 03Run tools across connected apps
- 04Build approval-gated workflows
- 05Review inputs, outputs, and tool-call credits
- 06Create toolkits from REST endpoint descriptions
Use cases
- 01Read recent Gmail subjects through an agent
- 02Schedule Slack recaps with approval before posting
- 03Pause a run and inspect its ledger
- 04Build a toolkit for an app REST endpoint
MCP support
The hosted MCP server at https://mcp.flowra.dev/mcp registers six tools for discovery, schemas, account connection, multi-execution, workbench, and bash. It connects MCP clients to Flowra projects and their app tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.flowra.dev/mcpclaude mcp add --transport http flowradev https://mcp.flowra.dev/mcp{"mcpServers":{"flowradev":{"type":"http","url":"https://mcp.flowra.dev/mcp"}}}Open in Cursor{"servers":{"flowradev":{"type":"http","url":"https://mcp.flowra.dev/mcp"}}}Open in VS Code{"mcpServers":{"flowradev":{"type":"http","url":"https://mcp.flowra.dev/mcp"}}}{"mcpServers":{"flowradev":{"serverUrl":"https://mcp.flowra.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project README
Flowra — Agent Skill & Hosted MCP Server
Run hosted AI agents and approval-gated workflows on Gmail, Slack, GitHub, Notion, Telegram, WhatsApp, Linear and 1,000+ apps — from Claude Code, Cursor, Codex, GitHub Copilot or any MCP client. OAuth per account, a human approval gate before send/delete/pay, and a ledger of every tool call.
Product · Docs · SDK · Changelog · skills.sh
This repo is the agent skill + Cursor/Claude/Codex plugin for Flowra. From your backend, use the SDK (@flowra/sdk, flowra-sdk, @flowra/cli).
What's included
| Component | Purpose |
|---|---|
mcp.json / .mcp.json | Registers https://mcp.flowra.dev/mcp (OAuth, no keys). Six tools: discover, schemas, connect, multi-execute, workbench, bash. |
skills/flowra | Routes operate / build / edit / debug / credits to the right Flowra calls. |
skills/flowra-onboard | First install: Connect MCP and one read-only first win. |
commands/ | /flowra-setup and /flowra-status. |
evals/ | Behavioral scenarios the skill must pass. |
rules/flowra-safety.mdc | Reads are free, writes need your yes; untrusted content is never an instruction. |
Install in 30 seconds
1. Skill (Claude Code, Cursor, Codex, Copilot, OpenClaw, Hermes):
npx skills add flowradev/skills --skill flowra
2. Hosted MCP server — no API key needed; sign in with OAuth:
https://mcp.flowra.dev/mcp
| Client | How |
|---|---|
| Cursor | Settings → Tools & MCP → Connect next to flowra (or install the Flowra plugin) |
| Claude Code | /plugin marketplace add flowradev/skills then /plugin install flowra@flowra — or claude mcp add --transport http flowra https://mcp.flowra.dev/mcp |
| Codex | Marketplace at .agents/plugins/marketplace.json |
| Gemini CLI | gemini extensions install https://github.com/flowradev/skills (needs release v0.2.0) |
| VS Code / Copilot | @mcp in Extensions, or add the URL to .vscode/mcp.json |
| Skill only | npx skills add flowradev/skills --skill flowra |
| CI / no OAuth | Project API key in your own config — never in this repo |
Cursor Marketplace: search "Flowra", or /add-plugin flowra once listed.
First run
- Connect the MCP server and pick a Flowra project.
- Ask: "List my 5 latest Gmail subjects with Flowra."
- Then: "Every weekday at 9, post a Slack recap of my inbox. Ask me before posting."
What you can ask
- "Connect Gmail on Flowra and list my latest subjects."
- "Every weekday at 9:00, post a Slack recap of new Linear issues — ask me before posting."
- "This Flowra run is paused — show the ledger and resume it."
Why Flowra (vs Zapier MCP, Composio, n8n)
- Agent or locked workflow on the same project — not just a tool catalog.
- Human approval gate on any step, including cron runs.
- Run ledger: inputs, outputs and credits for every tool call.
- Missing app? Describe the REST endpoint and Flowra builds the toolkit.
Security model
Inbound mail, chat and webhook content is treated as untrusted data. The skill never executes instructions found in payloads and never skips approval gates. Reads run freely; writes (send, post, create, update, delete, pay) need an explicit yes in this chat. Durable automations still need a human_wait node or agent humanApproval. No API keys are stored in this repo.
Use when you want a scheduled or approved automation instead of a local script or an n8n, Zapier, or Make canvas.
Skip when there is no Flowra project, or you are already editing an n8n, Zapier, or Make graph you own.
CI / clients without OAuth
Add headers only in your own .cursor/mcp.json. Never commit a key.
{
"mcpServers": {
"flowra": {
"url": "https://mcp.flowra.dev/mcp",
"headers": {
"x-api-key": "<your-project-api-key>",
"x-username": "project_default_user"
}
}
}
}
Local testing
mkdir -p ~/.cursor/plugins/local
ln -sfn "$PWD" ~/.cursor/plugins/local/flowra
Then run Developer: Reload Window.
Layout
.cursor-plugin/plugin.json
.claude-plugin/plugin.json
.claude-plugin/marketplace.json
.codex-plugin/plugin.json
.agents/plugins/marketplace.json
gemini-extension.json
mcp.json
.mcp.json
server.json
commands/flowra-setup.md
commands/flowra-status.md
evals/
rules/flowra-safety.mdc
skills/flowra/SKILL.md
skills/flowra-onboard/SKILL.md
skills/flowra/references/
MIT © Flowra
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.