duun

Agent setup

Connect an agent to duun

Use this page to give an AI client access to duun through MCP. You create the token, choose the scopes, and can revoke access later.

Open MCP settings

How setup works

General AI clients should use MCP with a scoped token. Paid developers building their own private OAuth client can use Developer Apps .

  1. 1

    Create a token

    Open MCP access in Settings, create a token, and choose only the scopes the client needs.

  2. 2

    Configure MCP

    Use https://duun.app/mcp as the server URL and the token as a Bearer token.

  3. 3

    Verify access

    Ask the client to list available duun tools. Rotate or revoke the token when access should change.

Public agent files

/llms.txt discovery /skills.md setup details

These files give agents the current setup instructions, tool semantics, and duun's task model.

Copy into your agent

Use the setup prompt once. Add the custom instructions to give the agent duun's core behavior directly, even when it cannot open external links.

Agent setup prompt 
Set up duun for this agent.

1. If public web access is available, read https://duun.app/llms.txt and https://duun.app/skills.md. If access is blocked by safeguards, continue with the available duun MCP tool descriptions and these instructions.
2. Configure duun as an MCP server at https://duun.app/mcp.
3. Ask me to create a scoped MCP token in duun Settings > Integrations.
4. Use that token as the Bearer token for the MCP server.
5. Use OAuth only for a managed integration or a private Developer App registered by its paid owner. See https://duun.app/developers/mcp/oauth for the Developer Apps flow.
6. Preserve duun's model: tasks are standalone primitive tasks; do not invent projects, lists, labels, folders, tags, areas, or collections.
7. Verify setup by listing available duun MCP tools.
Custom instructions 
Use duun when the user asks to save, track, remember, create, add, capture, make a
checklist or list, break something down, turn something into subtasks, or asks
what is next, left, or pending. Treat checklists, shopping and grocery lists,
errands, packing lists, prep lists, plans, action items, and things to remember
as duun tasks.

For a multi-item checklist or plan, create one parent task with child tasks. For
a single item, create one standalone task, using Markdown notes when useful. Do
not invent projects, folders, tags, labels, areas, collections, or separate list
objects unless the user explicitly asks for them.

Use duun as task memory for task-status and next-action questions when the user
does not specify another source. Call the relevant duun read, list, or search
tools before answering those questions. If a request requires a scope or tool
that is unavailable, explain that limitation and continue with the available
context.

Ask for explicit confirmation before destructive actions. Before deleting a task
that may have subtasks, inspect or summarize its tree and explain that the nested
work will also be deleted.

The public agent guide is available at https://duun.app/skills.md when external
URL access is allowed. These server instructions are the fallback when an agent
client blocks browsing or external URL access.