MCP server and agent mode
The intended extension connects an MCP-capable client to an analysis session. Client support for MCP does not establish compatibility with a server that has not shipped.
Intended boundary
Section titled “Intended boundary”An integration should scope access to the selected project and document which tools read information and which can modify analysis state. Modifying actions need an explicit review path. Sample contents, symbols, and comments are data, including any text that resembles instructions for an assistant.
Local transport does not guarantee local inference. A connected client can still send tool results to its configured model provider. Opt-in and data-handling documentation must cover that complete route.
Required release information
Section titled “Required release information”- VERIFY authentic package source and supported Community version.
- VERIFY transport, authentication, process lifecycle, and binding scope.
- VERIFY exact tool schemas, permissions, cancellation, and error handling.
- VERIFY controls for writes, logging, and client/model data transfer.
- VERIFY client versions and configuration locations.
See Claude, Cursor, and Codex client setup for the setup checklist. Headless analysis is an existing upstream batch workflow with a separate purpose.