Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Local plugin MCP server secret moves from the web address to an Authorization header

The local HTTP MCP server for plugins now expects its secret as a Bearer token in the Authorization header instead of in the URL path

Group of 2 You'll notice Improvements
JSON All of v2.1.317
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release

What

MCP servers are outside programs that give Claude Code extra tools. A plugin's MCP server can be reached through a small local web server on your own machine, protected by a secret.

  • The plugin's MCP config no longer puts the secret in the address. The address is now just the port, plugin name and version, and the secret is sent as Authorization: Bearer <secret>.
  • The local handler now reads the secret from the authorization header as Bearer ${n.secret}, compares it with a constant-length check, and answers "not found" if it does not match. Before, it took the secret from the first part of the URL path.

Why

Addresses often end up in logs and error messages, so keeping the secret out of the URL keeps it out of those places too.

See this entry in the whole of v2.1.317 →

Feedback