Use Progressive disclosure for MCP, apps and plugins #16919

What variant of Codex are you using?

App

What feature would you like to see?

Would it be possible to use the same logic used by skills to load only if necessary MCP and plugins ? It would be nice to be able to have all the MCP and plugins installed in codex for the different use cases and scenarios but only load them in the context when really needed.

This would allow reducing the token used per thread, without having to totally disable the MCPs and plugins.

So if a thread does not need Sentry MCP to run, it would not load Sentry MCP, but it would know Sentry MCP could be available and used if necessary. Then while the thread is going on, if at some point it feels it could be helpful, it would then enable it and load it in the context.

Currently I have to go to settings, disable MCPs I won't need in the next thread, start the thread and if in it or in a new thread it might be useful, I go back to settings, enable the MCP, click the restart button, then start or continue the thread that needs the MCP. This feels like a lot of manual tasks that could be automated by codex.

Also it would allow to have concurrent threads running with different loaded tools tailored for each thread, and not a big one size fit all tasks configuration.

We would also be able to force the loading of the mcp like we do with skills for example /sentry-mcp in the prompt.

Additional information

No response