> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/using-the-rhino-mcp-server/supported-clients.md).

# Supported Clients

The Rhino FCP MCP server supports any AI client that implements the Model Context Protocol. This article provides step-by-step setup instructions for each supported client.

All clients use the same production endpoint: `https://mcp.rhinohealth.com/mcp`

For environment-specific URLs (staging, QA, dev), see [Environments, Troubleshooting & FAQ](/using-the-rhino-mcp-server/mcp-environments-troubleshooting-faqs.md).

### Claude Desktop

**Transport:** Native HTTP | **Node.js required:** No | **Difficulty:** Easiest

Claude Desktop has a built-in connector UI — no config file needed.

{% stepper %}
{% step %}

#### Open Settings

Open Claude and click your user icon in the bottom left. Click **Settings → Connectors**. Alternatively, click **Customize → Connectors**.
{% endstep %}

{% step %}

#### Add a custom connector

Click the **+** icon and select *Add custom connector*. Enter the following details and click **Save**:

* **Name:** `Rhino FCP`
* **URL:** `https://mcp.rhinohealth.com/mcp`
  {% endstep %}

{% step %}

#### Authenticate

Click **Connect**. A browser window will open — first connecting to Claude on the web, then presenting the Rhino Health login page. Enter your credentials.
{% endstep %}
{% endstepper %}

### Claude Desktop — Dev Mode (Config File)

**Transport:** Native HTTP via mcp-remote | **Node.js required:** Yes | **Difficulty:** Intermediate

For advanced users who prefer editing the config file directly.

{% stepper %}
{% step %}

#### Locate the config file

Find `claude_desktop_config.json` in the following location for your operating system:

* **macOS:** `~/Library/Application Support/Claude/`
* **Windows:** `%APPDATA%\Claude\`
* **Linux:** `~/.config/Claude/`
  {% endstep %}

{% step %}

#### Add the server entry

Edit `claude_desktop_config.json` and add the following block:

```json
{
  "mcpServers": {
    "rhino-health": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.rhinohealth.com/mcp"
      ]
    }
  }
}
```

{% endstep %}

{% step %}

#### Restart and authenticate

Quit Claude Desktop (**Cmd+Q** on macOS) and reopen it. Look for the **hammer icon** in the chat input. Ask *"List my Rhino Health projects"* — your browser will open for OAuth login.
{% endstep %}
{% endstepper %}

### Claude Code CLI

**Transport:** HTTP | **Node.js required:** No | **Difficulty:** Easy

No config file needed — everything is managed via the CLI.

{% stepper %}
{% step %}

#### Add the server

Run the following command in your terminal. Use `--scope user` to make the server available globally across all projects:

```bash
claude mcp add \
     --transport http \
     rhino-health \
     https://mcp.rhinohealth.com/mcp

# Scope options:
#   --scope user     (global — available in all projects)
#   --scope project  (default — current project only)
```

{% endstep %}

{% step %}

#### Verify registration

Run the following to confirm `rhino-health` appears in your server list:

```bash
claude mcp list
```

{% endstep %}

{% step %}

#### Authenticate

Start a Claude session and ask a Rhino question. Your browser will open automatically for OAuth login:

```bash
claude
> "List my Rhino Health projects"
```

{% endstep %}
{% endstepper %}

### Cursor IDE

**Transport:** Native HTTP (Streamable HTTP) | **Node.js required:** No | **Difficulty:** Easy

{% stepper %}
{% step %}

#### Open MCP Settings

Go to Cursor Settings → MCP → click *"+ Add new global MCP server"*. Select type: **Streamable HTTP**.
{% endstep %}

{% step %}

#### Add the server

Alternatively, create or edit the config file directly:

* Global config: `~/.cursor/mcp.json`
* Per-project config: `.cursor/mcp.json`

```json
{
  "mcpServers": {
    "rhino-health": {
      "url": "https://mcp.rhinohealth.com/mcp"
    }
  }
}
```

{% endstep %}

{% step %}

#### Restart and authenticate

Quit and reopen Cursor. Open Agent mode (**Cmd+L**) and ask *"List my Rhino Health projects"*. A **green indicator** in MCP settings confirms you are connected.
{% endstep %}
{% endstepper %}

### VS Code + GitHub Copilot

**Transport:** HTTP | **Node.js required:** No | **Requires:** VS Code 1.99+ and an active GitHub Copilot subscription

{% stepper %}
{% step %}

#### Create the config file

Create `.vscode/mcp.json` in your workspace root. Alternatively, use the Command Palette → *MCP: Open Workspace Folder MCP Config*:

```json
{
  "servers": {
    "rhino-health": {
      "type": "http",
      "url": "https://mcp.rhinohealth.com/mcp"
    }
  }
}
```

{% endstep %}

{% step %}

#### Restart VS Code

Restart VS Code to load the new MCP configuration.
{% endstep %}

{% step %}

#### Enable Agent mode

Open Copilot Chat (**Ctrl+Shift+I**) and switch to **Agent mode** using the dropdown at the top of the chat panel.
{% endstep %}
{% endstepper %}

### Windsurf

**Transport:** mcp-remote bridge | **Node.js required:** Yes (npx must be on PATH) | **Difficulty:** Intermediate

Windsurf uses the `mcp-remote` bridge. Ensure Node.js is installed before proceeding (see [Prerequisites and Authentication](/using-the-rhino-mcp-server/prerequisites-and-authentication.md)).

{% stepper %}
{% step %}

#### Open MCP Config

Click the hammer icon in the Cascade toolbar → **Configure**. Or edit the config file directly:

* **macOS:** `~/.codeium/windsurf/mcp_config.json`

```json
{
  "mcpServers": {
    "rhino-health": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.rhinohealth.com/mcp"
      ]
    }
  }
}
```

{% endstep %}

{% step %}

#### Restart and authenticate

Restart the IDE. Open Cascade chat and ask a Rhino question — mcp-remote will open your browser for OAuth login.
{% endstep %}
{% endstepper %}

<details>

<summary>Using a Different Client?</summary>

The clients listed above are the ones Rhino officially documents and tests against. However, the MCP server uses the open Model Context Protocol standard, so it is compatible with a much broader range of AI assistants and coding tools.

If your client is not listed here, the general connection details are:

* **Server URL:** `https://mcp.rhinohealth.com/mcp`
* **Transport:** Streamable HTTP (preferred) or stdio via `mcp-remote`
* **Authentication:** OAuth 2.1 with PKCE — handled automatically on first use

Consult your client's documentation for instructions on adding a custom MCP server. Most clients that support MCP will have a settings panel, config file, or CLI command for this.

If you run into issues connecting a client that isn't listed above, contact <support@rhinohealth.com> and include your client name, the error message, and the result of the health check (`curl https://mcp.rhinohealth.com/health`).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rhinofcp.com/using-the-rhino-mcp-server/supported-clients.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.