{"version":"2.1.312","anchor":"plugin-mcp-configs-track-whether-the-endpoint-is-templated","canonical_anchor":"plugin-mcp-configs-track-whether-the-endpoint-is-templated","heading":"Plugin MCP server configs now carry official-source and templated-endpoint markers","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/plugin-mcp-configs-track-whether-the-endpoint-is-templated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Plugin MCP server configs now carry official-source and templated-endpoint markers\n\nPlugin MCP server configs now record whether an official source vouched for them and whether their endpoint uses substituted variables\n\n**Unclear.** It is not clear whether anything acts on these new records yet.\n\n**What**\n\nPlugins are add-ons for Claude Code, and some bring MCP servers, outside programs that give Claude extra tools. The settings Claude Code builds for these plugin servers now carry extra markers.\n\n- `pluginOfficialSourceVouched`: the step that builds plugin configs takes a new flag. When it is set, each config gets `pluginOfficialSourceVouched: true`. When it is not, the property is removed.\n\n- `pluginEndpointTemplated`: recorded when the server's command, args, env or URL use a variable that gets filled in.\n\n- Needs user input: a new check treats a config as needing your input if it has `user_config` or uses the `HOME`, `DESKTOP`, `DOCUMENTS` or `DOWNLOADS` variables.\n\n**Why**\n\nThe members do not show these markers changing what any plugin server is allowed to do yet. In practice, Claude Code can now tell whether a plugin server came from an official source, whether its endpoint is filled in from variables, and whether it depends on your own settings or folders.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}