Connect the docs to your AI assistant

These docs are available over the Model Context Protocol (MCP), so your coding assistant can search them directly and answer with links back to the exact section — instead of guessing from stale training data.

Server URL

https://T3F23WL577.algolia.net/mcp/1/pBfsB0jvSvOHvUzkKTVcLA/mcp

No API key, no sign-up, no authentication. The connection is read-only: it searches our public documentation and nothing else.

Add it to your client

Claude Code

claude mcp add --transport http dgw-docs \
  https://T3F23WL577.algolia.net/mcp/1/pBfsB0jvSvOHvUzkKTVcLA/mcp

Verify with claude mcp list.

ChatGPT

1. Open Settings → Security and login and turn on Developer mode.
2. Open ChatGPT Plugins and click the plus button.
3. Set the name to Delivery Gateway Docs and add a short description.
4. Under Connection, enter the MCP server URL: https://T3F23WL577.algolia.net/mcp/1/pBfsB0jvSvOHvUzkKTVcLA/mcp
5. Create the connection, then review the discovered tools and metadata.
6. Start a new conversation and add Delivery Gateway Docs from the tools menu.

:::note Availability Developer mode availability depends on your account and workspace policy. See the official OpenAI setup guide. :::

Claude (web/desktop)

1. Open Settings → Connectors and click Add custom connector.
2. Name: Delivery Gateway Docs
3. Remote MCP server URL: https://T3F23WL577.algolia.net/mcp/1/pBfsB0jvSvOHvUzkKTVcLA/mcp
4. Leave Advanced settings empty, click Add, then Connect.
5. Enable the connector from the prompt bar. Tools appear in new conversations.

:::note If you see a sign-in error The server needs no authentication, but the connector flow may still report that it couldn't register with the sign-in service. Press Connect again on the existing entry in your connectors list; if it persists, remove the connector and add it back. Adding the same URL twice returns a server with this URL already exists — that means the first attempt did create it, so connect to that one rather than adding a new one. :::

Cursor

Add to ~/.cursor/mcp.json (or %USERPROFILE%\.cursor\mcp.json):

{
  "mcpServers": {
    "dgw-docs": {
      "url": "https://T3F23WL577.algolia.net/mcp/1/pBfsB0jvSvOHvUzkKTVcLA/mcp"
    }
  }
}

Or: Cursor Settings → Tools and MCPs → Add MCP Server, paste the URL, set Authentication to none, then enable it from the prompt bar.

VS Code

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "dgw-docs": {
      "type": "http",
      "url": "https://T3F23WL577.algolia.net/mcp/1/pBfsB0jvSvOHvUzkKTVcLA/mcp"
    }
  }
}

What your assistant gets

Tool	What it does
algolia_search_index_docs	Searches every published documentation page. Accepts up to five query variations in one call, each with its own facet filters.
algolia_search_for_facet_values	Lists available values for a facet (type, lang, version). Rarely needed directly.

Every hit carries a url and an anchor, so the assistant can link to the exact section rather than the page.

:::tip Get the code samples too Code blocks are not part of the search index — a hit tells your assistant where the answer lives, not what the snippet says. Deeper section records (heading-only results) may come back with content: null for the same reason.

Every page is also published as raw Markdown: append .md to any docs URL, or point your assistant at /llms-full.txt. Most agents will fetch these on their own once they have the URL. :::

Prompts to start with

Using the Delivery Gateway docs, walk me through the minimal checkout
integration — what goes on the backend versus the frontend?

Search the Delivery Gateway docs for how to create a webhook and verify its
signature, then show me the createWebhook mutation inputs.

Plain-text alternative

If your tooling has no MCP support, the same content is available as static files:

File	Contents
/llms.txt	Index of every documentation page
/llms-full.txt	Complete documentation in one file
/llms-integration.txt	Getting started and integration guides only
/llms-merchant-api.txt	Merchant API reference only

Any page also returns Markdown if you append .md to its URL.

Limits

• Read-only, documentation only. The connector cannot reach your account, orders or shipments. For that, use the Merchant API.
• Public content only. Nothing behind authentication is exposed.
• Search queries reach Algolia. Tool calls send your query, plus the original prompt that triggered them, to Algolia for search analytics.
• Not a support channel. For account-specific questions, contact the Help Center.
• Answers are generated by your assistant. Verify against the linked page before shipping to production.