Build with AI

Give your coding assistant the Nelkap docs, so the workflows it writes follow them.

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.

MCP server

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:

https://docs.nelkap.com/mcp

Claude Code

Run this command in your project:

claude mcp add --transport http nelkap \
  https://docs.nelkap.com/mcp

To share the server with your team, add it to the project’s .mcp.json file instead, and commit that file:

claude mcp add --transport http nelkap --scope project \
  https://docs.nelkap.com/mcp

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

{
  "mcpServers": {
    "nelkap": {
      "url": "https://docs.nelkap.com/mcp"
    }
  }
}

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.

Single pages

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.

Full docs

Two files cover every page:

File	What it holds
llms.txt	Every page, with its link and a one-line summary.
llms-full.txt	The full text of every page, in one file.

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

Review generated code

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

• Each call to another service and each write to your database is inside a step. See What to put in a step.
• Nothing outside steps reads the time, draws a random ID, or calls an API. See Determinism.
• Steps that charge, email, or write pass an idempotency key, or check before they act. See Idempotency.