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

# MCP Server

- [MCP Server Overview](https://docs.remote.it/mcp-server/mcp.md): The hosted Remote.It MCP server lets AI assistants like Claude inventory devices, open connections, manage services and run scripts on your fleet.
- [Connect Claude](https://docs.remote.it/mcp-server/connect-claude.md): Add Remote.It as a connector in Claude so it can inventory and manage your devices in conversation, using OAuth sign-in with no API keys.
- [Tool Reference](https://docs.remote.it/mcp-server/tools.md): Every tool the Remote.It MCP server exposes to your AI assistant — devices, connections, services, networks and scripting — and which ones need approval.
- [Prompt Library](https://docs.remote.it/mcp-server/prompt-library.md): Forty-plus things to ask your AI assistant once the Remote.It MCP server is connected — fleet triage, diagnostics, access control, commissioning and fleet-wide scripting.
- [Permissions & Safety](https://docs.remote.it/mcp-server/permissions-and-safety.md): How the Remote.It MCP server protects your infrastructure — the capabilities you grant, your existing account permissions, and confirmation gates on risky operations.
- [Security Review Brief](https://docs.remote.it/mcp-server/security-review.md): The security brief for IT and OT teams reviewing the Remote.It MCP server — what changes, what doesn't, network exposure, authentication, authorization, auditability and recommended deployment posture


---

# 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.remote.it/mcp-server.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.