> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/data-science/mcp-servers.md).

# MCP Servers

<figure><img src="/files/ZNxQXwvFzCXCg7gyxohj" alt=""><figcaption><p>MCP Server UI</p></figcaption></figure>

MCP server definitions allow configuration of services that are available through model context protocol through simple mapping of sagas as tools.&#x20;

Definition of an MCP server includes:

### Definition

* **Name:** A descriptive name
* **Description:** Detailed description of the server
* **Tags:** Descriptive tags for the server
* **Status:** Whether this server should be deployed or not
* **Version:** Current version of the server
* **Domain:** Categorization of the server based on business domain
* **Allowed For Runners:** List of runners which can service the MCP server

### Toolkit

* **Tool Sagas:** Mapping of saga flows as tools, automatically enabled in tools/list and tools/call
* **Tool States:** Mapping of state managers as read & write enabled tools
* **Resources:** Mapping of state managers as static resources, automatically enabled in resources/list and resources/read
* **Resource Templates:** Mapping of state managers as dynamic templated resources, automatically enabled in resources/templates/list and resources/read

{% hint style="info" %}
For RBAC to specific tools by different user roles, Tool Sagas provide the most flexibility (and can be used to implement all other types of tools). As a rule of thumb, it is recommended to use other tool types for resources which are accessible by all users of the agent, and switch to sagas for granular access control.
{% endhint %}

### Prompts

List of prompts returned from prompts/list and prompts/get methods

### Comments

Historical list of comments, which typically includes information on server releases


---

# 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.rierino.com/data-science/mcp-servers.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.