Summary
The /add-mcp and /add-mcp-server slash commands are easy to confuse because their names are nearly identical but they perform different workflows. Warp should better disambiguate the command names, descriptions, or presentation so users can tell whether they are opening MCP settings or editing file-based MCP configuration.
Problem
A user noted that /add-mcp and /add-mcp-server sound like variants of the same command, but they currently target different MCP setup paths:
/add-mcp configures regular MCP servers directly in Warp's MCP settings and opens the settings flow./add-mcp-server is an agent skill that edits Warp's file-based MCP configuration, e.g. .mcp.json.
Because both commands use very similar naming around "add MCP server," users may select the wrong one when trying to add an MCP server. This is especially confusing now that Warp has both settings-managed MCP servers and file-based MCP configs.
Expected behavior
Users should be able to distinguish the two workflows from the slash-command menu before invoking either command. The command names, descriptions, categorization, or other UI affordances should make it clear which command opens Warp's MCP settings and which command edits file-based MCP configuration.
Actual behavior
The commands are named similarly enough that their different destinations are not obvious:
/add-mcp appears as a product slash command for adding an MCP server through settings./add-mcp-server appears as an agent skill for adding an MCP server to Warp's file-based configuration.
The distinction between "settings-managed MCP server" and "file-based MCP config" is easy to miss from the command names alone.
Reproduction steps or desired workflow
- Open the slash-command menu.
- Search for MCP-related add commands.
- Observe
/add-mcp and /add-mcp-server appearing as similarly named options.
- Try to infer which command opens MCP settings versus which command edits
.mcp.json file-based configuration.
Desired workflow: the user can confidently choose the correct MCP setup path without knowing the implementation distinction ahead of time.
Artifacts
None attached.
Warp version
v0.2026.04.30.08.57.dev_00
Operating system
macOS 26.4.1 (build 25E253)
Possible source references
app/src/search/slash_command_menu/static_commands/commands.rs: defines the static /add-mcp command with description Add new MCP server and registers it in the slash-command registry.app/src/terminal/input/slash_commands/mod.rs: executes /add-mcp by dispatching TerminalAction::OpenAddMCPPane, which opens the settings-managed MCP flow.resources/bundled/skills/add-mcp-server/SKILL.md: defines the add-mcp-server skill and describes editing global or project .mcp.json file-based MCP configuration.app/src/settings_view/ai_page.rs: MCP settings copy distinguishes managed MCP servers from file-based MCP detection, which may be relevant context for clearer command wording.
Summary
The
/add-mcpand/add-mcp-serverslash commands are easy to confuse because their names are nearly identical but they perform different workflows. Warp should better disambiguate the command names, descriptions, or presentation so users can tell whether they are opening MCP settings or editing file-based MCP configuration.Problem
A user noted that
/add-mcpand/add-mcp-serversound like variants of the same command, but they currently target different MCP setup paths:/add-mcpconfigures regular MCP servers directly in Warp's MCP settings and opens the settings flow./add-mcp-serveris an agent skill that edits Warp's file-based MCP configuration, e.g..mcp.json.Because both commands use very similar naming around "add MCP server," users may select the wrong one when trying to add an MCP server. This is especially confusing now that Warp has both settings-managed MCP servers and file-based MCP configs.
Expected behavior
Users should be able to distinguish the two workflows from the slash-command menu before invoking either command. The command names, descriptions, categorization, or other UI affordances should make it clear which command opens Warp's MCP settings and which command edits file-based MCP configuration.
Actual behavior
The commands are named similarly enough that their different destinations are not obvious:
/add-mcpappears as a product slash command for adding an MCP server through settings./add-mcp-serverappears as an agent skill for adding an MCP server to Warp's file-based configuration.The distinction between "settings-managed MCP server" and "file-based MCP config" is easy to miss from the command names alone.
Reproduction steps or desired workflow
/add-mcpand/add-mcp-serverappearing as similarly named options..mcp.jsonfile-based configuration.Desired workflow: the user can confidently choose the correct MCP setup path without knowing the implementation distinction ahead of time.
Artifacts
None attached.
Warp version
v0.2026.04.30.08.57.dev_00
Operating system
macOS 26.4.1 (build 25E253)
Possible source references
app/src/search/slash_command_menu/static_commands/commands.rs: defines the static/add-mcpcommand with descriptionAdd new MCP serverand registers it in the slash-command registry.app/src/terminal/input/slash_commands/mod.rs: executes/add-mcpby dispatchingTerminalAction::OpenAddMCPPane, which opens the settings-managed MCP flow.resources/bundled/skills/add-mcp-server/SKILL.md: defines theadd-mcp-serverskill and describes editing global or project.mcp.jsonfile-based MCP configuration.app/src/settings_view/ai_page.rs: MCP settings copy distinguishes managed MCP servers from file-based MCP detection, which may be relevant context for clearer command wording.