> For the complete documentation index, see [llms.txt](https://developer.celigo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.celigo.com/mcp/connect/other-clients.md).

# 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](/mcp/connect.md#pick-your-endpoint). |

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

```json
{
  "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.

```json
{
  "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`](https://www.npmjs.com/package/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`:

```bash
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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.celigo.com/mcp/connect/other-clients.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.