{"version":"2.1.242","anchor":"mcp-servers-managed-by-your-organization-are-labelled","canonical_anchor":"mcp-servers-managed-by-your-organization-are-labelled","heading":"MCP servers managed by your organization are labelled","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/mcp-servers-managed-by-your-organization-are-labelled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### MCP servers managed by your organization are labelled\n\nMCP servers your organization provisioned are now labelled as managed in the list and detail views.\n\n**What**\n\nMCP connections provisioned by your organization are now marked in the UI: the detail view shows a \"Managed:\" row reading \"by your organization\", and the list line gets a ` \u00b7 managed` suffix.\n\n**Details**\n\n- Shown only when the connection goes through the claude.ai proxy transport, is in the `claudeai` scope, and its config carries the enterprise-managed marker.\n- Not behind a feature flag; it is purely a condition on the server's own configuration.\n\n**Evidence**\n\n`by your organization`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}