Connect any MCP client to the Paradime MCP server - Paradime

First copy your MCP server URL from Step 1 in the Overview.

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

Server URL: copy from Settings → MCP Access in Paradime.
Authentication: OAuth by default. Add the server with just its URL, and the client walks you through a browser sign-in and consent screen.
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:

{
  "mcpServers": {
    "paradime": {
      "url": "<mcp-endpoint-url>"
    }
  }
}

Connected with a legacy token?

New tokens can’t be generated anymore, so clients that can’t complete a browser sign-in need an existing legacy token sent as a bearer header:

{
  "mcpServers": {
    "paradime": {
      "url": "<mcp-endpoint-url>",
      "headers": {
        "Authorization": "Bearer YOUR_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.