> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/es/ribbon-menu-bar/tools/all-tools/mcp-server/access-devolutions-documentation-mcp-server.md).

# Acceder al servidor MCP de documentación de Devolutions

Conecte ChatGPT, Claude, Claude Code o GitHub Copilot al servidor MCP de la documentación de Devolutions para acceder directamente a la documentación de Devolutions desde su agente.

Estos son los pasos para configurar el servidor MCP y darle acceso a la documentación de Devolutions en los agentes/LLM más habituales.

#### ChatGPT

1. Vaya a ***Workspace settings*** – ***Apps & Connectors*** – ***Create***.
2. Introduzca un ***Name*** para el nuevo conector y, a continuación, pegue `https://mcp.devolutions.net/docs` en el campo ***MCP Server URL***.

#### Claude

1. Navegue a ***Admin settings*** – ***Connectors*** – ***Add custom connector***.
2. Introduzca un nombre para el conector y, a continuación, pegue `https://mcp.devolutions.net/docs` en el segundo campo.

#### Claude Code

Introduzca lo siguiente:

```
claude mcp add --transport http "DevolutionsDocs" https://mcp.devolutions.net/docs
```

#### GitHub Copilot

1. En la paleta de comandos, vaya a ***MCP: Add Server*** y, a continuación, a ***HTTP (HTTP or Server-Sent Events)***.
2. Cuando se le solicite una URL, pegue `https://mcp.devolutions.net/docs` y elija un nombre para el servidor MCP. Pulse <kbd>Enter</kbd>.


---

# 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.devolutions.net/rdm/es/ribbon-menu-bar/tools/all-tools/mcp-server/access-devolutions-documentation-mcp-server.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.
