UnifiedFlows MCP server

Quick start

Add this URL to your AI client as a custom connector or remote MCP server:

https://unifiedflows-api.onrender.com/agents/mcp

1. Add the URL to your client. Pick your client in Connect your client.
2. Your client opens a browser window. Sign in to UnifiedFlows (or sign up free), choose a workspace and approve the permissions it asks for.
3. Ask for what you need. The assistant acts with your role in that workspace and nothing more.

What you can do

• Build agents: create agents from templates or from scratch, edit their state graphs as drafts, validate, publish and roll back versions.
• Trigger them: add schedules, app webhooks and manual triggers, and run published actions.
• Operate runs: start, cancel, retry and replay runs, and read each step’s tool calls and outputs.
• Stay in the loop: answer approval steps waiting for a person, and resolve incidents.

Connect your client

These steps add the UnifiedFlows management server. Menus move between releases, so check your client’s own MCP documentation if a step does not match.

claude mcp add --transport http unifiedflows https://unifiedflows-api.onrender.com/agents/mcp

codex mcp add unifiedflows --url https://unifiedflows-api.onrender.com/agents/mcp
codex mcp login unifiedflows

[mcp_servers.unifiedflows]
url = "https://unifiedflows-api.onrender.com/agents/mcp"

{
  "mcpServers": {
    "unifiedflows": {
      "url": "https://unifiedflows-api.onrender.com/agents/mcp"
    }
  }
}

code --add-mcp '{"name":"unifiedflows","type":"http","url":"https://unifiedflows-api.onrender.com/agents/mcp"}'

{
  "servers": {
    "unifiedflows": {
      "type": "http",
      "url": "https://unifiedflows-api.onrender.com/agents/mcp"
    }
  }
}

{
  "mcpServers": {
    "unifiedflows": {
      "serverUrl": "https://unifiedflows-api.onrender.com/agents/mcp"
    }
  }
}

gemini mcp add --transport http unifiedflows https://unifiedflows-api.onrender.com/agents/mcp

{
  "mcpServers": {
    "unifiedflows": {
      "httpUrl": "https://unifiedflows-api.onrender.com/agents/mcp"
    }
  }
}

{
  "context_servers": {
    "unifiedflows": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://unifiedflows-api.onrender.com/agents/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "unifiedflows": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://unifiedflows-api.onrender.com/agents/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "unifiedflows": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://unifiedflows-api.onrender.com/agents/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "unifiedflows": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://unifiedflows-api.onrender.com/agents/mcp"
      ]
    }
  }
}

Sign-in and permissions

OAuth (recommended)

• Your client signs you in to UnifiedFlows in the browser. On the consent screen you choose the workspace the client may use and approve the scopes it asks for. Its access is tied to that workspace.
• Every tool runs with your own role in the workspace (viewer, member, admin or owner), checked on every call. If you leave the workspace, the client loses access at once.
• A client approved for UnifiedFlows cannot use another product’s management server; each has its own URL and sign-in.

Workspace API key

Clients that can’t do OAuth can send a workspace API key as a bearer token. The workspace owner creates it in the app under Settings → API Access. It acts as the owner with every permission, so prefer OAuth where you can and keep the key secret.

Authorization: Bearer ud_…

# Claude Code
claude mcp add --transport http unifiedflows https://unifiedflows-api.onrender.com/agents/mcp --header "Authorization: Bearer ud_…"

Scopes

A tool also needs the right workspace role. The tables below list the minimum role; your role is checked as well as the scope.

Tools

43 tools. Tools marked Changes data are flagged as destructive, so most clients ask before running them; ones marked Confirm also need confirm: true.

Example prompts

• “Build an agent that reviews every new GitHub pull request and posts a summary to Slack.”
• “What is waiting for my approval? Approve the refund for order 1042.”
• “Why did the lead-enrichment agent fail this morning? Retry it.”
• “Run the lead-enrichment agent every weekday at 8am Pacific.”

Good to know

• Tool results are capped at 100,000 characters so they don’t flood your assistant’s context. List tools page through results (page, and limit up to 100).
• Agents start as drafts and run only when triggered. Runs started from your AI client count toward your plan’s agent runs, like any other run.
• The API allows up to 100 requests a minute from one IP address, MCP included.
• Plan limits and your workspace role apply exactly as in the app. See Pricing.

Security and revoking access

• Access tokens last one hour and only work with the server they were issued for. Refresh tokens last 30 days and are replaced every time they are used; reusing an old one revokes every token descended from it.
• Every sign-in uses PKCE (S256), so a stolen authorization code cannot be redeemed.
• To stop a client using your account, disconnect or remove UnifiedFlows in that client. Removing someone from the workspace cuts off their clients immediately.
• Workspace owners can rotate the API key in the app at any time.

See our Privacy Policy for how your data is handled.

Troubleshooting

For client developers

• Management server: Streamable HTTP, POST only (other methods get 405), stateless. Serves protocol revision 2026-07-28 (no initialize handshake) and earlier revisions back to 2025-03-26. Tools only; no resources or prompts.
• Protected resource metadata (RFC 9728): https://unifiedflows-api.onrender.com/.well-known/oauth-protected-resource/agents/mcp
• Authorization server metadata (RFC 8414): https://unifiedflows-api.onrender.com/.well-known/oauth-authorization-server
• Clients identify themselves with a Client ID Metadata Document (preferred) or Dynamic Client Registration at https://unifiedflows-api.onrender.com/oauth/register. Redirect URIs must be HTTPS, or HTTP on a loopback address.
• Authorization code with PKCE S256 (plain is refused) and refresh tokens. The resource parameter (RFC 8707) is required and must be the server URL. Public clients and client secrets are both supported; authorization responses include iss (RFC 9207). Revoke refresh tokens at https://unifiedflows-api.onrender.com/oauth/revoke.
• A 401 carries a WWW-Authenticate challenge naming the resource metadata and the product’s scopes. A client may request only the product’s own scopes; asking for none grants them all.

Need help?

If you have trouble connecting, contact us or read the FAQ.