> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Other clients

> Connect any MCP-compatible client to the Paradime MCP server using the standard remote MCP protocol over HTTP with bearer-token authentication.

<Info>
  First complete [Steps 1–2 in the Overview](/products/dino-ai/mcp-server) to generate your MCP token and copy your MCP server URL.
</Info>

The Paradime MCP server speaks the standard remote MCP protocol over HTTP with bearer-token authentication. To connect any other MCP-compatible client:

* **Server URL** — copy from **Settings → API keys** in Paradime.
* **Authentication** — `Authorization: Bearer <your-mcp-token>` header.
* **Transport** — HTTP/SSE (the client must support remote MCP servers, not just local stdio).

If your client requires a JSON config, the typical shape is:

```json theme={"system"}
{
  "mcpServers": {
    "paradime": {
      "url": "<mcp-endpoint-url>",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_TOKEN"
      }
    }
  }
}
```

If you run into issues, check that your client supports remote (not just local) MCP servers — older or stdio-only clients won't work.


## Related topics

- [MCP Server](/products/dino-ai/mcp-server/index.md)
- [Bolt API](/developers/graphql-api/api-reference/bolt-api.md)
- [Microsoft Entra ID (formerly Azure AD)](/products/single-sign-on/azure-ad-sso.md)
- [Power BI](/integrations/power-bi.md)
- [Google Workspace SSO](/products/single-sign-on/google-workspace-sso.md)