# Install in your client

Open the MCP panel from the account menu (or go to [exayard.com/?mcp=1](https://exayard.com/?mcp=1)) for ready-to-copy install blocks for each client. What follows is the raw shape for reference.

## Cursor (deep link)

Clicking this link installs the server in Cursor:

```
cursor://anysphere.cursor-deeplink/mcp/install?name=exayard&config=%7B%22url%22%3A%22https%3A%2F%2Fapi.exayard.com%2Fmcp%22%2C%22transport%22%3A%22streamable-http%22%7D
```

Paste this into your address bar or wire it up as a button. Cursor prompts for auth on first use.

## Claude Desktop / Claude Code

Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS):

```json
{
  "mcpServers": {
    "exayard": {
      "url": "https://api.exayard.com/mcp",
      "env": { "EXAYARD_API_KEY": "<your-api-key>" }
    }
  }
}
```

## Generic MCP clients (Codex, Continue, Goose, Windsurf)

Most accept the same shape as Claude Desktop. See your client's MCP section for the exact JSON location.

## OAuth vs API key

For long-lived human sessions use OAuth (and let the client run the DCR flow). For CI or server-to-server, use an `exa_live_...` key made on the Developer page. It is faster to set up, but
replace it regularly. A key set to work in **This company** acts in its own company, so no company needs naming. See
[Apps and keys](https://developers.exayard.com/apps-and-keys.md).