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

# Client configuration

> Connect Claude Desktop, Cursor, or any MCP client to the HypeDexer MCP server.

The server is hosted, so there is nothing to install: point your client at the endpoint and add your API key as a bearer token.

|               |                                      |
| ------------- | ------------------------------------ |
| **Endpoint**  | `https://mcp.hypedexer.com/mcp`      |
| **Transport** | Streamable HTTP, stateless           |
| **Header**    | `Authorization: Bearer YOUR_API_KEY` |

## Claude Desktop / Cursor

Both clients accept remote MCP servers declared under `mcpServers`. Add HypeDexer to your client's MCP configuration and restart it:

```json theme={null}
{
  "mcpServers": {
    "hypedexer": {
      "url": "https://mcp.hypedexer.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}
```

The 78 tools are then listed by the client and available to the agent.

## Any MCP client

Any client that speaks streamable HTTP works with the same two ingredients — the URL and the `Authorization` header:

<CodeGroup>
  ```bash List tools theme={null}

  curl -X 'POST' \
    'https://mcp.hypedexer.com/mcp' \
    -H 'Authorization: Bearer YOUR_API_KEY' \
    -H 'Content-Type: application/json' \
    -H 'Accept: application/json, text/event-stream' \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

  ```
</CodeGroup>

<Note>
  The server is stateless and implements MCP protocol `2026-07-28`. 2025-era clients are served through the SDK's legacy fallback, so an older client needs no special configuration.
</Note>

## Local stdio alternative

If you would rather not send your key to a hosted endpoint, run the server locally over stdio instead. It is published on npm and needs no clone or build:

<CodeGroup>
  ```bash Run locally theme={null}

  HYPEDEXER_API_KEY=YOUR_API_KEY npx @hypedexer/mcp-server

  ```
</CodeGroup>

Declared in a client configuration, the same server looks like this:

```json theme={null}
{
  "mcpServers": {
    "hypedexer": {
      "command": "npx",
      "args": ["@hypedexer/mcp-server"],
      "env": { "HYPEDEXER_API_KEY": "YOUR_API_KEY" }
    }
  }
}
```

<Warning>
  The stdio package only works with **regular Data API keys**. A key restricted to the hosted MCP server (see [403 `mcp_only_key`](/mcp/errors)) will not work locally.
</Warning>

## Next

<CardGroup cols={2}>
  <Card title="Tool catalog" icon="wrench" href="/mcp/tools">
    The 78 read-only tools, grouped by domain.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/mcp/errors">
    401, 402, 403 and 429 — and how to recover.
  </Card>
</CardGroup>