The list of tools available for a specific App/Connector should be available
What variant of Codex are you using?
Needed for App-Server, but core Codex capability -- affects App / IDE / CLI / Web
What feature would you like to see?
Currently if an app-server wants to list the tools available from a specific App/Connector, the only option is to parse the list of tools from codex_apps and match the snake_case names to the Initial Case names of the Apps.
The app/list tool returns AppInfo but the list of tools aren't part of that.codex_message_processor.rs uses connectors::list_connectors(&config) and returns AppsListResponse { data: Vec<AppInfo>, ... }. AppInfo doesn’t include tools.
The mcpServerStatus/list tool exposes those tools under the MCP Server name codex_apps but does not categorize the tools by App. It just returns a huge list.v2.rs defines McpServerStatus as a struct with a name and a tools HashMap<String, McpTool> but includes no connector_id or connector_name in the metadata.
Connector-aware tool info exists internally but isn’t exposedmcp_connection_manager.rs defines ToolInfo with connector_id and connector_name.
The connector-aware logic is used in core (e.g., connectors::accessible_connectors_from_mcp_tools) but those fields never make it into the app‑server protocol.
Additional information
_No response_
3 Comments
@deinspanjer, thanks for the feature request. Are you able to share a bit more about your use case — what you're working on? That will help inform prioritization.
I'm adding an "Agent Panel" functionality to an internal users TUI that helps the operators perform complex jobs around batch data changes for a production database.
The TUI is focused on providing guardrails and raising visibility of problems with these data change jobs that previously required hours of an operator's time writing SQL and studying raw query results.
While the TUI by itself is great, it is still a lot of data and even in the small POC, it has over 7 screens showing details of various parts of the job.
The next choice for me was to make the TUI host an MCP Server with tools to allow an external agent like Codex CLI to interact with it driven by operator prompts.
From there I decided to try incorporating the Agent Panel directly in the TUI itself for a single pane of glass.
While creating a settings page, I noticed that the App Connector listing wasn't showing the individual tools, so I had to "hack" around it by parsing the names of the tools from the
codex_appstool list and matching it up with the names of the Connectors.Note, I asked Codex to make a branch implementing the change, and it did and it seems to work, but I haven't put up a PR because I'm not sure if you guys want to see AI coded PRs from someone with minimal experience with the codebase. :)
Let me know if you do want it though!
See the attached screenshots for context.
<img width="1452" height="979" alt="Image" src="https://github.com/user-attachments/assets/6db69970-f20e-4e90-aeec-c6ab2109058d" />
<img width="1452" height="979" alt="Image" src="https://github.com/user-attachments/assets/44442790-cc41-492f-b3ad-c1753399a107" />
<img width="1452" height="979" alt="Image" src="https://github.com/user-attachments/assets/f5427acb-2ebc-4298-a3ae-4efea405fdee" />
This feature request hasn't received enough upvotes, so closing.