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

# Use Purpify docs with AI

> Connect an AI assistant to Purpify documentation through Markdown, llms.txt, llms-full.txt, or Mintlify MCP.

Mintlify exposes Purpify documentation in formats designed for AI retrieval. Use the smallest source that fits your assistant.

## Choose an access method

| Method          | Best for                                                     | URL pattern                                |
| --------------- | ------------------------------------------------------------ | ------------------------------------------ |
| Page Markdown   | Answering a question about one page                          | Open a page's **View as Markdown** action. |
| `llms.txt`      | Discovering pages before retrieval                           | `https://YOUR-DOCS-DOMAIN/llms.txt`        |
| `llms-full.txt` | Loading all public docs into a small knowledge base          | `https://YOUR-DOCS-DOMAIN/llms-full.txt`   |
| MCP             | Letting an AI search and retrieve the current docs on demand | `https://YOUR-DOCS-DOMAIN/mcp`             |

Replace `YOUR-DOCS-DOMAIN` with the production Purpify docs domain after deployment.

## Recommended setup

Use MCP when your AI platform supports it. MCP lets the assistant search current documentation instead of placing every page in every prompt.

Use `llms-full.txt` for a platform that can ingest a single remote text source but cannot use MCP. Refresh the source after documentation changes so the assistant does not answer from an old copy.

## Retrieval instructions for your assistant

Give your assistant rules like these:

```text theme={"dark"}
Answer Purpify questions only from the connected Purpify documentation.
Prefer a page that directly matches the user's task or error.
Distinguish Minecraft Bedrock Edition from Java Edition.
Cite the source page used for each answer.
Do not invent panel labels, URLs, limits, defaults, or supported versions.
When the docs do not contain an answer, say what information is missing and direct the user to Purpify support.
Never request a password or access token.
```

## Test the connection

Ask the connected assistant:

* "How do I upload an existing Bedrock world?"
* "What should I check when nobody can connect?"
* "What files identify a Bedrock world folder?"
* "When should I stop the server before editing files?"

A good answer cites the relevant Purpify page, follows its sequence, and does not add unsupported product details.

## Keep answers accurate

* Update docs and AI sources together.
* Keep one canonical page for each task.
* Add exact errors and supported values after verifying them.
* Review questions that produce no citation or the wrong citation.
* Retest common questions after navigation or terminology changes.

<Note>
  The docs and MCP server must be public for external AI tools to retrieve them. Do not publish private server addresses, account details, or credentials in documentation.
</Note>