> 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/mcp-environments-troubleshooting-faqs.md).

# MCP Environments, Troubleshooting, FAQs

This article covers environment-specific server URLs, solutions for common connection errors, and answers to frequently asked questions.

### Environments

Each Rhino FCP environment has a dedicated MCP endpoint. The production URL connects only to production — there is no cross-environment access.

| Environment        | Cloud | URL                                     |
| ------------------ | ----- | --------------------------------------- |
| **Production**     | AWS   | `https://mcp.rhinohealth.com/mcp`       |
| **Production**     | GCP   | `https://mcp.rhinofcp.com/mcp`          |
| **Production US2** | GCP   | `https://mcp-prod-us2.rhinofcp.com/mcp` |

#### Health check

To verify that a specific environment is operational, run:

```
curl https://mcp.rhinohealth.com/health
# → {"status":"ok","version":"1.0.0"}
```

Replace the hostname with the relevant environment URL from the table above.

### Troubleshooting

| Error or symptom                         | Resolution                                                                                                                        |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Browser doesn't open for login**       | Check your default browser settings. Fully quit and reopen the AI client.                                                         |
| **Server not responding / timeout**      | Verify the URL ends with `/mcp`. Run the curl health check above to confirm the server is reachable.                              |
| **Invalid Host / 421 error**             | Ensure the full `https://` URL is used. Update `mcp-remote` to the latest version.                                                |
| **OAuth succeeds but tools fail**        | Restart the client to refresh the OAuth token. Verify that your account has access to the relevant project in the Rhino platform. |
| **NOT\_AUTHENTICATED error**             | Your session token has expired. Restart the AI client — the OAuth flow will trigger automatically on the next tool call.          |
| **Tools appear but no data is returned** | Confirm your project access in the Rhino platform and check your workgroup membership.                                            |

If you are still experiencing issues, contact <support@rhinohealth.com> with your client name, the full error message, and the result of the health check.

### Frequently Asked Questions

<details>

<summary>Do I need to install anything to use the MCP server?</summary>

No. The MCP server runs entirely on Rhino's cloud infrastructure — there is nothing to install or update on your end. For most clients (Cursor, Claude Desktop, VS Code) you simply configure the server URL. The only exception is Windsurf and other stdio-only clients, which require Node.js for the `mcp-remote` bridge. See [Prerequisites and Authentication](/using-the-rhino-mcp-server/prerequisites-and-authentication.md) for details.

</details>

<details>

<summary>Is my data safe?</summary>

Yes. The MCP server enforces the same permissions as the Rhino FCP platform itself. Raw data never leaves hospital sites — all results are aggregated before being returned to your AI client. You will never see individual patient records through any MCP tool.

</details>

<details>

<summary>Can multiple people use the MCP server at the same time?</summary>

Yes. The MCP server is multi-tenant. Each user authenticates with their own Rhino Health account and sees only the projects and data they are authorised to access. There is no shared session between users.

</details>

<details>

<summary>Which environment am I connected to?</summary>

Each environment has its own dedicated URL — the production URL connects only to production, staging to staging, and so on. You can verify the environment and server version at any time by running the health check or by using `rhino_check_connection`.

</details>

<details>

<summary>How do I disconnect or remove the server?</summary>

Remove the `rhino-health` entry from your client's config file and restart the client. For Claude Code CLI, run:

```
claude mcp remove rhino-health
```

</details>

<details>

<summary>My token expired — how do I re-authenticate?</summary>

Simply restart your AI client. The OAuth flow will trigger automatically on the next tool call. No configuration changes are required.

</details>

<details>

<summary>Does the MCP server work with non-Claude AI assistants?</summary>

Yes. The Rhino MCP server supports any client that implements the Model Context Protocol, including the OpenAI Responses API, Cursor, VS Code Copilot, Windsurf, and any custom MCP-compatible client. For HTTP-native clients, use the URL directly. For stdio-only clients, use the `mcp-remote` bridge as described in [Supported Clients](/using-the-rhino-mcp-server/supported-clients.md).

</details>