Add a server
1
Create MCP server
Open MCP, create a server, and give it a name. Choose a mode when offered:
- NORMAL — tools are used as explicitly pinned selections
- SMART (Meta) — broader discovery; you can constrain toolkit participation with whitelist or blacklist when the UI offers it
2
Load tools
Open Tools on the server row, sync the tool list, and choose which tools to expose.
3
Install and config
For most clients, skip a server ID and use the hosted endpoint
https://mcp.flowra.dev/mcp. First request creates a default META server for the project. Pages: Agents.Open Install & Config. Prefer Sign in (OAuth) for Cursor or Claude — paste the URL with no headers; the client opens Flowra sign-in and you pick a project. Use the API key tab for CI or clients that cannot run OAuth (x-api-key plus x-username).Use a named server (pinned NORMAL tools) when you need a fixed tool list. The same OAuth / API key choice applies to that server’s URL.External MCP by URL
In tool-selection modals you can sometimes load tools from an external MCP base URL (optional headers), then select tools. Those picks are stored with the agent like other MCP selections.Tips
- Give credentials only the access the automation needs.
- If tools do not appear, re-check server health and mode, then revisit Toolkits and tools.
- MCP servers are shared for the project. OAuth binds the client to the project you pick at consent. Use x-username (or the End user switcher when testing) so each end user keeps separate connections.
- Bind toolkit App credentials when the UI asks which project credentials each toolkit uses — App credentials.