Use the /mcp Command to Inspect Your MCP Servers
MCP servers can silently fail without any obvious error in your conversation. The /mcp command is the fastest way to find out what's actually connected and healthy.
/mcp
Type /mcp in any Claude Code session and you'll see a live list of all configured MCP servers, their connection state, and how many tools each one is exposing. If something shows as disconnected or errored, you can restart it right there without leaving the terminal.
# Example /mcp output
✓ postgres connected — 6 tools
✗ github error — 0 tools (authentication failed)
✓ filesystem connected — 8 tools
✓ brave-search connected — 1 tool
A server might be in an error state because:
- An API key expired or wasn't set
- The server process crashed after a dependency update
- A per-project config references a server that isn't installed globally
Once you've fixed the underlying issue (updated the key in ~/.claude/settings.json, reinstalled the package, etc.), /mcp lets you restart just that server without restarting your whole session.
/mcp is your first diagnostic stop whenever a tool you expected to work suddenly isn't there.
Log in to leave a comment.
Scaffold a custom MCP server with Claude to give it direct access to your internal APIs, dashboards, and microservices.
Use --strict-mcp-config to restrict Claude Code to only the MCP servers you explicitly provide, ignoring all other sources.
Add the Slack MCP server to let Claude post deployment updates, incident alerts, or standup summaries directly to your channels.