> 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-via-mcp.md).

# Collaboration via MCP

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

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?"

## 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 project X online?"*
* *"Check the connectivity status of the sites in the oncology project before I run the analysis."*


---

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