---
title: Connecting via MCP
description: Wire Dike into Claude, Cursor, or any MCP-capable agent as a remote HTTP server.
order: 0
---

Dike exposes a remote **HTTP MCP server** at `https://api.dike.it.com/mcp` — there's no npm package or local process to install; agents connect to it directly over HTTP with your API key as a bearer token.

It exposes four tools: `dike_search`, `dike_reason`, `dike_cite`, `dike_graph_traverse` — direct MCP wrappers over the matching [REST endpoints](/docs/api-reference/search), so anything documented there (filters, rate limits, plan requirements) applies the same way here.

## Claude Code (CLI)

```bash
claude mcp add --transport http dike https://api.dike.it.com/mcp --header "Authorization: Bearer $DIKE_API_KEY"
```

## Claude Desktop

Add to your MCP config:

```json
{
  "mcpServers": {
    "dike": {
      "type": "http",
      "url": "https://api.dike.it.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_DIKE_API_KEY"
      }
    }
  }
}
```

## Cursor / Windsurf

Add the same block to your project's `.cursor/mcp.json` or `mcp_config.json`, keyed under whatever name you'd like the tool to show up as (`dike-legal`, etc.) — the `type`/`url`/`headers` shape is identical.

## Verifying the connection

Once connected, ask your agent a grounded legal question in Arabic or English — it should call `dike_search` or `dike_reason` and cite back a `canonical_id`. If it doesn't pick the tool up automatically, check `.claude/skills` or your client's tool-discovery docs; the server itself doesn't require any handshake beyond the bearer header.

See the full connector list on [/plugins](/plugins) for other clients (Custom GPT Actions, etc.) that connect over REST instead of MCP.