Agent setup
Have your AI coding agent set up Duraton for you - the docs MCP, the product MCP, and Duraton's agent rules - from a single prompt.
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.dev/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
mcpServersconfig), so it uses the right commands and config paths. - Adds the Duraton docs MCP (
https://docs-mcp.duraton.dev/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, approvals, and evals. 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.mdand saving it to the agent's rules file (for exampleCLAUDE.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 asDURATON_API_KEYonly 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.
Related
- MCP server - the full reference for connecting and the tool list.
- Docs for AI assistants - point any tool at the Duraton docs
(
llms.txt, the docs MCP, or a stdio server).
Worked examples
Two complete Kafka connector configurations with the workflows that consume them - order events given a lane per order, and call events threaded into one session across regional topics.
Docs for AI assistants
Wire the Duraton docs into Claude, Cursor, and other AI tools so your assistant can search and read them.