Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop for Windows does not load local MCP plugin tools [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19304•Fetched 2026-04-24 10:38:55
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
MCQ2000MCQ2000
Participants
github-actions[bot]github-actions[bot]MCQ2000MCQ2000
Timeline (top)
labeled ×5commented ×1
RAW_BUFFERClick to expand / collapse

I submitted in-app feedback with uploaded thread:

019dbc78-7907-7dc3-a498-8255e105f63c

Summary: Codex Desktop for Windows does not expose tools from a local MCP plugin even though the plugin is registered, enabled, cached, and the MCP server works when run directly.

Expected: After installing/enabling a local MCP plugin and restarting Codex Desktop, tools from that plugin should be available to Codex.

Actual: Tool discovery returns 0 tools for the local plugin, and no tools from the plugin are registered after both app restart and full computer restart.

Validation: The plugin's MCP server responds successfully to initialize and tools/list when run directly from the plugin root.

Additional context: The in-app feedback flow provided this issue template link: https://github.com/openai/codex/issues/new?template=1-codex-app.yml&steps=Uploaded%20thread%3A%20019dbc78-7907-7dc3-a498-8255e105f63c

extent analysis

TL;DR

The issue may be resolved by verifying the plugin registration and caching process in Codex Desktop for Windows.

Guidance

  • Check the plugin's registration status in Codex Desktop to ensure it is properly enabled and recognized.
  • Verify that the plugin's MCP server is correctly configured and responding as expected when run directly.
  • Investigate the tool discovery mechanism in Codex Desktop to see if there are any issues with discovering tools from local plugins.
  • Review the caching process to ensure that the plugin's tools are being properly cached and made available to Codex.

Notes

The issue seems to be specific to the interaction between Codex Desktop and local MCP plugins, so any solution will depend on the details of this integration.

Recommendation

Apply workaround: Verify the plugin registration, caching, and tool discovery processes to identify and address any issues that may be preventing the tools from being exposed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING