> 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/projects-and-datasets-via-mcp.md).

# Projects & Datasets via MCP

This article describes what you can do with the Rhino MCP connection in the Projects and Datasets capability areas, with example prompts for each action.

{% hint style="warning" %}
If you do not have the required permissions, you will not be able to perform the following actions.
{% endhint %}

***

## Projects

Projects are the top-level organisational unit in Rhino FCP. Each project contains datasets, code objects, runs, and a set of collaborating sites. You can list, inspect, create, and delete projects through natural language.

### Listing and viewing projects

Ask your AI assistant to show you the projects you have access to, or to get details on a specific project.

* *"List my Rhino projects."*
* *"What projects do I have access to?"*
* *"Show me the details for the Multi-site Oncology Study project."*
* *"How many sites are in my cardiology project?"*

### Creating a project

Ask your assistant to create a new project in your workgroup. You can provide a name and an optional description.

* *"Create a new project called 'Diabetes Cohort Study'."*
* *"Set up a new Rhino project for our Q3 multi-site trial. Give it a description explaining it covers sites in the EU and US."*

### Deleting a project

Project deletion is permanent — all job history, collaborator settings, and configuration will be lost. Datasets stored at sites are not affected.

* *"Delete the 'Pilot Study 2023' project."*

***

## Datasets

Datasets represent data files registered within a project. They can be local (single-site) or federated (spanning multiple sites). The MCP server lets you list, register, sync, profile, compare, and remove datasets through conversation.

### Listing and exploring datasets

Ask your assistant to show datasets available in a project, or to retrieve the schema of a specific dataset.

* *"What datasets are available in the oncology project?"*
* *"What are the column names and types in the 'patient\_cohort\_2024' dataset?"*
* *"Show me the schema for the admissions dataset."*

### Registering a dataset

You can register a file that already exists at a site as a dataset in the platform, or create a federated dataset that spans multiple sites.

* *"Register the file at '/data/cohort\_jan2025.csv' as a new dataset called 'Cohort Jan 2025' in the oncology project."*

### Profiling a dataset

Generate a statistical profile to understand your data before running analytics. Profiling returns null rates, value distributions, and summary statistics without exposing any raw rows.

* *"Profile the 'patient\_cohort\_2024' dataset."*
* *"Give me a statistical summary of the age, gender, and diagnosis columns in the admissions dataset."*
* *"What percentage of values are missing in each column of the trial dataset?"*

### Comparing datasets

Compare datasets — or the same dataset across sites — to check for distribution drift, schema differences, or cohort divergence before running federated analytics.

* *"Compare the baseline and follow-up datasets for distribution differences."*
* *"Check whether the admissions data is consistent across all three sites."*
* *"Are there any schema mismatches between the two cohort datasets?"*

### Deleting a dataset

Deleting a dataset removes the platform record only — the underlying file at the site is not affected.

* *"Delete the 'old\_cohort\_2022' dataset from the project."*
* *"Remove the federated admissions dataset."*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rhinofcp.com/using-the-rhino-mcp-server/projects-and-datasets-via-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.