MCP tool discovery InOp
Resolved 💬 6 comments Opened Feb 14, 2026 by iharc-jordan Closed Feb 21, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
102 alpha 6
What subscription do you have?
pro
Which model were you using?
5.3 codex
What platform is your computer?
windows
What terminal emulator and version are you using (if applicable)?
wsl ubuntu
What issue are you seeing?
With the bm_25 search only exposing codex apps and not non app mcp tools, codex is unable to find/use mcp tools. Specifically, MCPs that only have tools and not resources/templates.
What steps can reproduce the bug?
Using the standard supabse mcp in a fresh Codex session, the model is unable to see/use the mcp tools.
What is the expected behavior?
_No response_
Additional information
_No response_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I have confirmed this bug does not appear in alpha 4 after reverting and resuming the same session.
I think this is a duplicate of #11264, no?
Are you saying that you think there was a regression between alpha 4 and alpha 6?
I believe so. It seems there was a regression between 4 and 6 and reverting back to 4 fixes it. This PR is what I think might be a reason.
I attempted to have the model manually find the MCP tools in multiple ways to no avail. The only fix was moving back to alpha 4.
As a sidenote, I am not sure if it is helpful for me to bring forward these types of issues in the alpha versions. I love testing them, but don't want to cause extra work/headaches for you guys by creating issues like this if it's not helpful.
This seems to be resolved in alpha 8. The downside is that the non-Codex app mcp schemas are back to being injected in the initial prompt/context taking up a fair amount of context.