> 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/collaboration.md).

# Collaboration

This article describes what you can do in the **Collaboration** capability area, with example prompts for each action.

{% hint style="info" %}
The underlying tool names and implementation details in this section are subject to change as the MCP server evolves. You do not need to know the tool names to use the MCP server — simply describe what you want to do in natural language and your AI assistant will handle the rest.
{% endhint %}

***

Collaboration tools let you manage who has access to a project and check the health of your federated network before running jobs.

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

## Viewing and managing collaborators

List all [collaborators](/collaborators/what-is-a-collaborator.md) on a project, invite new users or sites, or remove access for someone who should no longer be on the project.

* *"Who has access to the oncology project?"*
* *"List all collaborators and their roles in the trial project."*
* *"Invite <jane@hospital.org> to the oncology project as an analyst."*
* *"Add <site-b@partner.org> to the trial project."*
* *"Remove <john@hospital.org> from the oncology project."*

## Checking workgroup and site connectivity

Before submitting a long-running federated job, check that all required sites are online and reachable.

* *"Are all sites in my workgroup online?"*
* *"Check the connectivity status of the sites in the oncology project before I run the analysis."*
* *"When was Site B last seen?"*


---

# 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/collaboration.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.