{"version":"2.1.274","anchor":"mcp-server-source-attribution-sdk-plugin-config-scope","canonical_anchor":"mcp-server-source-attribution-sdk-plugin-config-scope","heading":"MCP server 'source' attribution (sdk \/ plugin \/ config scope) added to schemas","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-server-source-attribution-sdk-plugin-config-scope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### MCP server 'source' attribution (sdk \/ plugin \/ config scope) added to schemas\n\nMCP server status now reports where each server definition came from\n\n**What**\n\nMCP (Model Context Protocol) server status information now includes an optional `source` field, showing whether a given server was registered in-process via the SDK, came from a plugin, or came from a config scope such as user, project, local, dynamic, managed, enterprise, claudeai, or agent. This is computed internally from the server's metadata and exposed on `mcp_servers` status entries.\n\n**Why**\n\nThis lets you (or tools reading this status) tell where an MCP server definition actually originated, rather than relying on its name alone, which is useful when the same server name could be defined in more than one place.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}