docs: fix drift in ElevenLabs

[jack-arturo]

Automated docs-accuracy audit of docs/platforms/elevenlabs — first review of this page. All findings verified against the MCP sidecar source (mcp-sse-server/server.js, in the automem repo) at the SHA below.

Claim	Current state	Fix	Evidence
ElevenLabs is "the only cloud platform that can use the more secure header-based authentication"	Not true, and self-contradicted by this page's own Related Platforms list ("Claude.ai (Web) — header or URL auth"). getAuthToken() accepts Authorization: Bearer, X-API-Key/X-API-Token, or query token from any client, and docs/platforms/claude-web states Claude.ai supports both.	Say ElevenLabs supports header auth, note Claude.ai (Web) does too and ChatGPT is URL-only.	automem@8ff266e:mcp-sse-server/server.js#L896; automem-website:src/content/docs/docs/platforms/claude-web.md#L10
"Memory service unreachable (sidecar returns 502)"	The sidecar never emits 502. 502 appears only inside TRANSIENT_STATUS_CODES, the set of upstream codes it retries on. Upstream failures surface as an MCP tool error (isError: true); a missing endpoint returns 500, a missing token 401.	Heading dropped the 502; added a sentence describing what actually happens.	automem@8ff266e:mcp-sse-server/server.js#L21, #L731, #L1096
401 troubleshooting: "Test token: curl -H "Authorization: Bearer $TOKEN" .../health"	Cannot detect a bad token. The sidecar's /health route reads no auth and unconditionally res.status(200). A wrong token returns 200 exactly like a right one.	Point the token test at the AutoMem service, and state that the sidecar 401s only on a missing token — a present-but-wrong one is forwarded upstream.	automem@8ff266e:mcp-sse-server/server.js#L857, #L1058
"Agent cannot connect → 1. Verify sidecar health: curl .../health"	Misleading for the same reason: /health is 200 whenever the sidecar process is up, even with AutoMem down. The /ready route is the one that returns 503 on an unhealthy upstream.	Noted that /health is always 200, to read the upstream field, and that /ready is the failing-on-unhealthy probe.	automem@8ff266e:mcp-sse-server/server.js#L857
Anti-buffering header "Cache-Control: no-cache"	Actual value is no-cache, no-transform — no-transform is the directive that stops proxies rewriting the stream, which is the point of the bullet.	Corrected the value.	automem@8ff266e:mcp-sse-server/server.js#L1042, #L1103

Verified against: verygoodplugins/automem@8ff266e

Verified as correct, no change made: the 20-second SSE heartbeat and its exact : ping\n\n comment format; X-Accel-Buffering: no; PORT default 8080; AUTOMEM_API_URL / AUTOMEM_API_TOKEN roles (the token is a per-call fallback behind the request token); the POST /mcp and GET /mcp/sse routes; api_token as a valid URL query parameter; the one-hour SSE session-inactivity sweep; and all six tool names in the Available Memory Tools table.

Questions

• The page has no :::note[Source files] block, unlike every other platform page. The sidecar it documents lives in the automem repo at mcp-sse-server/server.js, which is easy to miss. Adding one would help, but it's an additive structural change rather than a drift fix, so I left it out — say the word and it's a one-line follow-up.
• "The sidecar is included in the AutoMem Railway one-click template" — not verifiable from the working tree (railway.json in mcp-sse-server/ exists, but template membership is external). Left as-is.

Unverified

• ElevenLabs' own 30-second idle timeout and its Agents UI field names (Server URL / Custom Header Name / Custom Header Value). These are vendor-side facts with no representation in our code; the heartbeat that compensates for the timeout is verified.

Follow-ups

None beyond the Questions above — the page came in under the five-fix cap.

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying automem-website with    Cloudflare Pages

Latest commit:	7980887
Status:	✅  Deploy successful!
Preview URL:	https://c4420c95.automem-website.pages.dev
Branch Preview URL:	https://docs-audit-platforms-elevenl.automem-website.pages.dev

View logs