> 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/overview.md).

# Overview

The [Hex-Rays IDA MCP Server](https://github.com/HexRaysSA/ida-mcp) connects and multiplexes IDA across AI agents, letting your agent see and act on the same database you have open in the IDA GUI.

It's a first-party, open-source MCP Server, built by Hex-Rays to support its own ecosystem: a supported, multiplexed connection between a fleet of AI agents and IDA. It runs fully local and lets you bring your own model, so nothing about your analysis has to leave your environment unless you choose a cloud-hosted model yourself.

See [AI & Automation Tools](/core/mcp/concepts.md) for how it compares to Assist and idalib, Hex-Rays' other AI-driven ways to work with IDA.

## Key features

### First-party and professionally supported

Built and maintained by Hex-Rays, not a community project — something you can build on and rely on for the long term.

### Fast to start

Set up in a few minutes, using the agent harness you already use. It doesn't replace your workflow, it makes it faster and smarter.

### Coordinates multiple databases and sessions

The MCP Server can manage access across several IDA databases at once. An agent can, for example, extract an embedded payload from one binary, open and analyze it as its own database, and continue reasoning about the original question without losing context.

### Built for multi-agent collaboration

Multiple agents or subagents can work on a large or difficult program together, coordinating through the server rather than stepping on each other.

### A building block, not a framework

The MCP Server uses industry-standard protocols and technologies, so it can extend existing or future systems with IDA's analysis capabilities without locking you into a particular architecture.

### Local models supported

Bring your own model and run entirely locally if you need to keep sensitive information inside your own environment.

## Licenses and Versions

The Hex-Rays IDA MCP Server is available with [**IDA Home**](https://hex-rays.com/ida-home), [**IDA Pro**](https://hex-rays.com/ida-pro) (Essential/Expert/Ultimate), and [**IDA Classroom**](https://hex-rays.com/classroom).

## Source code

The Hex-Rays IDA MCP Server is open source: [github.com/HexRaysSA/ida-mcp](https://github.com/HexRaysSA/ida-mcp).

## What next?

For installation instructions, see [Getting Started](/core/mcp/getting-started.md).


---

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