Skip to main content
Accelerate your development workflow by connecting AI agents and LLMs directly to the Auth0 knowledge base. Get context-aware answers, code samples, and API references with links to official documentation. To help your AI tools index and search for the information you need, Auth0 provides:
  • LLM context files (llms.txt): Structured Markdown files for bulk ingestion.
  • Auth0 Docs MCP Server: Hosted MCP Server for AI agents to dynamically query the knowledge base.

​
LLM context files

Use LLM context files to help LLMs understand and efficiently ingest the entire Auth0 site directory.
NameURLDescription
llms.txthttps://auth0.com/llms.txtConcise summaries of all articles; best for quick context.
llms-full.txthttps://auth0.com/docs/llms-full.txtFull content of all articles; best for deep indexing.

​
Auth0 Docs MCP Server

Connect your AI tools to the Auth0 Docs Model Context Protocol (MCP) Server for real-time access to the most up-to-date documentation on Auth0. The Auth0 Docs MCP Server exposes the SearchAuth0Docs tool, which enables AI agents to search the Auth0 knowledge base and return contextual content with relevant links to product documentation. The Auth0 Docs MCP Server has the following endpoint metadata: 
Server Name: Auth0 Docs
Server URL: https://auth0.com/docs/mcp
Transport Type: HTTP
Learn how to connect your AI tools to the Auth0 Docs MCP Server by following our integration guides.
To connect ChatGPT to the Auth0 Docs MCP Server:
  1. Navigate to Settings > Connectors.
  2. Select Create and provide the metadata for your MCP server:
    • Connector Name: Auth0 Docs MCP Server
    • Description: Indexes and searches the Auth0 knowledge base
    • Connector URL: https://auth0.com/docs/mcp
  3. Select Create.
If successful, the Auth0 Docs MCP Server should appear as an installed MCP server. To learn more, read OpenAI’s Connect from ChatGPT documentation.

​
Sample prompts

AI tools can make mistakes. Always review responses by referencing the provided documentation links and AI-generated code for accuracy before deploying.
Use the following sample prompts with your AI tools to leverage Auth0 to secure your identity workflow.

​
Setup

  • How do I customize the consent prompt to render rich authorization requests in a web browser?
  • Fetch me instructions on how to set up asynchronous authorization with the Auth0 Guardian app in my mobile application.
  • How do I implement refresh token rotation in a Next.js app? Show me the configuration steps and a code example.

​
Connections and integrations

  • I want to restrict access to this app to users who are members of a specific GitHub Organization. Use the Auth0 Docs MCP Server to find how to configure the GitHub Enterprise Connection and write an Auth0 Action that checks the user’s GitHub org membership during login, denying access if they aren’t a member.
  • Configure a Slack Social Connection. Use the Auth0 Docs MCP Server to find the correct way to map Slack’s team_id onto the user’s ID token. Then, update my local user interface to include this slack_team_id field.
  • How do I integrate Auth0 into an existing Vercel project?

​
AI agents and MCP servers

  • Add a tool call to my AI agent that can access the user’s Google calendar and answer questions about their schedule and meetings. Use the Auth0 Docs MCP Server for instructions on using Auth0 to secure login and implementing the tool call to the user’s Google calendar.
  • Act as a security engineer. Use the Auth0 Docs MCP Server to find the guide on Authorization for Your MCP Server. Update my current server configuration to require OAuth 2.1 for all incoming connections and verify that it uses the Resource Parameter Compatibility Profile for access tokens.
  • Examine my current tool definitions in server.py. Use the Auth0 Docs MCP Server to verify whether my implementation of Custom Token Exchange complies with RFC 8693. If you find any discrepancies where user context might be leaked, suggest a fix and provide the updated code.

​
Troubleshooting

  • Help me troubleshoot a refresh token doesn’t exist error when using the refresh token exchange. Use the Token Vault setup instructions as context.
  • The logout button isn’t clearing the session on the Auth0 side. Search the documentation for the correct Federated Logout URL structure and update my logout handler to use it.
  • My login flow is failing with a 401 Unauthorized error. Use the Auth0 Docs MCP Server to look up common causes for this error with the auth0-node SDK and check my .env and client initialization for mismatches.