Adding MCP connectors

MCP (Model Context Protocol) servers give your agent external tools. Configure them once: the same servers and OAuth tokens work in your terminal, on your cloud computer, and in workflow runs. Local and remote copies stay aligned via How it works.

Adding MCP servers locally

1. In your terminal, go to ~/.fl0w/mcp.json (or use fl0w mcp add from the CLI reference).
2. Add the server to the json config. After editing, run fl0w reauth for OAuth servers, or enable them per session with /configure.

For OAuth Servers

// MCP server using HTTP or SSE - runs on a server
{
  "mcpServers": {
    "server-name": {
      "url": "http://localhost:3000/mcp",
      "headers": {
        "API_KEY": "value"
      }
    }
  }
}

For static OAuth

{
  "mcpServers": {
    "oauth-server": {
      "url": "https://api.example.com/mcp",
      "auth": {
        "CLIENT_ID": "your-oauth-client-id",
        "CLIENT_SECRET": "your-client-secret",
        "scopes": ["read", "write"],
        "callbackPort": 3118
      }
    }
  }
}

Adding MCP servers remotely

Add any remote MCP directly in the MCP tab of your remote computer fl0w (open the app via Quickstart — Starting fl0w remotely).

Changes on either side sync automatically; you can also run fl0w sync after manual edits. MCP tools are available in interactive sessions and in unattended fl0w workflow runs when saved on the workflow.