Back to Claude Code hub
BEGINNERsnapshot-basedVerified 2026-03-31core

MCP and Plugins

How Claude Code connects to external servers, tools, and resources

A map of MCP connection management, plugin-facing flows, and how external capabilities become part of the Claude Code experience.

MCP is treated as a managed capability layer

Claude Code does not just list MCP servers. It manages connection state, exposes reconnect and toggle behavior, and treats MCP clients as first-class runtime capabilities.

That makes MCP closer to a capability graph than a simple settings page.

  • Servers can be reconnected and toggled.
  • Connections can expose tools, commands, and resources.
  • The app distinguishes MCP management from generic browsing.

The command surface exposes operational controls

The `/mcp` command family is not only descriptive. It actively supports reconnect, enable, and disable behavior for servers.

That reflects how operational MCP is inside Claude Code: integrations are meant to be managed during real work, not only configured once.

Why this matters for the directory

For `claudecode.directory`, MCP content should not live as isolated resource cards. Users need concept pages that explain where MCP fits in the Claude Code mental model.

The best directory experience links protocol docs, concrete servers, and workflow guidance together.

Learn next

These guides are adjacent to the current topic and make the learning path easier to follow.