.cursor/mcp.json (no API key):
FLOWRA_DISCOVER_TOOLS.
Per-server URLs from Install & Config still work if you want a pinned NORMAL tool set. Connecting Gmail or Slack is a separate toolkit OAuth step after MCP is connected.
API key instead of OAuth
Use this for CI or a client that cannot run the sign-in flow:Prerequisites
- A Flowra account and at least one project
- Cursor installed
Steps
1
Add the hosted URL in Cursor
Paste the OAuth config above into Cursor’s MCP settings (
.cursor/mcp.json or the MCP panel). Restart or reload MCP if Cursor requires it.2
Sign in and pick a project
Approve the Flowra consent page. Choose the project whose tools you want. Details: MCP in the dashboard.
3
Optional: pin tools in the dashboard
Open MCP Servers if you need a named NORMAL server. Use Install & Config and keep Sign in (OAuth) selected.
4
Smoke-test a tool
In Cursor Agent chat, ask it to list or call one of your Flowra tools (
FLOWRA_DISCOVER_TOOLS). Confirm the call succeeds.Verify
- Cursor shows the MCP server as connected
- A tool from your project appears and returns a successful result
Developers deep dive
- MCP — OAuth vs API key, Smart vs Normal, API registration
- Native tools: Meta — discovery tools used in Smart mode