{"version":"2.1.317","anchor":"plugin-mcp-server-specs-can-be-loaded-from-a-bundled-mcp-ser","canonical_anchor":"plugin-mcp-server-specs-can-be-loaded-from-a-bundled-mcp-ser","heading":"Plugins can point their MCP server list at a bundled resource","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plugin-mcp-server-specs-can-be-loaded-from-a-bundled-mcp-ser","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Plugins can point their MCP server list at a bundled resource\n\nA plugin's `.mcp.json` or `mcpServers` entry can now refer to a resource of kind `mcp-servers` instead of a file\n\n**Unclear.** How a plugin provides an `mcp-servers` resource is not described.\n\n**What**\n\nMCP servers are outside services that give Claude extra tools, and plugins can list the ones they bring. A plugin's `.mcp.json` or `mcpServers` text entry can now refer to a resource of kind `mcp-servers`. The normal file loader skips entries like these.\n\n**Why**\n\nPlugins may be able to ship their MCP server definitions as a bundled resource rather than a separate file.\n\n- Area: Plugins\n- Names: `mcpServers`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}