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

# Getting Started

Set up the [Hex-Rays IDA MCP Server](https://github.com/HexRaysSA/ida-mcp) automatically via [HCLI](https://hcli.docs.hex-rays.com) and get started in minutes.

## Prerequisites

* IDA 9.4 or higher (IDA Home, IDA Pro, or IDA Classroom), with idalib installed
* Installed in your PATH:
  * [Git](https://git-scm.com/)
  * [uv](https://github.com/astral-sh/uv)
* Python 3.11+

{% hint style="info" %}
If you haven't set up a Python virtual environment for IDA yet, see [IDAPython Environment](/getting-started/idapython-environment.md).
{% endhint %}

{% hint style="info" %}
We recommend disabling other IDA MCP servers before installing, to avoid confusing your agent.
{% endhint %}

## Automatic installation (recommended)

Install the Hex-Rays IDA MCP using [HCLI](https://hcli.docs.hex-rays.com):

```
uvx ida-hcli mcp install
```

This will also install the GUI plugin (giving you access to the opened IDA instances) and interactively offer to install the supported agent plugins for you.

{% hint style="info" %}
For manual installation steps (installing the GUI plugin or a specific agent harness individually), see [manual installation](https://github.com/HexRaysSA/ida-mcp#manual-installation).
{% endhint %}

## Try it

Start your agent harness and ask it something like:

> Reverse /path/to/sample.elf for me in IDA

To check the GUI integration, open a database in IDA and ask your harness:

> What do I have open in the IDA GUI?


---

# 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.hex-rays.com/core/mcp/getting-started.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.