> 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/ribbon-menu-bar/tools/all-tools/mcp-server/access-devolutions-documentation-mcp-server.md).

# Access Devolutions' documentation MCP server

Connect ChatGPT, Claude, Claude Code, or GitHub Copilot to the Devolutions documentation MCP server for direct access to Devolutions docs from your agent.

Here are the steps to configure MCP server to give it access to Devolutions' documentation for the most common agents/LLMs.

#### ChatGPT

1. Head to ***Workspace settings*** – ***Apps & Connectors*** – ***Create***.
2. Enter a ***Name*** for the new connector, then paste `https://mcp.devolutions.net/docs` in the ***MCP Server URL*** field.

#### Claude

1. Navigate to ***Admin settings*** – ***Connectors*** – ***Add custom connector***.
2. Enter a name for the connector, then paste `https://mcp.devolutions.net/docs` in the second field.

#### Claude Code

Enter the following:

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

#### GitHub Copilot

1. In the command palette, go to ***MCP: Add Server***, then ***HTTP (HTTP or Server-Sent Events)***.
2. When asked for a URL, paste `https://mcp.devolutions.net/docs` and choose a name for the MCP Server. Press <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/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.