Skip to Content
MCP Server (Preview)Connect Other Clients

Connect Other Clients

Dialora is a plain streamable-HTTP MCP server with bearer auth, so any MCP client can reach it. Most of them take the exact same JSON.

The config

Drop this into your client’s MCP config file:

{
  "mcpServers": {
    "dialora": {
      "url": "https://api.dialora.ai/mcp",
      "headers": {
        "Authorization": "Bearer dlr_live_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

That is the whole integration — one URL and one header. Everything else on this page is just where each client keeps that file, and the handful of clients that spell the same fields differently.

Where the config file lives

ClientConfig fileShape
Cursor~/.cursor/mcp.json, or .cursor/mcp.json per projectConfig above — see Connect Cursor
VS Code (GitHub Copilot agent mode).vscode/mcp.json per workspace, or MCP: Open User Configurationservers variant below
Windsurf~/.codeium/windsurf/mcp_config.jsonserverUrl variant below
Cline (VS Code extension)cline_mcp_settings.json — open via the extension’s MCP Servers → ConfigurestreamableHttp variant below
LM Studiomcp.json, via Program → Install → Edit mcp.jsonConfig above
WarpAdded through Settings → AI → MCP ServersConfig above
Continue~/.continue/config.yamlmcpServers block, YAML
Zedsettings.json → context_serversZed-specific key
Claude DesktopNeeds the stdio bridgeSee Connect Claude
Claude CodeOne CLI commandSee Connect Claude

MCP clients move fast and config formats drift between releases. If a client below rejects the block, check its own MCP docs for the current field names — the values never change: URL https://api.dialora.ai/mcp, header Authorization: Bearer dlr_live_xxxxxxxxxxxxxxxx.

Clients that spell it differently

VS Code uses a top-level servers key instead of mcpServers, and wants the transport named:

{
  "servers": {
    "dialora": {
      "type": "http",
      "url": "https://api.dialora.ai/mcp",
      "headers": {
        "Authorization": "Bearer dlr_live_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

Put this in .vscode/mcp.json to scope it to one workspace, or run MCP: Open User Configuration from the command palette to make it global. Dialora tools then show up in Copilot agent mode under the tools picker.

Client can’t do remote HTTP servers

Some clients — Claude Desktop among them — only launch local stdio servers. Those reach Dialora through mcp-remote, a bridge that speaks stdio to the client and HTTPS to Dialora. It needs Node 18+:

{
  "mcpServers": {
    "dialora": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.dialora.ai/mcp",
        "--transport", "http-only",
        "--header", "Authorization:${DIALORA_AUTH}"
      ],
      "env": {
        "DIALORA_AUTH": "Bearer dlr_live_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

Note "Authorization:${DIALORA_AUTH}" has no space after the colon, with the Bearer prefix in the env block. Several clients split arguments on spaces, which corrupts the header and produces a confusing 401. mcp-remote expands ${DIALORA_AUTH} itself, so the space survives.

If the bridge fails to start with spawn npx ENOENT, the client can’t find npx — the fix (an explicit PATH, and cmd /c on Windows) is covered in Connect Claude.

Rolling your own client

If you’re building against MCP directly, the server is a standard streamable-HTTP endpoint:

URLhttps://api.dialora.ai/mcp
TransportStreamable HTTP (no SSE endpoint)
AuthAuthorization: Bearer dlr_live_… on every request
SessionStateless — no session id to carry between requests

Tools are registered per key, so the tools/list response reflects your key’s scopes. Mind the rate limits: one tool call per 15 seconds, 20 requests per 5 seconds.

Verify

Whatever the client, ask it:

“Using Dialora, list my 5 most recent calls.”

If the tools don’t appear, work through Troubleshooting.

Connect CursorTools Reference