# Connect Claude Desktop to FreshlyCited MCP

There are two ways to use FreshlyCited in Claude Desktop: as a custom connector with OAuth (no key to manage), or as a local bridge with an API key.

## Recommended: add a custom connector

Claude Desktop shares connectors with Claude.ai. In Claude Desktop open **Settings › Connectors**, choose **Add custom connector**, name it FreshlyCited and paste:

```text
https://freshlycited.com/mcp
```

Click **Connect**. The FreshlyCited consent screen opens: sign in, pick the workspace and access level, and allow. Full steps and plan notes: [Claude.ai connector](https://freshlycited.com/docs/clients/claude-ai).

## Alternative: claude_desktop_config.json with an API key

`claude_desktop_config.json` only runs local servers, so a remote server goes through the `mcp-remote` bridge (needs Node.js). Open **Settings › Developer › Edit Config** and add:

```json
{
  "mcpServers": {
    "freshlycited": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://freshlycited.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer ipk_YOUR_KEY"
      }
    }
  }
}
```

Keep `Authorization:${AUTH_HEADER}` exactly as written, without spaces around the colon: the key itself lives in `env`. Restart Claude Desktop afterwards.

API keys are created under **API keys** in the FreshlyCited app and shown once. A key only sees its own workspace and the clients under it, with the key's role.

## Check it works

Ask: *"Call FreshlyCited's get_started tool."* You should see your workspace, role and credit balance. If the client says it can't connect, see [Authentication](https://freshlycited.com/docs/authentication) for what each error means.

---
Source: https://freshlycited.com/docs/clients/claude-desktop