Skip to main content

Flow MCP

Connect AI agents to Rynko Flow via the Model Context Protocol (MCP). Each active gate automatically generates a dedicated validate_{slug} tool that agents can call to validate their outputs before passing them to downstream systems.

Server URL: https://api.rynko.dev/api/flow/mcp

Authentication: Workspace-scoped API Key

How It Works​

  1. Your AI agent connects to the Flow MCP server
  2. Flow discovers all active gates in the workspace and registers a validate_{slug} tool for each
  3. The agent sees each tool's full schema (field types, constraints) and business rule descriptions
  4. When the agent has data to validate, it calls the appropriate tool
  5. Flow validates the payload and returns the result, including a tamper-proof validation_id

When gates are created, updated, or deleted, the MCP server pushes a notifications/tools/list_changed event so connected agents automatically see the updated tool list — no reconnection needed.

Dynamic Gate Tools​

For each active gate, Flow generates a tool named validate_{gate_slug} (hyphens replaced with underscores).

Example: A gate with slug payment-review produces a tool called validate_payment_review.

Tool Properties​

  • Input schema is dynamically generated from the gate's current schema — each variable becomes a typed JSON Schema property with its constraints
  • Description includes the gate description and all enabled business rule error messages, so the agent understands constraints before submitting
  • Marked as destructive — calling the tool creates a run and consumes quota

Example: Agent Conversation​

User: Please validate this order before submitting it.

Agent: I'll validate this against your Order Validation gate.

[Agent calls validate_order_validation with:
  {
    "orderId": "ORD-2026-042",
    "amount": 1250.00,
    "currency": "USD",
    "customerEmail": "buyer@example.com"
  }
]

Agent: The order passed validation. Here are the results:
- Schema validation: pass
- Business rules: pass
- Validation ID: v_abc123...

You can use the validation ID to confirm this data hasn't been
modified when it reaches your downstream system.

Freetext Mode​

For gates in freetext mode (or gates without a schema), the tool accepts a single content string parameter instead of individual typed fields.

Static Tools​

In addition to the dynamic gate tools, Flow provides these static tools:

ToolDescriptionParameters
list_flow_gatesList all active gates in the workspaceNone
get_flow_gateGet gate details: schema, approval config, delivery configgate_id
get_flow_run_statusCheck the status of a submitted runrun_id
list_flow_runsList recent runs with optional filteringgate_id (opt), limit (default 10), status (opt)
verify_validationVerify a payload against a validation_id for tamper detectionvalidation_id, payload

All static tools are read-only except verify_validation, which performs a comparison check.

Setup​

Step 1: Create a Workspace-Scoped API Key​

  1. Log in to the Rynko Dashboard
  2. Switch to the workspace whose gates you want to expose
  3. Go to Settings → API Keys
  4. Click Create New API Key
  5. Copy the key (starts with fm_)
warning

The API key must be workspace-scoped. A team-level key without a workspace will be rejected with an error explaining what's needed.

Step 2: Configure Your AI Tool​

Via Connectors (OAuth — Recommended)​

  1. Open Claude Desktop → Settings → Connectors
  2. Click Add Custom Connector
  3. Paste the server URL: 
    https://api.rynko.dev/api/flow/mcp
  4. OAuth authorization completes automatically — sign in with your Rynko account when prompted
info

Connectors with OAuth require a Claude Pro, Max, Team, or Enterprise plan.

Via mcp-remote Proxy (API Key)​

Claude Desktop does not support custom headers for HTTP transport. Use the mcp-remote proxy to bridge the remote server to stdio:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rynko-flow": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.rynko.dev/api/flow/mcp",
        "--header",
        "Authorization:${RYNKO_FLOW_KEY}"
      ],
      "env": {
        "RYNKO_FLOW_KEY": "Bearer fm_your_api_key"
      }
    }
  }
}

Replace fm_your_api_key with your actual API key, then restart your AI tool. You should see the Flow tools (e.g., list_flow_gates, validate_order_validation) appear in your available tools.

Step 3: Verify Connection​

Ask your AI tool:

  • "List my Flow gates"
  • "What validation gates do I have access to?"

MCP Transport​

The Flow MCP server uses Streamable HTTP transport (JSON-RPC 2.0 over HTTP with optional SSE):

MethodPathDescription
POST/api/flow/mcpCreate session or route JSON-RPC to existing session
GET/api/flow/mcpSSE stream for server-initiated notifications
DELETE/api/flow/mcpTerminate session

Sessions are identified by the Mcp-Session-Id header and auto-expire after 30 minutes of inactivity.

Rate Limits​

The MCP endpoint is rate-limited to 100 requests per minute per API key. This is separate from per-gate rate limits configured on individual gates.

Related: Render MCP | Flow Gates | Flow Runs