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

# Other clients

> Connect Kualia to VS Code, Windsurf, Zed, Continue, and any MCP-compatible client

Any client that speaks the [Model Context Protocol](https://modelcontextprotocol.io) over HTTP can connect to Kualia. The server URL is always:

```
https://api.kualia.com/mcp
```

OAuth is fully automatic — clients discover the auth endpoints from the server, register dynamically, and walk you through consent in your browser.

## VS Code (GitHub Copilot Chat)

VS Code supports MCP servers in agent mode. Add Kualia to your user `settings.json`:

```json theme={null}
{
  "mcp": {
    "servers": {
      "kualia": {
        "type": "http",
        "url": "https://api.kualia.com/mcp"
      }
    }
  }
}
```

Reload VS Code, open Copilot Chat in **Agent** mode, and approve the OAuth prompt that appears.

## Windsurf

In Windsurf, open **Settings → Cascade → MCP servers → Add server** and enter the Kualia URL with HTTP transport. Or edit `~/.codeium/windsurf/mcp_config.json`:

```json theme={null}
{
  "mcpServers": {
    "kualia": {
      "serverUrl": "https://api.kualia.com/mcp"
    }
  }
}
```

## Zed

In Zed, open the assistant panel settings and add a context server. In `settings.json`:

```json theme={null}
{
  "context_servers": {
    "kualia": {
      "source": "custom",
      "url": "https://api.kualia.com/mcp"
    }
  }
}
```

## Continue

Add Kualia to your `~/.continue/config.json`:

```json theme={null}
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "http",
          "url": "https://api.kualia.com/mcp"
        }
      }
    ]
  }
}
```

## Cline / Roo Code

Open the MCP server settings panel and add a remote server with URL `https://api.kualia.com/mcp` and transport **HTTP** (or **streamable HTTP**).

## Build your own client

Kualia implements the standard MCP authorization flow:

1. Unauthenticated request to `https://api.kualia.com/mcp` returns `401` with a `WWW-Authenticate` header pointing at `/.well-known/oauth-protected-resource`.
2. That document points at the authorization server's metadata at `/.well-known/oauth-authorization-server`.
3. Clients use Dynamic Client Registration (RFC 7591) and Authorization Code + PKCE to obtain a token.
4. Tokens are sent as `Authorization: Bearer <token>` on subsequent MCP requests.

Any spec-compliant MCP client library will handle all of this for you.