# Other clients

DNS Super works with any MCP client that supports remote servers over Streamable HTTP. You need two things:
the server address, `https://mcp.dnssuper.com/mcp`, and your API key in an `Authorization: Bearer` header.

## Clients with remote server support

Most clients accept this shape in their config file:

Any client that speaks Streamable HTTP: the server URL plus an Authorization header.

```json
{
  "mcpServers": {
    "dnssuper": {
      "type": "http",
      "url": "https://mcp.dnssuper.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

Some clients name the fields differently (`serverUrl` instead of `url`, or no `type`); the address and the
header stay the same.

## Clients that only start local servers

If a client can only start servers as local commands, run the stdio bridge as the command. It needs
Node.js:

Run the stdio bridge as the server command, with your key in the environment:

```sh
npx -y mcp-remote https://mcp.dnssuper.com/mcp --header "Authorization: Bearer $DNSSUPER_API_KEY"
```

## Calling the server directly

The server is plain MCP over HTTP, so you can also call it from your own code with an MCP SDK. Each tool
takes the same parameters as its REST endpoint; see the [tool reference](/docs/tools). If you don't need
MCP, the [REST API](/docs/quickstart) gives you the same checks with plain HTTP.
