{"version":"2.1.242","anchor":"claude-ai-mcp-servers-carry-an-enterprise-managed-marker","canonical_anchor":"claude-ai-mcp-servers-carry-an-enterprise-managed-marker","heading":"claude.ai MCP servers carry an enterprise-managed marker","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/claude-ai-mcp-servers-carry-an-enterprise-managed-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### claude.ai MCP servers carry an enterprise-managed marker\n\nMCP servers from claude.ai can be flagged enterprise-managed, driving the \"managed by your organization\" label.\n\n**What**\n\nMCP server configurations served by claude.ai now include an `enterpriseManaged` boolean, populated from the API's `enterprise_managed` field, which drives the \"managed by your organization\" label.\n\n**Details**\n\n- Present whenever the server sends the field; there is no flag.\n- One config-writing path deletes it before saving, alongside `eligible`, `ineligibleReason` and `discoverSupport`, so the server-derived marker is not persisted into local config.\n\n**Evidence**\n\n`enterpriseManaged`, `enterpriseManaged: m.enterprise_managed`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}