Skip to content

CLIENT_CONFIG.md

Latest commit

 

History

History
63 lines (45 loc) · 1.71 KB

CLIENT_CONFIG.md

File metadata and controls

63 lines (45 loc) · 1.71 KB
Raw

🔐 Client Configuration

CodeBuddy / Claude Desktop (HTTP mode)

Add to your MCP client config:

{
  "mcpServers": {
    "dolphinscheduler": {
      "type": "sse",
      "url": "http://localhost:8001/mcp/",
      "headers": {
        "X-DS-Token": "your_api_token"
      }
    }
  }
}

⚠️ The URL must end with /. Without the trailing slash, Starlette returns a 307 redirect, which some MCP clients fail to follow.

Protocol compatibility

The HTTP endpoint supports both protocol eras:

  • MCP 2.0 clients use the stateless 2026-07-28 protocol. Every request is independently routable and no Mcp-Session-Id header is issued.
  • MCP 1.x clients continue to use the initialize handshake, but the server handles each request statelessly for load-balancer compatibility.

No client URL changes are required: the endpoint remains /mcp/. Stdio clients are unchanged.

Example Configurations

More examples in the examples/ directory:

  • codebuddy-config.json — CodeBuddy configuration
  • claude-desktop-config.json — Claude Desktop stdio mode
  • http-auth-token.json — HTTP with token auth
  • http-auth-password.json — HTTP with username/password

Multi-Tenant Per-Request Auth

In HTTP mode, each caller can pass their own credentials:

Token mode (preferred):

X-DS-Token: your_api_token

Username/password mode:

X-DS-User: alice
X-DS-Password: alice_password

This enables multi-tenant scenarios where different AI agents or users operate with different DolphinScheduler credentials through the same MCP server instance.

← Back to README | Configuration | Deployment | API Reference