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

# Connecting a client

> Configure Claude, Cursor, and other MCP clients to use the Noxus MCP server

The Noxus MCP server is a remote **streamable-HTTP** endpoint at `https://backend.noxus.ai/mcp`, authenticated with your Noxus API key as a bearer token. Below are configs for the common clients. Replace `YOUR_NOXUS_API_KEY` with a key from **Settings → Organization → Workspaces → API Keys**.

<Warning>
  Your API key grants access to its workspace. Treat it like a password — prefer
  an environment variable over hardcoding it, and use a key scoped to only the
  permissions the client needs.
</Warning>

<Tabs>
  <Tab title="Claude Code">
    Add the server with the CLI (HTTP transport + an Authorization header):

    ```bash theme={null}
    claude mcp add --transport http noxus https://backend.noxus.ai/mcp \
      --header "Authorization: Bearer YOUR_NOXUS_API_KEY"
    ```

    Then in a session, the Noxus tools are available to the model. Manage it with `claude mcp list` / `claude mcp remove noxus`.
  </Tab>

  <Tab title="Claude Desktop">
    Claude Desktop can add remote MCP servers as **custom connectors**: **Settings → Connectors → Add custom connector**, then enter the URL `https://backend.noxus.ai/mcp`. When prompted for authentication, supply your API key as the bearer token.

    If your version needs a config-file entry instead, bridge the remote server with `mcp-remote` in `claude_desktop_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "noxus": {
          "command": "npx",
          "args": [
            "-y", "mcp-remote", "https://backend.noxus.ai/mcp",
            "--header", "Authorization: Bearer YOUR_NOXUS_API_KEY"
          ]
        }
      }
    }
    ```

    Restart Claude Desktop after editing the file.
  </Tab>

  <Tab title="Cursor">
    Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):

    ```json theme={null}
    {
      "mcpServers": {
        "noxus": {
          "url": "https://backend.noxus.ai/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_NOXUS_API_KEY"
          }
        }
      }
    }
    ```

    Enable it under **Cursor Settings → MCP**.
  </Tab>

  <Tab title="Any MCP client">
    Any client that supports the **streamable-HTTP** transport can connect. Provide:

    * **URL**: `https://backend.noxus.ai/mcp`
    * **Header**: `Authorization: Bearer YOUR_NOXUS_API_KEY`

    The server advertises its tools on connect (`tools/list`); no per-tool setup is needed.
  </Tab>
</Tabs>

## Self-hosted deployments

On-prem / self-hosted Noxus serves the same MCP server at your backend host:

```
https://<your-backend-host>/mcp
```

Use that URL in any of the configs above.

## Verify the connection

Once connected, ask the model to list something read-only, e.g. *"list my Noxus workflows"* or *"what knowledge bases do I have?"* — it should call `workflows_list` / `knowledge_bases_list` and return your workspace's resources. If calls fail with an auth error, re-check the bearer token; if a specific tool is refused, the key likely lacks that permission (see [Available tools](/sdk/mcp/tools#permissions)).