[DOCS] Remove outdated references to MCP server @-mentions for toggling status

Resolved 💬 3 comments Opened Jan 19, 2026 by coygeek Closed Feb 27, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

Section/Topic

  • MCP server management and Quick commands sections.

Current Documentation

The documentation at https://code.claude.com/docs/en/mcp currently includes the instruction:

"Enable/disable MCP servers by @mentioning, or in /mcp."

Additionally, older sections of the feature documentation may still suggest that @-mentioning an MCP server is a valid way to toggle its enabled/disabled state.

What's Wrong or Missing?

According to the Claude Code Changelog for version 2.1.6:

"Removed ability to @-mention MCP servers to enable/disable — use /mcp enable <name> instead."

The existing documentation encourages a workflow that has been explicitly removed from the product, leading to user confusion when the @-mention UI only shows file suggestions or resources rather than server toggles.

Suggested Improvement

Update all references to MCP server management to reflect the new command-based workflow.

Suggested text for https://code.claude.com/docs/en/mcp:**
"Manage your MCP servers using the following commands:

  • /mcp: Open the interactive management menu.
  • /mcp enable <name>: Enable a specific server.
  • /mcp disable <name>: Disable a specific server.
  • Note: @-mentioning servers to toggle status is no longer supported."

Suggested update for https://code.claude.com/docs/en/interactive-mode:**
Ensure the @ symbol is only described as a trigger for file, directory, or resource mentions, removing any mention of server status toggling.

Impact

High - Prevents users from using a feature

Additional Context

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗