Use FlyWP Docs with AI Agents and MCP

The FlyWP documentation is published in formats that AI agents read well. An assistant such as Claude, ChatGPT, Cursor or GitHub Copilot can then answer questions about FlyWP from the current docs instead of from memory.

What's available

Address	What it contains
https://flywp.com/docs/llms.txt	An index of every documentation page, grouped by section, in the llms.txt format.
https://flywp.com/llms-full.txt	The full text of the documentation in a single Markdown file.
Any page address ending in .md	That page as Markdown. For example, /docs/site/backups.md is the Markdown version of Backup and Restore.

Every documentation page links to its Markdown version at the bottom (View as Markdown) and announces it in its HTML <head>, so crawlers can find it too.

Give an assistant the docs

If your assistant can read web pages, paste one of these into the chat along with your question:

• The .md address of the page you need, for a focused answer.
• https://flywp.com/docs/llms.txt, to let the assistant pick the relevant pages itself.
• https://flywp.com/llms-full.txt, to give it the whole documentation at once.

Connect the docs over MCP

The Model Context Protocol (MCP) lets an agent call tools that fetch documentation when it needs it. FlyWP's llms.txt works with mcpdoc, an open-source MCP server for any llms.txt file. It runs through uv, so install uv first. The commands below pin mcp<2, the MCP library version mcpdoc is built for.

Claude Code

claude mcp add flywp-docs -- uvx --from mcpdoc --with "mcp<2" mcpdoc --urls "FlyWP:https://flywp.com/docs/llms.txt" --transport stdio

Cursor, Claude Desktop and other MCP clients

Add this server to the client's MCP configuration file, such as .cursor/mcp.json or claude_desktop_config.json:

{
  "mcpServers": {
    "flywp-docs": {
      "command": "uvx",
      "args": ["--from", "mcpdoc", "--with", "mcp<2", "mcpdoc", "--urls", "FlyWP:https://flywp.com/docs/llms.txt", "--transport", "stdio"]
    }
  }
}

The server gives your agent two tools: list_doc_sources, which returns the FlyWP index, and fetch_docs, which reads any page the index links to. Then ask, for example: “Using the FlyWP docs, how do I restore a site from a backup?”