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.

Claude Desktop

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

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

1

Open Settings

Open Claude and click your user icon in the bottom left. Click Settings → Connectors. Alternatively, click Customize → Connectors.

2

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

3

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.

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.

1

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/

2

Add the server entry

Edit claude_desktop_config.json and add the following block:

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

3

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.

Claude Code CLI

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

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

1

Add the server

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

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)

2

Verify registration

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

claude mcp list

3

Authenticate

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

claude
> "List my Rhino Health projects"

Cursor IDE

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

1

Open MCP Settings

Go to Cursor Settings → MCP → click "+ Add new global MCP server". Select type: Streamable HTTP.

2

Add the server

Alternatively, create or edit the config file directly:

• Global config: ~/.cursor/mcp.json

• Per-project config: .cursor/mcp.json

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

3

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.

VS Code + GitHub Copilot

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

1

Create the config file

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

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

2

Restart VS Code

Restart VS Code to load the new MCP configuration.

3

Enable Agent mode

Open Copilot Chat (Ctrl+Shift+I) and switch to Agent mode using the dropdown at the top of the chat panel.

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).

1

Open MCP Config

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

• macOS: ~/.codeium/windsurf/mcp_config.json

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

2

Restart and authenticate

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

Using a Different Client?

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 [e-mail] and include your client name, the error message, and the result of the health check (curl https://mcp.rhinohealth.com/health).