> 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/concepts/where-mcp-fits.md).

# Comparing AI Tools

Hex-Rays ships several ways to bring AI and automation into IDA, and they solve different problems:

* [**The Hex-Rays IDA MCP Server**](/core/mcp.md) connects your own agent harness, such as Claude Code or Codex, to IDA. It lets you work side-by-side with an agent in the GUI, or run multiple agents against the same local databases at once.
* [**Assist**](https://github.com/HexRaysSA/ida-docs/tree/9.4/core/assist/README.md) is an AI copilot built directly into the IDA GUI, for interactive help while you work in a session.
* [**idalib**](/core/idalib.md) runs IDA headlessly as a library, for scripting, automation pipelines, and CI/CD.

See [Agentic IDA with idalib](/core/idalib/concepts/agentic-ida-with-idalib.md) for how idalib specifically fits into agent-driven workflows.


---

# 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/concepts/where-mcp-fits.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.