Windows desktop lists local STDIO MCP servers as enabled but provides zero tools

Resolved 💬 2 comments Opened Aug 16, 2026 by shawn-jacobson Closed Aug 16, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

codex-desktop-local-mcp-diagnostic.md

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 12 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#38162

Powered by Codex Action

shawn-jacobson · 12 days ago

This appears to be a duplicate of #38162.

My reproduction confirms the same post-discovery tool-exposure failure on a newer Windows desktop build, 26.810.52044, with app server 0.148.0-alpha.9. A different local STDIO server successfully completed MCP initialization in 5.188 seconds and returned 63 tools, but new Chat tasks received zero tools from that namespace. The problem persisted after a full reboot and after allowing the desktop app to finish warming up.

Please treat my report as an additional reproduction showing that the issue persists in a newer release and affects MCP servers other than Tessl.