Developer Lets Codex Autonomously Configure and Fix MCP Connections Hands-Free

On October 8, developer dfinke posted a thread about using Codex's computer use capability to autonomously set up and debug MCP: he never touched his computer—Codex launched VS Code on its own, wrote the mcp. config, pointed to the right port, started the local server from the correct directory, and ran baseline tests to confirm everything connected.

Confirmed

dfinke complained that manually configuring MCP is a chore: open VS Code, write the mcp., point to localhost, start the server, check the connection, tweak, repeat—so he decided to hand it all to Codex.
When the MCP server wouldn't connect in VS Code Insiders, he simply told Codex to "use computer use and sort it out yourself," then made no manual intervention.
Codex's debugging process included: reading logs to find an unhandled branch; deliberately making a change that would break functionality and confirming it actually broke—a real reproduction, not a guess; then locating on its own where VS Code logs MCP activity, a location the author himself didn't know.

Why it matters

A single natural-language request completed the full debug loop of reproduction, diagnosis, and repair—the author remarked that this workflow itself has become the prompt.
Computer use lets the agent directly operate the IDE interface and local environment, automating the otherwise tedious work of MCP configuration and troubleshooting, demonstrating AI agents' viability in real-world dev-ops scenarios.

2026-10-08 ~ 2026-10-08 · 5 related posts

Primary sources

Codex uses computer use to debug a broken MCP server in VS Code end to end — dfinke · 2026-10-08 21:03 (UTC+08:00)
Codex reproduces the MCP failure and locates VS Code's hidden MCP logs — dfinke · 2026-10-08 21:03 (UTC+08:00)

[source] Codex uses computer use to debug a broken MCP server in VS Code end to end — dfinke · 2026-10-08
The manual MCP setup slog the author refused to do himself — dfinke · 2026-10-08
Codex writes mcp., starts the server and verifies the connection autonomously — dfinke · 2026-10-08
[source] Codex reproduces the MCP failure and locates VS Code's hidden MCP logs — dfinke · 2026-10-08
One prompt closed the whole debugging loop: repro, diagnosis, fix and verification — dfinke · 2026-10-08