This step-by-step guide describes the configurations to connect Claude Desktop to the BlueDolphin MCP server. This is a one-time setup. After that, Claude will always start with the BlueDolphin tools available.

Prerequisites:

Before you start, make sure you have:

a. Your BlueDolphin MCP API token

You need your BlueDolphin MCP API key to connect BlueDolphin MCP with Claude. For more details on how to retrieve your BlueDolphin MCP API, refer to the Add BlueDolphin MCP Server to an AI Assistant article.

b. Claude Desktop

Download the Claude Desktop app and sign in with your account.

c. Node.js LTS (Long-Term Support)

Node.js is remotely connected to MCP server.
Install Node.js 20.18.1 LTS or newer.
After installation, open Terminal (macOS) or PowerShell (Windows) and check: node --version

The command should print a version number (no errors).

d. The mcp-remote npm package installed

Open Terminal (macOS) or PowerShell (Windows).
Run: npm install -g mcp-remote

Step 1: Open Claude’s configuration file

Claude Desktop stores MCP settings in a file called claude_desktop_config.json. You don’t need to find it manually; Claude will open it for you.

Open Claude Desktop.
Click your profile picture/initials in the bottom-left.
Choose Settings.
In the left-hand menu, click Developer.
Click Edit Config.

This opens claude_desktop_config.json in your default text editor.

💡 If the file is empty or almost empty, we’ll paste in the BlueDolphin configuration.

Step 2: Add the BlueDolphin MCP configuration

Below is the configuration template for BlueDolphin. The example below uses the EU MCP server, but if your tenant is in the US, replace the URL with the corresponding one.

If the file is empty (or you’re not using other MCP servers), replace everything in it with this exact content:

{
  "mcpServers": {
    "BlueDolphin": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://bd-mcpserver-api.eu.bluedolphin.app/mcp",
        "--header",
        "Authorization:${API_TOKEN}"
      ],
      "env": {
        "API_TOKEN": "Bearer YOUR-API-TOKEN"
      }
    }
  }
}

Then go to Step 3: Insert your API token below.

If the file already has an mcpServers section, or if you see something like this:

{
  "mcpServers": {
    "SomeOtherServer": {
      "command": "npx",
      "args": [
        "something-here"
      ]
    }
  }
}

You need to add the BlueDolphin block inside "mcpServers", without removing the existing ones.

Example with two servers configured:

{
  "mcpServers": {
    "SomeOtherServer": {
      "command": "npx",
      "args": [
        "something-here"
      ]
    },
    "BlueDolphin": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://bd-mcpserver-api.eu.bluedolphin.app/mcp",
        "--header",
        "Authorization:${API_TOKEN}"
      ],
      "env": {
        "API_TOKEN": "Bearer YOUR-API-TOKEN"
      }
    }
  }
}

NOTE: Be careful with commas:

There must be a comma between entries (SomeOtherServer and BlueDolphin).
There must not be a comma after the last entry inside "mcpServers".

Step 3: Insert your API token

Replace YOUR-API-TOKEN (inside the quotes) with the token from within BlueDolphin, for example:

"env": {
  "API_TOKEN": "Bearer bdmcp_123456789_very-long-token"
}

NOTE:

Keep the quotes around the token and keep the Bearer prefix.
Don’t change the word API_TOKEN – only the value on the right.
Do not remove the space between Bearer and the token.
Do not add spaces before or after the token.
Do not share screenshots or recordings that show your token.

Step 4: Save and restart Claude Desktop

Save the claude_desktop_config.json file in your editor.
Fully quit Claude Desktop:
- Windows: Right-click the Claude icon in the system tray → Quit.
- macOS: Right-click the Claude icon in the dock → Quit, or use ⌘+Q.
Open Claude Desktop again.

Step 5: Verify that BlueDolphin is connected

Open any chat in Claude Desktop.
Look to the bottom-left corner of the chat box for the + icon.
Click the + button. You should see BlueDolphin listed as an MCP server. Make sure it’s enabled (the toggle is on or the status shows as running).

To test it, you can ask:

“Use the BlueDolphin tools to confirm that the BlueDolphin MCP server is connected.”

If you encounter tool failure, try toggling OFF the “Thinking” feature on Claude (accessed by clicking on the Claude model; a drop-down menu will appear. Click on Effort, where you can find Thinking)

Troubleshooting with BlueDolphin MCP and Claude

Claude shows no tools / BlueDolphin doesn’t appear

Double-check that you:
- Saved claude_desktop_config.json.
- Restarted Claude Desktop.
If the file has other MCP servers, check commas and quotes.

You see an error about `npx` or `node` not found

This usually means Node.js isn’t installed correctly or your terminal/editor was open before installation and needs a restart.

Confirm in a new Terminal / PowerShell window:
node --version npx --version
If you get an error, reinstall Node.js (LTS version)

You see errors about `mcp-remote` not found

Run:
npm install -g mcp-remote
Then restart Claude Desktop and try again.

BlueDolphin tools appear, but calls fail (authorization issues)

If Claude can see BlueDolphin, but tool calls fail with messages about authorization:

Check that your API token is correctly pasted in the config (no extra spaces, no missing characters).
Confirm that your token is still valid (if in doubt, you can regenerate the API token).

Configure SCIM user provisioning for BlueDolphin using Okta

Power BI for BlueDolphin Quickstart

Add BlueDolphin MCP Server to an AI Assistant

Microsoft Copilot to BlueDolphin with MCP

Claude to BlueDolphin with MCP