Skip to main content
The Runflow connector lets Claude work with your Runflow workspace. You can ask Claude about your agents, open execution traces, create and resolve reviews, edit prompts and knowledge bases, and deploy agents, all from a conversation. It works in every Claude product that supports connectors: claude.ai, Claude Desktop, Claude Mobile and Claude Code.

​
What you need

  • A Runflow account with access to at least one workspace.
  • A Claude plan that supports custom connectors.
The connector uses the permissions you already have in Runflow. It can’t see or change anything your Runflow user can’t.

​
Connect in claude.ai or Claude Desktop

  1. Open Settings > Connectors.
  2. Find Runflow in the directory, or click Add custom connector and enter:
  3. Click Connect. A Runflow sign-in page opens.
  4. Sign in with your Runflow account and approve the requested access.
Claude now has access to the workspace you signed in to. Connectors added on claude.ai are also available in Claude Desktop and Claude Mobile.

​
Connect in Claude Code

Add the server with the Claude Code CLI:
The first time Claude Code calls a Runflow tool, it opens a browser tab so you can sign in. You can also run /mcp inside Claude Code and choose runflow > Authenticate.

​
What you can ask

  • “What agents do I have, and are any of them unhealthy?”
  • “Show me the last failed execution of my support agent and explain what went wrong.”
  • “List pending reviews and mark the oldest one as resolved.”
  • “Search my product docs knowledge base for the return policy.”
  • “Create a prompt called support-greeting with this text.”
  • “Deploy the support agent to staging and send it a test message.”
  • “Add a dashboard card with daily sales for the last 30 days.”
The full list of tools is in Public tools.

​
Permissions and confirmations

Every tool is marked either read-only or changes data:
  • Read-only tools, such as listing agents or reading a trace, run without asking.
  • Tools that change data, such as creating a prompt, deploying an agent or running a connector, are marked destructive. Claude asks you to confirm before each call.
Access is also limited by OAuth scope: The scopes you get depend on what your Claude client requests when it connects. Delete tools appear only when the token includes mcp:admin, and like every tool that changes data, they ask for confirmation before running. Details are in Scopes.

​
Switching workspaces

The connector works with one Runflow workspace at a time, the one you signed in to. To use another workspace, disconnect the connector and connect again, signing in with the account or workspace you want.

​
Disconnecting

In claude.ai or Claude Desktop, open Settings > Connectors, select Runflow and click Disconnect. In Claude Code, run:
To revoke access from the Runflow side as well, contact support@runflow.ai.

​
Security and privacy

  • Sign-in uses OAuth 2.1 with PKCE. Claude never sees your Runflow password.
  • Access tokens expire after one hour and are refreshed automatically. Revoking a client in Runflow invalidates its tokens immediately.
  • Every request is limited to the workspace in the token. Tool input can’t select another workspace.
  • Credentials are stored encrypted. The credential tools return names and metadata, never secret values.
Read the Runflow privacy policy. Report security issues as described in our security.txt.

​
Troubleshooting

Check that your browser isn’t blocking pop-ups for Claude. In Claude Code, run /mcp, select runflow and choose Authenticate to open the page again.
Your token may not have the scope the tool needs. Delete tools need mcp:admin, which your Claude client has to request when it connects.
The connector uses the workspace you signed in to. Disconnect, then connect again and sign in to the right workspace.

​
Support

Email support@runflow.ai with the time of the problem and what you asked Claude.