> 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-getting-started.md).

# MCP Getting Started

The Rhino FCP MCP Server connects any AI assistant directly to the Rhino Federated Computing Platform. Through natural language, you can run federated analytics, explore datasets, execute code, and monitor jobs — all without raw data ever leaving your sites.

This section covers everything you need to get started and use the MCP server effectively.

***

### What You Can Do

The MCP server exposes 8 capability areas, each mapped to a set of tools your AI assistant can invoke:

| Capability Area    | What You Can Do                                                                                              |
| ------------------ | ------------------------------------------------------------------------------------------------------------ |
| **Authentication** | Login, confirm identity, verify connectivity                                                                 |
| **Projects**       | List, inspect, create, and delete federated projects                                                         |
| **Datasets**       | Register, sync, profile, compare, and delete datasets — including federated datasets spanning multiple sites |
| **Queries**        | Run mean, Kaplan-Meier, Cox PH, Table 1, chi-square, SQL, and more via a single unified tool                 |
| **Execution**      | Upload Python code objects, execute them across sites, launch NVFlare training jobs                          |
| **Monitoring**     | Check run status, stream logs, list recent runs, halt jobs                                                   |
| **Collaboration**  | List, invite, and remove collaborators; check site connectivity and workgroup health                         |
| **Harmonization**  | Manage schemas, browse vocabularies, apply semantic and syntactic mappings, run full pipelines               |

***

### Privacy and Data Safety

Privacy is enforced at the platform level. All results returned by the MCP server are **aggregated** — raw patient data never leaves hospital sites. You will never see individual patient records through any MCP tool.

The MCP server enforces the same access permissions as the Rhino FCP platform itself. Each user authenticates with their own account and sees only the projects and data they are authorised to access.

***

### Base URL

The MCP server endpoint is:

```auto
https://mcp.rhinohealth.com/mcp
```


---

# 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/mcp-getting-started.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.