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

# Multiplexing

The Hex-Rays IDA MCP Server can serve more than one agent at once, as long as they're running on the same machine. Two separate agent instances (for example, two Claude Code sessions), can attach to the same running server and work on the same open databases together, seeing each other's changes immediately: when one agent renames a function or adds a comment, the other sees it right away.

This makes it possible to split a large or difficult binary between two locally-running agents, or to have one person driving interactively in the IDA GUI while a second, local agent explores the same database in the background.

![Multiple clients sharing local databases](https://1926493584-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7fgl4EL0WWJ18ZQcIxE%2Fuploads%2Fgit-blob-e9a0b76c37ee5590e690876f3e5033200fcbe85a%2Fmcp-multiplexing-diagram.png?alt=media)

For the underlying technical details, see [the library repository](https://github.com/HexRaysSA/ida-nexus/).


---

# 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/multiplexing.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.