> For the complete documentation index, see [llms.txt](https://mcp-docs.nichefire.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mcp-docs.nichefire.com/quick-start/supported-integrations/commercial-mcp-clients/claude-connectors.md).

# Claude Connectors

Nichefire MCP works across all three Claude clients:

* Claude.ai (web)
* Claude Code
* Claude Desktop

 Which authentication methods are available depends on the client.

### Claude.ai (web)

The Claude.ai custom connector only supports **OAuth** — its "Add custom connector" screen does not accept a custom header, so an API key cannot be used here.

1. Go to [**Settings → Connectors → Add custom connector**](https://claude.ai/admin-settings/organization?modal=add-custom-connector#settings/customize-connectors).
2. Set the Name of the connector and the URL to the Nichefire MCP endpoint.
3. Upon saving, you will be requested to connect to the MCP server, click on "Connect" to sign in and approve the connection.
4. Once approved, the connector appears with all available tools in the configuration modal, this means the connection has been successfully setup.

Once authorization is complete, Claude displays the tools available through Nichefire MCP. This confirms that the connection has been configured successfully.

**Test the connection**

1. Open a new conversation.
2. Make sure the Nichefire connector is enabled for the conversation.
3. Send the following message:

> Can you search for the latest trends around coffee using Firesearch?

Claude should call Nichefire MCP and return the relevant trends.

### Claude Desktop

Claude Desktop supports both OAuth and API key.

**OAuth** — add the server through Desktop's connector settings, the same way as Claude.ai (web).

**API key** — add it to your config file using the `mcp-remote` bridge:

```json
{
  "mcpServers": {
    "nichefire": {
      "command": "npx",
      "args": ["mcp-remote", "<MCP_URL>", "--header", "x-api-key: <YOUR_API_KEY>"]
    }
  }
}
```

## Claude Code

Claude Code supports both OAuth and API-key authentication. Nichefire MCP can be registered directly from the command line using the HTTP transport.

#### **Option 1: OAuth**

1. Open a terminal.
2. Add the Nichefire MCP server without an authentication header:

```
claude mcp add --transport http nichefire <MCP_URL>
```

3. Replace `<MCP_URL>` with the endpoint assigned to your Nichefire environment.
4. Start Claude Code:

```
claude
```

5. Run the following command inside Claude Code:

```
/mcp
```

6. Select the `nichefire` server.
7. Follow the sign-in flow and approve the connection.
8. Return to Claude Code after authorization is complete.

#### **Option 2: API key**

1. Open a terminal.
2. Run the following command:

```
claude mcp add --transport http nichefire <MCP_URL> \  --header "x-api-key: <YOUR_API_KEY>"
```

3. Replace `<MCP_URL>` with the endpoint assigned to your Nichefire environment.
4. Replace `<YOUR_API_KEY>` with the corresponding API key.
5. Start or restart Claude Code.
6. Run `/mcp` to confirm that the `nichefire` server is connected.

#### **Test the connection**

Send the following prompt inside Claude Code:

> Can you search for the latest trends around coffee using Firesearch?

Claude Code should call Nichefire MCP and return the relevant trends.

### Claude Desktop

Claude Desktop supports both OAuth and API key.

**OAuth** — add the server through Desktop's connector settings, the same way as Claude.ai (web).

**API key** — add it to your config file using the `mcp-remote` bridge:

```json
{
  "mcpServers": {
    "nichefire": {
      "command": "npx",
      "args": ["mcp-remote", "<MCP_URL>", "--header", "x-api-key: <YOUR_API_KEY>"]
    }
  }
}
```