{"version":"2.1.305","anchor":"mcp-plugin-server-env-now-carries-pluginid-built-in-claude","canonical_anchor":"mcp-plugin-server-env-now-carries-pluginid-built-in-claude","heading":"Plugin MCP servers are told which plugin they come from","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/mcp-plugin-server-env-now-carries-pluginid-built-in-claude","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Plugin MCP servers are told which plugin they come from\n\nMCP servers started from a plugin now get the plugin's name, and the built-in Claude Test server is marked as for a person only\n\n**Unclear.** What being marked as for a person only restricts for the Claude Test server.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools, and some come from plugins. When Claude Code starts one from a plugin, it now passes along which plugin it came from.\n\nA built-in server listed as \"Claude Test (built into Claude Code)\" is now marked as for a person only.\n\n**Why**\n\nClaude Test is a server built into Claude Code that gets its own special treatment.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}