Under the hood
MCP server status now reports where each server definition came from
What
MCP (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.
Why
This 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.