Claude Desktop

Claude Desktop starts its MCP servers from a config file on your computer. Unitley runs on Unitley's servers, so the config starts a small bridge, mcp-remote, that connects to Unitley over the internet and passes your access token along.

Before you startCopy Anchor Link

• Node.js 20.18.1 or later (the current LTS is fine). Claude Desktop runs the bridge with npx, which comes with Node.js. Run node --version in a terminal to check. If it is missing, install the LTS version from nodejs.org (opens in a new tab).
• An access token from the Connect page. Tick Let it log bets, settle them and save picks only if you want Claude to use log_bet, settle_bet and save_recommendation. Unitley shows the token only once, and the Connect page fills it into the config for you while the page is open.

Set it upCopy Anchor Link

1. Open the config fileCopy Anchor Link

   Open the Claude menu in your system's menu bar (not the settings inside the Claude window) and choose Settings…. Open the Developer tab and click Edit Config. This creates claude_desktop_config.json if it does not exist yet, or opens the one you have.

   macOSWindows

   ~/Library/Application Support/Claude/claude_desktop_config.json

2. Add UnitleyCopy Anchor Link

   Add this to the file, with your token in place of the placeholder:

   Copy Text

   {
     "mcpServers": {
       "unitley": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://console.unitley.com/api/mcp",
           "--header",
           "Authorization:${AUTH_HEADER}"
         ],
         "env": {
           "AUTH_HEADER": "Bearer YOUR_UNITLEY_TOKEN"
         }
       }
     }
   }

   If the file already has an mcpServers section, add only the unitley entry inside it, next to your other servers, with a comma between entries. Do not paste a second mcpServers section. A JSON mistake can stop Claude Desktop loading any of your servers.

3. Restart Claude DesktopCopy Anchor Link

   Quit Claude Desktop completely, not just its window, and open it again. It reads the config file only when it starts.

   The first start can take a little longer while npx downloads mcp-remote.

4. Check that it loadedCopy Anchor Link

   Click the Add files, connectors, and more button at the bottom left of the message box, point to Connectors and click Manage connectors. Select unitley to see its tools. Then try a question such as: Using Unitley, what is the implied probability of −110?

Why the token goes in envCopy Anchor Link

The config passes the header to mcp-remote as Authorization:${AUTH_HEADER} and puts the real value, Bearer and your token, in the env section. mcp-remote fills in ${AUTH_HEADER} when it starts.

The reason is the space in Bearer unt_…. On some systems, Claude Desktop on Windows among them, a space inside an argument is not escaped, so the header would be split in two and Unitley would never see the token. A value in env keeps its space.

Keep the token in the env section and treat the config file like a password: anyone who can read it can use Unitley as you until you revoke the token.

If it does not loadCopy Anchor Link

Claude Desktop writes a log for each MCP server:

The usual causes are Node.js missing, a JSON mistake in the config, or a token that was revoked or expired. See Troubleshooting.

Replace the tokenCopy Anchor Link

1. Create a new token on the Connect page.
2. Put it in place of the old one in AUTH_HEADER, keeping the Bearer in front.
3. Save the file and restart Claude Desktop.
4. Revoke the old token on the Connect page.

Remove itCopy Anchor Link

Delete the unitley entry from mcpServers, save the file, and restart Claude Desktop. Then revoke its token on the Connect page, since removing the entry does not revoke it.

Learn moreCopy Anchor Link

• Tokens and security covers scopes, expiry and revoking.
• Connect to local MCP servers (opens in a new tab) is the MCP project's guide to Claude Desktop's config file and logs.
• mcp-remote (opens in a new tab) documents the bridge and its options.