One Config File, Every Team Member: Deploy Shared MCP Servers Org-Wide in Claude Code 2.1.259

Claude Code 2.1.259 adds managedMcpServers — a managed setting that pushes HTTP/SSE MCP servers to every user in your org without per-machine .mcp.json setup.

When you run Claude Code across a team, each engineer configures their own .mcp.json. Add a new internal tool — a knowledge base connector, a database MCP, a CI runner — and every engineer needs to update their config manually. managedMcpServers removes that friction.

How to configure it:

In your org's managed settings file (deployed via MDM, a dotfile repo, or the Claude console for Enterprise users), add:

{
  "managedMcpServers": {
    "company-wiki": {
      "url": "https://mcp.internal.example.com/wiki/sse",
      "type": "sse"
    },
    "jira-connector": {
      "url": "https://mcp.internal.example.com/jira",
      "type": "http"
    }
  }
}

Every Claude Code session on a managed machine sees these servers immediately — no .mcp.json edit, no restart. The entry shape is identical to .mcp.json.

One hard constraint: managedMcpServers accepts HTTP/SSE endpoints only. Entries that name a command to run are silently skipped. If your MCP servers are stdio/command-based, you need an HTTP adapter (a small FastAPI wrapper over the stdio session is the common pattern) or you keep per-user setup for those.

When to use this vs. .mcp.json: Use managed settings for shared org services (internal knowledge bases, company-specific integrations, compliance tools). Use per-project .mcp.json for tools that vary by repo. User-level ~/.mcp.json still handles personal one-off servers.

Also new in 2.1.259: --permission-prompts none for unattended headless environments — anything that would prompt is auto-denied, useful for CI runs where a hanging prompt would silently block the job.

Sources: Claude Code changelog v2.1.259 — code.claude.com · Install and Configure MCP Servers in Claude Code — systemprompt.io · How to Add an MCP Server to Claude Code — TrueFoundry