Bricks Builder MCP v1.8.0
fix: MCP protocol compliance for Claude.ai web (v1.8.0)
Three spec violations prevented Claude.ai (and other strict MCP clients)
from loading tools after a successful initialize handshake:
-
notifications/initialized returned HTTP 204 — spec (§6.1) requires 202.
Claude.ai checks for 202 before proceeding to tools/list; getting 204
caused it to abort the session, leaving tools never registered. -
DELETE /mcp returned 404 — spec (§6.4) requires the endpoint to accept
DELETE for session termination. Added graceful 200 acknowledgement. -
initialize response had no Mcp-Session-Id header — spec says servers
SHOULD include it. Now generated as a random 32-char hex token per
request (plugin remains stateless; the ID is not tracked server-side).
Also added: ping method handler, and a catch-all 202 for any future
unknown notifications so sessions are never broken by unrecognised methods.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com