A plugin can now carry a server-issued id in a file next to it, tying it to a server record.
What's wrong with this entry?
The loader now reads a JSON file sitting next to a plugin and accepts a server_plugin_id from it, letting a plugin be tied back to a server record.
- The id must match
plugin_followed by up to 64 alphanumeric characters. - A sidecar that is not valid JSON, is not an object, or has a missing or malformed id is logged and ignored, and the plugin still loads.
- Read whenever the sidecar exists; nothing gates it.
server_plugin_id
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
"__proto__" rejected as an MCP server name
Both mention server
-
v2.1.219
SDK init message reports skipped MCP server configs
Both mention server
-
v2.1.221
New MCP policy-predicate telemetry for allowedMcpServers matching
Both mention server