llms.txt Developer Tools entry points to dead path: /docs/customize/integrations/ai-tools/auth0-mcp-server (404, no redirect)

[wallidsaydi-creator]

Summary

https://auth0.com/llms.txt — the index file Auth0 publishes specifically for AI coding agents — lists a Developer Tools entry whose target no longer exists:

## Developer Tools
AI-native developer tools for integrating Auth0.
- [Auth0 MCP Server](https://auth0.com/docs/customize/integrations/ai-tools/auth0-mcp-server)

/docs/customize/integrations/ai-tools/auth0-mcp-server returns a hard 404. The MCP Server docs moved to /docs/get-started/auth0-mcp-server/ (the repo's own content already links there — see below), but the llms.txt entry was never updated and no redirect covers the legacy path.

Repro (live, 2026-08-29)

Check	Result
GET /docs/customize/integrations/ai-tools/auth0-mcp-server (2 UAs × 2 passes, redirects followed)	404 all 4 times, final URL unchanged
GET /llms.txt, line 35	- [Auth0 MCP Server](https://auth0.com/docs/customize/integrations/ai-tools/auth0-mcp-server)
llms.txt response headers	cf-cache-status: DYNAMIC, age: 0 — fresh edge generation, not a cache artifact
Replacement target GET /docs/get-started/auth0-mcp-server	200 (also 200: /auth0-mcp-tools-reference, /getting-started-with-auth0-mcp-server)
main/config/redirects.json (5,477 entries)	0 entries match customize/integrations/ai-tools — the legacy path is not redirected anywhere

Why it matters

llms.txt exists to give AI agents a reliable map of your docs. This entry is in the Developer Tools section — the exact place an agent (or an agent-driven workflow like Cursor/Claude Code setup) looks first for MCP integration. Today that lookup lands on a 404 with no redirect, so the agent either dead-ends or improvises. Your own content already treats the new path as canonical:

• auth4genai/build-with-ai/using-ai-tools.mdx L34: …read the [Auth0 MCP Server documentation.](https://auth0.com/docs/get-started/auth0-mcp-server)
• main/docs/get-started/auth0-mcp-server.mdx — the live MCP hub (200)

Also notable: the new Lychee link-check workflow added in #1800 (c2f615a) only scans changed *.mdx files on PRs, so a stale entry in the edge-generated llms.txt is invisible to it — this class of drift won't self-heal through CI.

Suggested fix (happy to open a PR)

Two complementary options:

1. Repo-side (smallest, heals every consumer): add a redirects.json entry in the established format:

   { "source": "/docs/customize/integrations/ai-tools/auth0-mcp-server", "destination": "/docs/get-started/auth0-mcp-server" }

2. Generator-side: update the llms.txt entry to point at https://auth0.com/docs/get-started/auth0-mcp-server directly. The generator doesn't appear to live in this repo (cf-cache-status: DYNAMIC suggests edge generation), so option 1 is the fix this repo can own on its own; option 2 removes the stale link from the agent-facing index itself.

Context

I maintain agent-context hygiene for AI coding tools (stale docs / dead llms.txt links are a recurring hallucination source for agents). Recent related fixes: merged PR to cloudflare-docs fixing 27 dead links in their llms.txt hubs (cloudflare/cloudflare-docs#32985), and a maintainer-shipped fix for llms-docs-builder v1.0.0 (mensfeld/llm-docs-builder#165). If useful, I can put together a one-off drift report of the full llms.txt surface — sample of the format: https://deploy-foorge-team.vercel.app/sample-fresh-context-pack.html

Happy to open the PR with the redirects.json entry (plus the generator-side change if you can point me at where llms.txt is generated).

[wallidsaydi-creator]

PR with the redirects.json entry is up: #1808 (4-line addition, placed at the head of the existing customize/integrations cluster, destination content verified in-repo).

Also re-verified the live state this morning before opening: legacy path still 404 (2 UAs), /docs/get-started/auth0-mcp-server still 200, llms.txt L35 unchanged.