The list of tools available for a specific App/Connector should be available

Resolved 💬 3 comments Opened Feb 5, 2026 by deinspanjer Closed Mar 20, 2026

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 exposed
mcp_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_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗