[Bug] MCP dynamic tool proxy returns unsupported call for all MCP tools
Open 💬 1 comment Opened May 16, 2026 by MyuanHIT
Description
MCP server connection works (resources can be listed and read), but all MCP dynamic tools (mcp__matlab__, mcp__node_repl__) return unsupported call when invoked.
Environment
- Codex version: 26.513.31313 (Desktop, Windows)
- OS: Windows
- Model provider: Custom (DeepSeek V4 via cc-switch proxy at localhost:3000)
- wire_api: responses (also tested chat - same result)
- MCP servers: MATLAB MCP Core Server v0.9.1, Node REPL
Steps to Reproduce
- Configure any MCP server in
config.toml(tested with MATLAB Agentic Toolkit and Node REPL) - Start Codex session
- Verify MCP connection works:
list_mcp_resourcesreturns resources from the MCP server successfully - Try calling an MCP tool:
mcp__matlab__ormcp__node_repl__ - Observe error:
unsupported call: mcp__matlab__/unsupported call: mcp__node_repl__
What Works
list_mcp_resources- returns resources correctlyread_mcp_resource- reads resource content correctly- All built-in Codex tools (shell, apply_patch, etc.) work fine
- MCP server logs show
list_all_toolssucceeded and tools were registered
What Does Not Work
- Any MCP dynamic tool call (mcp__matlab__, mcp__node_repl__) fails with unsupported call error
- The model correctly emits function calls with proper arguments, but Codex tool router rejects them
Log Evidence
From Codex SQLite logs:
ERROR|codex_core::tools::router|...:dispatch_tool_call_with_code_mode_result{
otel.name=mcp__matlab__ tool_name=mcp__matlab__ ...}:
error=unsupported call: mcp__matlab__
Expected Behavior
MCP tools should be callable just like built-in tools.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗