{"version":"2.1.299","anchor":"plugin-seating-managed-mcp-server-file-also-seats-the-plugi","canonical_anchor":"plugin-seating-managed-mcp-server-file-also-seats-the-plugi","heading":"A managed MCP server file now gives a plugin top precedence for the whole session","tier":"notice","area":"Plugins","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-seating-managed-mcp-server-file-also-seats-the-plugi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### A managed MCP server file now gives a plugin top precedence for the whole session\n\nA machine with a managed MCP server file now also puts a particular plugin in the top-precedence position, and it stays there until the session ends\n\n**Unclear.** Which plugin is given the outermost position is not identified.\n\n**What**\n\nClaude Code places one plugin (an add-on package that extends Claude Code) in the outermost position on some machines. That position gives it precedence over other plugins. Before, this happened only on machines with managed settings (settings an organization controls) or for Team and Enterprise organizations. It now also happens when the machine has a managed MCP server file. MCP servers are outside programs that give Claude Code extra tools, and a managed file is one an organization sets up.\n\nOnce the plugin takes that position, it keeps it until the session (the current run of Claude Code) ends.\n\n**Why**\n\nOn machines an organization manages, this changes which plugin wins when plugins overlap. Because the position holds for the whole session, it does not switch back partway through.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}