Other MCP clients

Any client that speaks the Model Context Protocol over Streamable HTTP can connect. You need one value:

Endpoint	https://api.integrator.io/celigo-mcp (US). For another region, see Pick your endpoint.

Most clients use the same shape: a server name and the URL.

{
  "mcpServers": {
    "celigo": {
      "url": "https://api.integrator.io/celigo-mcp"
    }
  }
}

If the client implements the MCP authorization spec (OAuth 2.1 with PKCE), it discovers the Celigo authorization server from the endpoint and opens a browser — sign in with your Celigo credentials and pick the account and environment the agent should work in.

Clients without OAuth support

Authenticate with a bearer token in the Authorization header instead. Both API tokens and personal access tokens work; keep any config file that holds a token out of version control.

{
  "mcpServers": {
    "celigo": {
      "url": "https://api.integrator.io/celigo-mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_TOKEN>"
      }
    }
  }
}

Clients without Streamable HTTP

If your client only supports the older HTTP+SSE transport, bridge to it with mcp-remote, which exposes the hosted endpoint as a local server. Run it with no header to start the OAuth sign-in in your browser, or attach a token with --header:

npx -y mcp-remote https://api.integrator.io/celigo-mcp

npx -y mcp-remote https://api.integrator.io/celigo-mcp \
  --header "Authorization: Bearer <YOUR_API_TOKEN>"

Verify

Once connected, ask the agent to "list my connections." It should discover and call list_connections and report a summary of your account.