Skip to main content
A coding assistant writes better workflows when it can read the docs. These docs are ready for it: your assistant can search them through an MCP server, read any page as Markdown, or take the whole site in one file.

Connect your assistant to the docs

The docs MCP server lets your assistant search these docs and read their pages while it works, so its code follows the current SDK. It needs no account and no key. Its URL is:

Claude Code

Run this command in your project:
To share the server with your team, add it to the project’s .mcp.json file instead, and commit that file:
Run claude mcp list to check that it’s connected.

Cursor

Open the menu at the top of any page of these docs, and choose Connect to Cursor. Or add the server to .cursor/mcp.json in your project:
.cursor/mcp.json

VS Code

Open the menu at the top of any page of these docs, and choose Connect to VS Code. Or run MCP: Add Server from the Command Palette, choose HTTP, and enter the server’s URL.

Other assistants

Any assistant that connects to remote MCP servers over HTTP can use the same URL.

Give your assistant one page

Each page has a menu at its top. It copies the page as Markdown, ready to paste into a chat, or opens the page in ChatGPT, Claude, or Perplexity, to ask questions about it. Every page is also served as Markdown: add .md to its address, like https://docs.nelkap.com/quickstart.md.

Give your assistant the whole docs

Two files cover every page: Give your assistant llms.txt to let it find the right page, or llms-full.txt to give it everything at once.

Check the steps it writes

Before you deploy a workflow your assistant wrote, check that: