MCP server

Flow Relay speaks the Model Context Protocol in two ways, exposing the same 40 tools, 3 prompts and 1 resource template over the same REST API:

• Remote server at https://www.flowrelay.it/mcp (Streamable HTTP) – nothing to install, works from any MCP client that supports remote servers.
• Local server via the @flowrelay/mcp-server npm package – a thin stdio client installed on demand via npx, for clients that only speak stdio.

The endpoint is https://www.flowrelay.it/mcp. Authenticate with your fr_ API key as a bearer token, or through the built-in OAuth flow if your client supports it. Setup differs per client – pick yours below.

Claude Desktop and claude.ai (custom connector)

No manual header and no OAuth credentials needed. In Settings > Connectors > Add custom connector:

1. Name: Flow Relay.
2. URL: https://www.flowrelay.it/mcp.
3. Leave the advanced OAuth Client ID and Client Secret fields empty – Flow Relay handles client registration automatically.
4. Click Add, then Connect: the Flow Relay authorize page opens in your browser and you paste one of your API keys once to grant access.

The connection carries exactly the permissions of that key and stops working the moment you revoke the key in Settings > API Keys.

Claude Code

claude mcp add --transport http flowrelay https://www.flowrelay.it/mcp \
  --header "Authorization: Bearer fr_your_api_key_here"

Cursor, Windsurf and other JSON-config clients

Any client that takes a JSON config with remote servers:

{
  "mcpServers": {
    "flowrelay": {
      "url": "https://www.flowrelay.it/mcp",
      "headers": {
        "Authorization": "Bearer fr_your_api_key_here"
      }
    }
  }
}

Stdio-only clients

Bridge with mcp-remote:

{
  "mcpServers": {
    "flowrelay": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://www.flowrelay.it/mcp",
        "--header", "Authorization: Bearer fr_your_api_key_here"
      ]
    }
  }
}

Picking a project

The connection itself is project-agnostic: one key sees every project it has access to. The model picks a project in conversation – list_projects then set_active_project – or passes project_id explicitly to any tool. The remote server keeps the active project per API key for 30 days, so it survives across sessions and devices using the same key.

The @flowrelay/mcp-server package runs locally over stdio. No repository access is required; the server is installed on demand via npx.

Setup

1. Install Node.js (v22 or later).
2. Create an API key in Settings > API Keys.
3. Add the server to your Claude config file:

{
  "mcpServers": {
    "flowrelay": {
      "command": "npx",
      "args": ["-y", "@flowrelay/mcp-server"],
      "env": {
        "FLOWRELAY_API_KEY": "fr_your_api_key_here",
        "FLOWRELAY_PROJECT_ID": "your_project_id"
      }
    }
  }
}

Environment variables

Both servers expose the same 40 tools:

The work item tools, resolve_suggestion, create_raid_entry, delete_work_item, decide_approval, list_raid, get_earned_value, get_portfolio, get_forecast, list_automations, list_templates, apply_template, list_approvals and request_change cost no credits; work item tools use wall-clock dates in the plan time zone. See Work management and Evidence linking.

Both servers also offer three prompts that start the usual flows and one resource template:

The generate_* tools and list_filter_options accept per-source filters (projects / eventTypes / branches / priorities), so the model works with real selectable values rather than guessing. See Filters.

The package is published on npm under the AGPL-3.0-or-later license.