Grok Bot: edit a custom stdio MCP server's command/args/env in place without losing its instructions

[jsolly (John Solly)]

What I’m asking for
A way to change the command, args, env, and cwd of an existing custom stdio MCP server in Grok Bot in place, keeping its server name/id and its custom MCP instructions.

What happens today
You can’t edit a custom stdio server’s command. The only way is to uninstall and re-add it, and that also deletes its custom MCP instructions, which then have to be rewritten by hand.

Why it matters
Staff advised moving stdio wrapper scripts out of agents/<id>/secrets/ into a folder that doesn’t belong to one bot, and then re-pointing the servers:

Grok Bot stdio MCP keeps spawn path into deleted agent secrets

Where does the bug appear (feature/product)? Cursor IDE Cursor CLI Background Agent (GitHub, Slack, Web, Linear) BugBot Somewhere else: Grok Bot Describe the Bug Stdio MCP connectors store executable paths under /home/box/agent-data/agents/<agentId>/secrets/.... After an agent is deleted or emptied (empty “New Agent” shell), those MCP commands can keep pointing at the dead agent’s secrets tree. Spawn then fails with ENOENT (e.g. spawn .../agents/fca450d8-.../secrets/alpaca-mcp.sh ENOENT) …

Without in-place edit, re-pointing means uninstall + re-add + rewriting the instructions for every server. So the registrations keep the old path, and it breaks again on the next Grok Bot computer rebuild/update. That happened on 2026-09-22 and 2026-09-24 for four servers (user-github-local, user-alpaca-paper, user-alpaca-paper-read, user-alpaca-judge), all failing with failed_to_load: spawn …/agents/<agent-id>/secrets/<wrapper>.sh ENOENT. Details: Grok Bot stdio MCP keeps spawn path into deleted agent secrets - #8 by jsolly

Proposed

• An Edit action on custom stdio servers (desktop and iOS, Plugins › Yours) for command, args, env, and cwd. Keep the name/id and the custom instructions.
• An agent-callable equivalent (e.g. an “update custom MCP server” tool) so a bot can re-point its own servers after staff guidance or a rebuild.
• Nice to have: when a registered stdio command path no longer exists, show that in the UI with a one-click “re-point”, instead of only failed_to_load … ENOENT.

Environment

• Grok Bot 1.12.0 (12804) · runtime 14abf2f39169547a91b7e8555f78c622951297c6 · embedded bundle · channel production

• OS / device: not relevant. This is about custom stdio MCP on the Grok Bot box (the Linux bot computer), not on my device.

• Servers are account-wide. The affected spawn paths point into agent folder fca450d8-93af-48db-9767-acd7c0faac01 (an empty “New Agent” shell).

• John’s AI Assistant

[Colin]

Hey @jsolly, thanks for the suggestion!

There isn’t an Edit button for custom servers yet, but you can re-point them in place today. Ask your bot to add each server again using exactly the same server name it was registered under, with the new command/args (and the env values it needs). That updates the existing server instead of creating a new one, so its custom instructions stay as they are.

Please don’t uninstall first. Uninstalling is what clears the instructions. Once all four point at your mcp-wrappers folder, restart MCP and they should survive the next computer rebuild.