# Connect a client

The PROlinks MCP server uses the Streamable HTTP transport. It authenticates every request with a bearer token in the `Authorization` header. In the examples below, replace `YOUR_API_TOKEN` with the token from **Settings > API Tokens**.

> **Warning:** Do not commit a configuration file that contains your token to a public repository.

## Claude Code

Run this command in your terminal:

```bash
claude mcp add --transport http prolinks https://prolinks.pro/mcp/prolinks \
  --header "Authorization: Bearer YOUR_API_TOKEN"
```

To make the server available in all your projects, add `--scope user`. Run `claude mcp list` to check the connection.

## Claude Desktop

Claude Desktop connects to a remote server with a custom header through the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) package. You need Node.js on your computer.

1. Open **Settings > Developer** in Claude Desktop.
2. Click **Edit Config**.
3. Add the `prolinks` server to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "prolinks": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://prolinks.pro/mcp/prolinks",
        "--header",
        "Authorization:${PROLINKS_AUTH}"
      ],
      "env": {
        "PROLINKS_AUTH": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
```

4. Restart Claude Desktop.

The header has no space after the colon. Some systems split the argument at the space, so the token goes in the `env` value instead.

## Cursor

Add the server to `~/.cursor/mcp.json` for all projects, or to `.cursor/mcp.json` for one project:

```json
{
  "mcpServers": {
    "prolinks": {
      "url": "https://prolinks.pro/mcp/prolinks",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
```

## VS Code

Add the server to `.vscode/mcp.json` in your workspace:

```json
{
  "servers": {
    "prolinks": {
      "type": "http",
      "url": "https://prolinks.pro/mcp/prolinks",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
```

## Other clients

Any client that supports remote MCP servers with custom headers can connect. Use these values:

| Setting | Value |
| --- | --- |
| Transport | Streamable HTTP |
| URL | `https://prolinks.pro/mcp/prolinks` |
| Header | `Authorization: Bearer YOUR_API_TOKEN` |

Some clients connect to remote servers only with OAuth. The PROlinks MCP server does not support OAuth at this time, so these clients cannot connect directly.

## Check the connection

Ask your assistant to "list my PROlinks organizations". If the connection is correct, the assistant shows your organizations. If the client shows a `401` error, the token is missing, incorrect or deleted. Read [Limits and errors](/docs/mcp/limits-and-errors) for the other errors.