Read the Docs (llms.txt + MCP)

Search and query KyberSwap docs via llms.txt and Documentation MCP

Two surfaces help agents discover and understand KyberSwap before taking action: a flat documentation index that works everywhere, and the MCP Server's typed tool manifest for agents that prefer structured, schema-driven discovery.

llms.txt

A structured, LLM-optimised index of every KyberSwap developer doc, API endpoint, and integration guide, following the llmstxt.org standard. Works with any AI tool - paste the URL into a chat, attach it to a system prompt, or pipe it into a RAG pipeline.

URL

https://docs.kyberswap.com/llms.txt

https://docs.kyberswap.com/llms-full.txt

Usage

# Pull the index
curl -s https://docs.kyberswap.com/llms.txt

# Or paste the URL straight into any AI chat:
#   "Use https://docs.kyberswap.com/llms.txt as context, then …"

Example prompts once llms.txt is loaded:

  • "How do I get a swap quote on Ethereum using the Aggregator API?"

  • "Write a script that creates a gasless limit order on BNB Smart Chain."

Documentation MCP

KyberSwap's documentation site is hosted on GitBook, which automatically generates a read-only MCP server at:

Once connected, your AI assistant can search through the full documentation, retrieve specific pages, and answer questions using real-time content from docs.kyberswap.com — user guides, developer guides, API references, and all other published pages.

This is a documentation-only server. It does not execute swaps or build transactions — that is the role of the MCP Server described under Execute Operations below.

Server URL

HTTP transport. No authentication required. The server only provides access to published content.

Setup

Verify with:

Other MCP-compatible tools

Any tool that supports the MCP protocol can connect to https://docs.kyberswap.com/~gitbook/mcp using HTTP transport.

What the agent gets

Once connected, the assistant has real-time access to:

  • Search across all published documentation pages.

  • Retrieve full page content for any doc, guide, or API reference.

  • Answer questions using the latest published content — never drafts or unpublished changes.

Last updated

Was this helpful?