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

# Using FlowX docs with AI assistants

> Connect this documentation to Claude, ChatGPT, Cursor, or any MCP client so your assistant answers from the current docs instead of guessing.

This documentation is built to be read by AI assistants as well as people. You can connect it to your assistant so that answers come from the current FlowX.AI documentation rather than from whatever the model happened to memorize during training.

***

## Why connect the docs

Language models are trained at a point in time and FlowX.AI ships monthly. An assistant answering from memory will confidently describe features that changed, node types that were renamed, and configuration keys that never existed.

Connecting the docs changes where the answer comes from. The assistant searches the live documentation, reads the actual page, and cites it back to you.

<Tip>
  This matters most for version-sensitive questions. Availability, environment variables, and node configuration differ between releases, and those are exactly the details a model is most likely to get wrong from memory.
</Tip>

***

## Connect from any page

Every page on this site has a contextual menu at the top with the connection options built in.

<Steps>
  <Step title="Open the menu on any documentation page">
    Use the control at the top of the page, beside the page title.
  </Step>

  <Step title="Pick your assistant or editor">
    Options include Claude, ChatGPT, Perplexity, Cursor, and VS Code. Each one hands the current page, or the connection details, straight to that tool.
  </Step>

  <Step title="Ask your question">
    The assistant now has the documentation available and will search it rather than answering from memory.
  </Step>
</Steps>

The same menu also offers **Copy page** and **View as Markdown** if you would rather paste content in manually.

***

## Connect manually over MCP

For any client that supports the Model Context Protocol, connect to this endpoint over HTTP:

```
https://docs.flowx.ai/mcp
```

In Claude Code, add it with:

```bash theme={"dark"}
claude mcp add --transport http flowx-docs https://docs.flowx.ai/mcp
```

Other clients store MCP server definitions in their own configuration file, and most accept a remote HTTP server as a name and URL pair. Use the contextual menu on any page to get the exact configuration for Cursor and VS Code, since it generates the correct file and format for you.

### What the assistant can do once connected

The docs server exposes three tools.

| Tool                         | What it does                                                                                                     |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| `search_docs`                | Searches the documentation and returns matching content with direct links to the source page                     |
| `query_docs_filesystem_docs` | Reads and searches the documentation as a read-only file tree, for exact keyword matching or reading a full page |
| `submit_feedback`            | Reports a documentation problem to the docs team, tied to the page path it concerns                              |

<Info>
  `query_docs_filesystem_docs` runs against a sandboxed, in-memory copy of the documentation. It is not a shell, and nothing runs on your machine, the docs server, or any FlowX environment.
</Info>

<Tip>
  `submit_feedback` is worth knowing about. If your assistant gives you an answer that turns out to be wrong because a page is outdated or incomplete, you can ask it to report that, and the correction reaches the docs team with the page path attached.
</Tip>

***

## Bulk formats

If you are building a tool, seeding a knowledge base, or feeding a long-context model, three formats are published.

<CardGroup cols={2}>
  <Card title="Page as Markdown" icon="file-lines">
    Append `.md` to any documentation URL to get that single page as clean Markdown.
  </Card>

  <Card title="llms.txt" icon="list">
    An index of the documentation with a one-line description per page. Good for routing and discovery.
  </Card>

  <Card title="llms-full.txt" icon="database">
    The complete documentation as a single Markdown file. Large, and intended for ingestion rather than browsing.
  </Card>

  <Card title="Sitemap" icon="sitemap">
    `https://docs.flowx.ai/sitemap.xml` lists every indexed page URL.
  </Card>
</CardGroup>

Example, fetching one page as Markdown:

```bash theme={"dark"}
curl https://docs.flowx.ai/5.1/docs/introduction.md
```

***

## Working across versions

FlowX.AI documentation is published as one tree per release family, and the version is part of every URL. When you ask a version-specific question, name the release in your prompt so the assistant searches and cites the right tree.

<Warning>
  Ask for the version you are running, and check the version in the links your assistant returns. A question asked without a version can be answered from any tree, including newer releases whose features are not present in 5.1, and release families that have reached end of life.
</Warning>

***

## Related resources

<CardGroup cols={2}>
  <Card title="Build your first process" icon="diagram-project" href="/5.1/docs/getting-started/building-your-first-proc">
    Start here if you are new to the platform
  </Card>

  <Card title="Introduction" icon="book" href="/5.1/docs/introduction">
    What FlowX.AI is and how the platform fits together
  </Card>
</CardGroup>


## Related topics

- [FlowX.AI architecture](/5.1/docs/platform-overview/flowx-architecture.md)
- [FlowX.AI 5.3.0 Release Notes](/release-notes/v5.x/v5.3.0-december-2025/v5.3.0-december-2025.md)
- [FlowX.AI documentation](/5.1/docs/introduction.md)
- [FlowX.AI Scheduler](/5.1/docs/platform-deep-dive/core-extensions/scheduler.md)
- [FlowX.AI Designer](/5.1/docs/flowx-designer/overview.md)