Claude Code MCP

by Anthropic

Anthropic shipped the official Claude Code MCP server. It is the missing piece for any team that loved Claude Code's file, git, and bash tooling but wanted to use it from inside a different agent.If you run Cursor, Windsurf, or any custom MCP-compatible agent, this server lets you wire in Claude Code's full toolset as first-class agent capabilities. No more rebuilding what Anthropic already shipped.What It Actually ExposesThe server exposes Claude Code's complete tool layer as MCP tools. Everything the Claude Code CLI uses internally is now callable from any MCP client:File operations — read, write, edit, glob, search across a workspace with proper .gitignore handling.Git operations — status, diff, log, branch, commit, push (with the same safety guardrails the CLI enforces).Bash execution — run shell commands with the same workspace-scoped permissions Claude Code uses.Web search — fetch and reason about web content during a task.Workspace context — project structure, recent changes, and file-tree summaries available as MCP resources.The whole point is that Anthropic is no longer keeping Claude Code's internals proprietary to the CLI. Any agent that speaks MCP gets the same tools.Why This MattersUntil this release, if you wanted Claude Code's file-and-git tooling inside Cursor, you reimplemented it. Cursor wrote its own. Windsurf wrote its own. Cline wrote its own. Each implementation was 70% of Claude Code's quality at best, and each agent had a different bug surface.This MCP server consolidates the toolset. The same code that ships in Claude Code now runs as an MCP server. Your Cursor agent gets Claude Code's actual file edit logic. Your custom orchestrator gets Claude Code's actual git diff handling. The fragmentation ends here.The strategic move is even more interesting: Anthropic is treating Claude Code as a tool layer, not a closed product. You can use it with any model — Anthropic models, OpenAI models, open-weight models. The MCP server does not require Claude API access; it requires an MCP client that wants the tools.Install and ConfigureStandard MCP server install. Clone the repo or install via npm, then point your MCP client at the stdio binary. Cursor, Windsurf, and Claude Desktop all auto-discover the new tools on the next session. The README has a 5-minute setup with copy-paste configs for the major clients.For HTTP transport (remote hosting), the server supports MCP v2.1's authenticated streaming endpoint. That makes it usable for shared team agents where the MCP server runs on internal infrastructure.Where It Falls ShortTwo caveats. First, the bash and git tools have the same destructive-action guardrails Claude Code enforces — confirmation prompts on rm, force pushes, branch deletions. That is correct behavior, but if your client cannot show prompts, those operations fail safely instead of executing. Read the docs before automating anything destructive.Second, the server is workspace-scoped. It expects to run in a specific project directory and inherits that project's permissions. For multi-project agents, you spin up multiple server instances — one per workspace.Who Should Install ItInstall Claude Code MCP if you use any MCP-compatible coding agent and you want Anthropic's actual tool implementations instead of a third-party reimplementation. That includes Cursor, Windsurf, Claude Desktop, Cline, and any custom agent built on the MCP standard.Skip it only if you exclusively use the Claude Code CLI itself — in that case, the tools are already inside the CLI and the MCP server adds nothing.Related ResourcesArticle: GPT-5.5 just launched — the new model that pairs cleanly with Claude Code MCP for cross-vendor agent stacks.Tool: Gemini Enterprise Agents — pair with Claude Code MCP to add Anthropic's tooling to a Google-hosted agent.Repo: Microsoft Magentic-One — wire Claude Code MCP into Magentic-One's Coder specialist for richer code edits.Skill: Anthropic Data Analysis Skills — structured skills that compose with Claude Code MCP's file and bash tools.