> ## Documentation Index
> Fetch the complete documentation index at: https://developers.authlete.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> ### Authlete versions
> Authlete 3.0 is the current version. Unless the user says they use another version, answer for Authlete 3.0 using the 3.x documentation.
> Documentation for Authlete 2.x (pages under `/v2/` and `/ja/v2/`) is for the legacy version. Refer to it only when the user is on Authlete 2.x.
>
> ### Authlete architecture
> Authlete is a backend engine for OAuth 2.0 and OpenID Connect processing. End users and client applications do not call it directly; the service provider's authorization server and API server call Authlete's APIs. Authlete handles protocol processing and token, client, and service management, while the service provider owns the OAuth/OIDC endpoints and user authentication.
> See [Architecture](https://developers.authlete.com/get-started/introduction-to-authlete/architecture.md).
>
> ### Concepts
> If the user is new to Authlete, read these pages first:
> - [Request and Response](https://developers.authlete.com/get-started/concepts/request-and-response.md): Core API requests pass the client's request parameters as-is, and responses return `resultCode`, `action`, and `responseContent`.
> - [Action Handling](https://developers.authlete.com/get-started/concepts/action-handling.md): Branch on `action`, never on `resultCode`, and map each action to the HTTP response your server returns.
> - [Two-Step API Calls](https://developers.authlete.com/get-started/concepts/two-step-api-calls.md): Actions such as `INTERACTION` are completed with a second call (`/auth/authorization/issue` or `/auth/authorization/fail`) linked by a `ticket`.
> - [Management API Overview](https://developers.authlete.com/get-started/concepts/overview.md): The Management API configures services, manages clients, and operates issued tokens, separately from the protocol flows handled by the Core API.
> - [API Authentication](https://developers.authlete.com/get-started/concepts/authentication.md): Authlete APIs use bearer tokens: a Service Access Token (one service) or an Organization Token (the whole organization).

# AI Agent Integration (llms.txt / MCP)

> Explains how to load the Authlete documentation into AI coding tools through llms.txt, Markdown pages, and the MCP server. No authentication or sign-up is required.

This documentation site is also published in formats that AI coding tools can read directly: [llms.txt](https://llmstxt.org/), a Markdown version of each page, and an [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server. With these formats, your tools can search and read API specifications, settings, and implementation guides. No authentication or prior sign-up is required.

<Note>
  You can use these formats to check specifications while implementing, and also to investigate errors or confirm behavior after release.
</Note>

## Loading the documentation by URL

To give your AI agent the documentation, pass it one of the following URLs. No tool-side setup is needed.

| Purpose | URL |
| - | - |
| List of all pages | `https://developers.authlete.com/llms.txt` |
| Full text of all pages in one file | `https://developers.authlete.com/llms-full.txt` |
| A single page as Markdown (example: Action Handling) | `https://developers.authlete.com/get-started/concepts/action-handling.md` |

* `llms.txt` links to separate indexes for English and Japanese, and for 3.x and 2.x.
* `llms-full.txt` contains the English 3.x pages only. Its size is about 2.6 MB. For Japanese or 2.x pages, follow the indexes in `llms.txt` and read the pages you need.
* Appending `.md` to a page URL returns the Markdown version of the page. Japanese pages have `/ja/` at the start of the path, for example `https://developers.authlete.com/ja/get-started/concepts/action-handling.md`.

## Page menu actions

The menu next to **Copy page** at the top of each page provides the following actions.

| Action | Description |
| - | - |
| **Copy page** | Copies the page as Markdown |
| **View as Markdown** | Opens the page as Markdown |
| **Open in ChatGPT** / **Open in Claude** | Starts a conversation about the page |
| **Copy MCP Server** | Copies the MCP server URL |
| **Connect to Cursor** | Installs the MCP server in Cursor |

## Connecting to the MCP server

If your tool supports MCP, register the MCP server endpoint `https://developers.authlete.com/mcp`. The tool can then search and read the documentation directly.

```text theme={null}
https://developers.authlete.com/mcp
```

<Warning>
  The MCP server also contains the Authlete 2.x documentation. If `version` is not specified, search results can include 2.x pages. Tell your AI agent which Authlete version you use, and have it specify `version` in `search_authlete_documentation` (`3.x` for Authlete 3.0).
</Warning>

The transport is HTTP. No authentication is required. The configuration format depends on the tool; see your tool's documentation for details. The following examples register the server as `authlete-docs`.

<CodeGroup>
  ```bash Claude Code theme={null}
  claude mcp add --transport http authlete-docs https://developers.authlete.com/mcp
  ```

  ```json Cursor (.cursor/mcp.json) theme={null}
  {
    "mcpServers": {
      "authlete-docs": {
        "url": "https://developers.authlete.com/mcp"
      }
    }
  }
  ```

  ```json VS Code (.vscode/mcp.json) theme={null}
  {
    "servers": {
      "authlete-docs": {
        "type": "http",
        "url": "https://developers.authlete.com/mcp"
      }
    }
  }
  ```

  ```toml Codex (~/.codex/config.toml) theme={null}
  [mcp_servers.authlete-docs]
  url = "https://developers.authlete.com/mcp"
  ```
</CodeGroup>

If you commit a project-level configuration file, such as `.cursor/mcp.json` or `.vscode/mcp.json`, to your repository, everyone on the project gets the same setup.

### MCP server tools

The MCP server provides the following three tools.

| Tool | Description |
| - | - |
| `search_authlete_documentation` | Searches the documentation. `language` (`en` by default, `ja` for Japanese) and `version` (`3.x` or `2.x`) narrow the results. |
| `query_docs_filesystem_authlete_documentation` | Reads pages and the OpenAPI specification with read-only commands such as `rg`, `cat`, and `tree`. |
| `submit_feedback` | Reports a documentation page that is incorrect, outdated, or incomplete to the Authlete documentation team. |

## Using AI agent answers

* Authlete 3.0 is the current version. Documentation for Authlete 2.x (pages under `/v2/`) is for users of the legacy version.
* The documentation is updated regularly. Do not rely on an AI agent's answer as is; confirm it on the relevant page.
* If you cannot find what you need in the documentation, do not guess. [Contact us](https://www.authlete.com/contact/).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.