> For the complete documentation index, see [llms.txt](https://docs.fulfillmenttools.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fulfillmenttools.com/documentation/getting-started/llm-ready-docs.md).

# LLM-ready docs

Our documentation is LLM-ready. It's automatically published in AI-friendly formats for AI tools to discover, read, and use. These tools can discover and retrieve accurate documentation without parsing HTML.

## Ask AI

When searching for a term in our documentation, you can either select a page to view, or you can ask a question to AI by selecting Ask AI at the bottom of the results. It will search our documentation and respond with relevant information and links to the pages it used for references.

<div data-with-frame="true"><figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FhxobSNJMWBnlECxrEHFY%2FAsk%20AI%20in%20search%20bar.png?alt=media&amp;token=a6f2568e-e9bd-4b8d-904e-795629922261" alt="" width="188"><figcaption></figcaption></figure></div>

## MCP

Because our documentation is hosted in GitBook, an MCP is automatically generated for our full documentation that you can use. This works with Claude, Claude Code, Cursor, Codex, VS Code, and other MCP clients.

You'll need to use our MCP URL (`https://docs.fulfillmenttools.com/documentation/~gitbook/mcp`) to access it.

{% hint style="info" %}
Opening the MCP URL in a browser returns an error. Use a tool that can make HTTP requests.
{% endhint %}

You can copy this URL directly from an article by using the dropdown actions menu and selecting **Connect with MCP**.

<div data-with-frame="true"><figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FnIgx7zJXXWcidXl0SXtN%2FConnect%20docs%20to%20MCP.png?alt=media&amp;token=da0360e9-56f2-48e3-98f5-1d0220fd6880" alt="" width="375"><figcaption></figcaption></figure></div>

You can also follow the different instructions per provider below:

{% tabs %}
{% tab title="Claude" %}
These steps work in Claude on the web and in Claude Desktop.

Open **Settings**, and then select **Connectors**.

Click **Add custom connector**. Then paste the MCP server URL below:

```
https://docs.fulfillmenttools.com/documentation/~gitbook/mcp
```

{% endtab %}

{% tab title="Claude Code" %}
Run this command in your terminal:

```shellscript
claude mcp add --transport http fulfillmenttools-docs https://docs.fulfillmenttools.com/documentation/~gitbook/mcp
```

Replace `fulfillmenttools-docs` with any server name you want.
{% endtab %}

{% tab title="Cursor" %}
Open **Settings**, then select **MCP**.

Click **Add new MCP server**. Then paste `https://docs.fulfillmenttools.com/documentation/~gitbook/mcp`.

You can also add this file in `.cursor/mcp.json`:

```
{
  "mcpServers": {
    "fulfillmentools-docs": {
      "url": "https://docs.fulfillmenttools.com/documentation/~gitbook/mcp"
    }
  }
}
```

Replace `fulfillmenttools-docs` with your own server name if you want.
{% endtab %}

{% tab title="Codex" %}
Use the `codex mcp add` command, or add the server to your `config.toml`.

Command example:

```bash
codex mcp add fulfillmenttools-docs https://docs.fulfillmenttools.com/documentation/~gitbook/mcp
```

Config example:

```bash
[mcp_servers.fulfillmenttools-docs]
url = "https://docs.fulfillmenttools.com/documentation/~gitbook/mcp"
```

Replace `fulfillmenttools-docs` with your own server name if you want.
{% endtab %}

{% tab title="VS Code (Copilot)" %}
Open your `mcp.json` file. Then add a server entry with HTTP transport:

```json
{
  "servers": {
    "fulfillmenttools-docs": {
      "type": "http",
      "url": "https://docs.fulfillmenttools.com/documentation/~gitbook/mcp"
    }
  }
}
```

Replace `fulfillmenttools-docs` with your own server name if you want.
{% endtab %}
{% endtabs %}

If you use an agentic tool, you can also give it this setup prompt:

```
Add an MCP server named fulfillmenttools-docs with HTTP transport at https://docs.fulfillmenttools.com/documentation/~gitbook/mcp. Then verify it connects by listing its available tools.
```

{% hint style="info" %}
For information on the MCP Servers fulfillmenttools provides, see the [MCP articles](https://docs.fulfillmenttools.com/documentation/integrations/mcp-servers/mcp-server-fulfillmenttools-api.md).
{% endhint %}

## LLMs.txt

We have two versions of an LLMs.txt.

The [LLMs.txt](https://docs.fulfillmenttools.com/documentation/llms.txt) is a proposed standard for LLM-friendly web content. It lists every published page with a Markdown version. AI tools can use this index to discover our documentation.

The [LLMs.txt-full](https://docs.fulfillmenttools.com/documentation/llms-full.txt) includes our full documentation content in one place.

## AI Sidekick

The fulfillmenttools [AI Sidekick](https://docs.fulfillmenttools.com/documentation/backoffice/ai-sidekick.md) in Backoffice can be used to search our documentation, so you can stay in Backoffice but find the answers you need.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fulfillmenttools.com/documentation/getting-started/llm-ready-docs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
