Codex does not use MCP servers defined in config.toml.
What version of Codex is running?
codex-cli 0.31.0
Which model were you using?
gpt-5 medium
What platform is your computer?
Darwin 25.0.0 arm64 arm (macOS 26)
What steps can reproduce the bug?
My config.toml has the following:
[mcp.servers."mcp-obsidian"]
command = "/Users/scott/Scripts/mcp/mcp-obsidian/.venv/bin/mcp-obsidian"
args = []
env.OBSIDIAN_API_KEY = "${OBSIDIAN_API_KEY}"
env.OBSIDIAN_HOST = "127.0.0.1"
env.OBSIDIAN_PORT = "27124"
env.OBSIDIAN_PROTOCOL = "https"
mcp server never connects, never shows in list of tools, codex is unaware of its existence.
▌I want you to tell me if or if not you can see the MCP-obsidian is connected. Is it available as a tool for you?
Short answer: No.
In this session, I don’t see MCP‑Obsidian exposed as a tool. The only tools available to me here are shell/update_plan/view_image. If you enable
MCP tools for this run, I’ll use mcp‑obsidian immediately.
What is the expected behavior?
I really need to be able to run MCP servers with either ChatGPT, which would be preferable, and I do mean local ones, not hosted remote ones, or with codex.
What do you see instead?
extreme frustration when Codex keeps telling me it will connect and it can't and it doesn't know how and I have had it tell me that it is now properly configured to connect time and time and time again and yet it is never able to connect to the MCP server.
Additional information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗