Connect Other Clients

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

It supports both credential styles: OAuth sign-in for clients that speak it (they discover Dialora’s authorization server from the URL alone and register themselves), and a bearer API key for everything else. The configs below use an API key, which works everywhere.

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

Client	Config file	Shape
Cursor	`~/.cursor/mcp.json`, or `.cursor/mcp.json` per project	Config above — see Connect Cursor
VS Code (GitHub Copilot agent mode)	`.vscode/mcp.json` per workspace, or MCP: Open User Configuration	`servers` variant below
Windsurf	`~/.codeium/windsurf/mcp_config.json`	`serverUrl` variant below
Cline (VS Code extension)	`cline_mcp_settings.json` — open via the extension’s MCP Servers → Configure	`streamableHttp` variant below
LM Studio	`mcp.json`, via Program → Install → Edit mcp.json	Config above
Warp	Added through Settings → AI → MCP Servers	Config above
Continue	`~/.continue/config.yaml`	`mcpServers` block, YAML
Zed	`settings.json` → `context_servers`	Zed-specific key
Claude Desktop	Needs the stdio bridge	See Connect Claude
Claude Code	One CLI command	See 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

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.

Windsurf

Windsurf marks a remote server with serverUrl rather than url:


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

Edit ~/.codeium/windsurf/mcp_config.json, then hit Refresh in the Cascade MCP panel.

Cline

Cline wants the transport named explicitly:


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

Open it from the Cline sidebar → MCP Servers → Configure MCP Servers.

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:


URL	`https://api.dialora.ai/mcp`
Transport	Streamable HTTP (no SSE endpoint)
Auth	`Authorization: Bearer dlr_live_…` on every request
Session	Stateless — 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.