Once you've added a few MCP servers, you need to review them, inspect one in detail, and remove the ones you no longer use. Three subcommands and one in-session menu cover all of it.
List what you have
Start with an overview:
claude mcp list
This shows every server registered for your current context, across the scopes that apply. It's the quickest way to confirm a server you just added is actually there.
Inspect one server
When you want the details of a single server, ask for it by name:
claude mcp get notion
This prints how that server is configured, including its transport and how Claude Code reaches it. Use it when a server misbehaves and you want to check exactly what was registered.
Remove a server
When you're done with a server, take it out by name:
claude mcp remove notion
For a project-scoped server, this updates .mcp.json, so commit the change to share it with your team.
Manage from inside a session
While you're working in Claude Code, type /mcp to open the servers menu. It shows connection status for each server and is where you sign in to a server that needs authentication. It's the fastest check when a server's tools aren't showing up mid-task.
A simple routine
Run claude mcp list after any change, use claude mcp get when something looks off, and claude mcp remove to keep the set tidy. Keeping your server list small and current means fewer surprises and a cleaner set of tools for Claude to choose from.
Comments
Be the first to comment.