Codex CLI doesn't know about the MCP in conversation
Resolved 💬 4 comments Opened Sep 24, 2025 by PabloLION Closed Nov 23, 2025
What version of Codex is running?
codex-cli 0.40.0 , codex-cli 0.39.0
Which model were you using?
gpt-5-codex
What platform is your computer?
Darwin 24.6.0 arm64 arm
What steps can reproduce the bug?
Install some MCP like context7
codex
/approvals
# select 3. Full Access
outcome is something like this dialogue
▌ list the available MCP server
• Ran zsh -lc ls
• Ran zsh -lc 'rg "MCP"'
■ Conversation interrupted - tell the model what to do differently
▌ what MCP do you have access to
• Ran zsh -lc 'ls -a'
• Ran zsh -lc 'cat .mcp.json'
> Available MCP server: graphiti-memory (SSE) at http://localhost:8000/sse.
▌ what MCP tool can you call?
> I only see the configured MCP server (graphiti-memory), but I don’t have
visibility into its tool list from here. If you know it’s running, you can either
share its tool manifest or ask me to query it with the appropriate client command.
▌ use context7 to find how to "Create and Run a New Next.js App"
▌ use context7 to find how to "Create and Run a New Next.js App"
tool running...
context7.resolve-library-id({"libraryName":"next.js"})
tool success, duration: 487ms
context7.resolve-library-id({"libraryName":"next.js"})
Available Libraries (top matches):Each result includes:- Library ID: Context7-
compatible identifier (format: /org/project)- Name: Library or package name-
Description: Short summary- Code Snippets: Number of available code examples- Trust
Score: Authority indicator- Versions: List of versions if available. Use one of
those versions if and only if the user explicitly provides a vers...
tool running...
context7.get-library-docs({"context7CompatibleLibraryID":"/vercel/
next.js","topic":"Create and Run a New Next.js App","tokens":2000})
tool success, duration: 350ms
context7.get-library-docs({"context7CompatibleLibraryID":"/vercel/
next.js","topic":"Create and Run a New Next.js App","tokens":2000})
================CODE SNIPPETS================TITLE: Create and Run a New Next.js App
(Quick Start)DESCRIPTION: Demonstrates the quickest way to scaffold a new Next.js
application named `my-app` using the `create-next-app` CLI with default settings.
The commands create the project, change into the new directory, and start the
development server. Examples are provided for pnpm, npm, yarn...
> Create & Run Next.js App
- Run pnpm create next-app@latest my-app --yes then cd my-app and pnpm dev; same
flow works with npm, yarn, or bun (npm run dev, yarn dev, bun dev). Source: /
vercel/next.js docs (Installation quick start).
- To walk through prompts interactively, use npx create-next-app@latest (or yarn
create next-app, pnpm create next-app, bunx create-next-app) and follow the CLI
questions.
- When you need a starter template, add --example <template> to the command (e.g.,
--example blog my-blog) to scaffold from featured examples.
Let me know if you want steps for deploying or customizing the initial setup.
▌ list the available MCP servers
• Ran zsh -lc 'cat .mcp.json'
> Available MCP Servers
- graphiti-memory (sse, URL http://localhost:8000/sse)
▌ what MCP do you have access to
> Accessible MCP
- graphiti-memory at http://localhost:8000/sse
/mcp
🔌 MCP Tools
• Server: context7
• Command: context7-mcp
• Tools: get-library-docs, resolve-library-id
• Server: playwright
• Command: mcp-server-playwright
• Tools: browser_click, browser_close, browser_console_messages, browser_drag,
browser_evaluate, browser_file_upload, browser_fill_form, browser_handle_dialog,
browser_hover, browser_install, browser_navigate, browser_navigate_back,
browser_network_requests, browser_press_key, browser_resize, browser_select_option,
browser_snapshot, browser_tabs, browser_take_screenshot, browser_type,
browser_wait_for
▌ what MCP can I use here?
> You can use the graphiti-memory MCP server (type: sse, URL http://localhost:8000/
sse).
But the graphiti-memory server was installed for Claude Code before, and I removed it later.
In some other dialogue Codex CLI just says "None" or saying it needs approvals to access MCP.
What is the expected behavior?
list all the MCP available like in /mcp command
What do you see instead?
see the dialogue
Additional information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗