AI coding tools

If you build with an AI coding agent (Claude Code, Codex, Cursor, Windsurf, VS Code, and others), you can have it wire up Duraton for you instead of doing it by hand. Duraton publishes a machine-readable setup file that your agent reads and acts on directly.

Give your agent this prompt

Paste this into your agent:

Fetch https://docs.duraton.ai/agent-setup.md and follow it to set up Duraton in this project: add the Duraton MCP servers, install the project rules, and sign me in.

Your agent fetches /agent-setup.md and runs the steps itself - you do not run the commands.

What your agent will do

Following the setup file, the agent:

Detects which agent it is (Claude Code, Codex, Cursor, Windsurf, VS Code, or a generic mcpServers config), so it uses the right commands and config paths.
Adds the Duraton docs MCP (https://docs.duraton.ai/mcp) so it can search and fetch the documentation on demand.
Adds the Duraton product MCP (https://mcp.duraton.dev) so it can drive your runs, events, and approvals. It defaults to the bare URL - your whole workspace, where the agent can switch between and create projects when you sign in - and can pin a single project with a single-project URL instead.
Installs Duraton’s agent rules by fetching /agent-rules.md and saving it to the agent’s rules file (for example CLAUDE.md, AGENTS.md, or .cursor/rules/), so it knows Duraton’s core concepts.
Authenticates - OAuth opens in your browser the first time a Duraton product tool is used, and you complete sign-in and the project pick there.

The setup file is instructions for an agent, but it is plain and readable - open /agent-setup.md yourself to see exactly what your agent will do before you run it.

Guardrails

The setup file tells your agent to keep secrets out of the flow:

It will never ask you for, or store, a Duraton secret key. Secret keys (dtn_live_...) are issued by you in the console under API Keys and set as DURATON_API_KEY only when wiring a runner - never for MCP setup, which uses OAuth.
It grants the least privilege a task needs: read-only access to inspect runs, write access only to trigger events or control runs.

Point an assistant at the docs

The docs are published in a machine-readable form so an AI assistant can pull them in as context: an llms.txt index at /llms.txt, a full single-file dump at /llms-full.txt, and clean markdown for every page (add /content.md to a doc’s markdown path, e.g. /llms.mdx/docs/guides/quickstart/content.md).

Point a tool at llms.txt

Any tool that understands llms.txt - Cursor’s @Docs, for example - can index the docs directly. Give it this URL:

https://docs.duraton.ai/llms.txt

The index links to the clean markdown for each page, so the tool fetches documentation, not rendered HTML.

Connect over MCP

The docs run as a hosted MCP server over Streamable HTTP, so an assistant can search and fetch them on demand with nothing to install. It exposes two tools, list_doc_sources and fetch_docs, and is at:

https://docs.duraton.ai/mcp

Add it to your client:

Claude Code
Cursor
VS Code
Windsurf
Config file

claude mcp add --transport http duraton-docs https://docs.duraton.ai/mcp

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (one project):

~/.cursor/mcp.json

{
  "mcpServers": {
    "duraton-docs": {
      "url": "https://docs.duraton.ai/mcp"
    }
  }
}

Add to .vscode/mcp.json. VS Code nests servers under a servers key:

.vscode/mcp.json

{
  "servers": {
    "duraton-docs": {
      "type": "http",
      "url": "https://docs.duraton.ai/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. Windsurf names the field serverUrl:

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "duraton-docs": {
      "serverUrl": "https://docs.duraton.ai/mcp"
    }
  }
}

Most other MCP clients read a mcpServers map with an http server:

.mcp.json

{
  "mcpServers": {
    "duraton-docs": {
      "type": "http",
      "url": "https://docs.duraton.ai/mcp"
    }
  }
}

Use a stdio server instead If your client speaks stdio rather than HTTP, mcpdoc serves the same two tools from the llms.txt.

mcpdoc runs via uvx, so you need uv installed. The command downloads mcpdoc on first run.

claude mcp add duraton-docs -- uvx --from mcpdoc mcpdoc --urls Duraton:https://docs.duraton.ai/llms.txt --transport stdio

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (one project):

~/.cursor/mcp.json

{
  "mcpServers": {
    "duraton-docs": {
      "command": "uvx",
      "args": ["--from", "mcpdoc", "mcpdoc", "--urls", "Duraton:https://docs.duraton.ai/llms.txt", "--transport", "stdio"]
    }
  }
}

Add to .vscode/mcp.json. VS Code nests servers under a servers key:

.vscode/mcp.json

{
  "servers": {
    "duraton-docs": {
      "command": "uvx",
      "args": ["--from", "mcpdoc", "mcpdoc", "--urls", "Duraton:https://docs.duraton.ai/llms.txt", "--transport", "stdio"]
    }
  }
}

Add to ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.duraton-docs]
command = "uvx"
args = ["--from", "mcpdoc", "mcpdoc", "--urls", "Duraton:https://docs.duraton.ai/llms.txt", "--transport", "stdio"]

Add to ~/.codeium/windsurf/mcp_config.json:

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "duraton-docs": {
      "command": "uvx",
      "args": ["--from", "mcpdoc", "mcpdoc", "--urls", "Duraton:https://docs.duraton.ai/llms.txt", "--transport", "stdio"]
    }
  }
}

Add to claude_desktop_config.json:

claude_desktop_config.json

{
  "mcpServers": {
    "duraton-docs": {
      "command": "uvx",
      "args": ["--from", "mcpdoc", "mcpdoc", "--urls", "Duraton:https://docs.duraton.ai/llms.txt", "--transport", "stdio"]
    }
  }
}

Restart the client, and the assistant can list the docs source and fetch any page on demand.

See the AI examples running end to end in Examples.

MCP server - the full reference for connecting and the tool list.

Start with code

Agent kit

AI

Durable runs

Integrations

TypeScript SDK

REST API

Protocol

AI coding tools

Give your agent this prompt

What your agent will do

Guardrails

Point an assistant at the docs

Point a tool at llms.txt

Connect over MCP

​Give your agent this prompt

​What your agent will do

​Guardrails

​Point an assistant at the docs

​Point a tool at llms.txt

​Connect over MCP

​Related

Give your agent this prompt

What your agent will do

Guardrails

Point an assistant at the docs

Point a tool at llms.txt

Connect over MCP

Related