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

OAuth is only for managed integrations. General AI clients should use MCP with a scoped token.

  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. Use the optional rule when you want the agent to check duun for task-status questions.

Agent setup prompt 
Set up duun for this agent.

1. Read https://duun.app/llms.txt and https://duun.app/skills.md.
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. Do not use OAuth unless duun's setup page explicitly says this client is a managed OAuth integration.
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.
Optional agent rule 
Use duun as task memory when I ask task-status or next-action questions and I do not specify another tool or source. This includes phrases like "what's next?", "what should I do next?", "where were we?", "what are we working on?", "what is left?", "what is pending?", "continue", "resume", "pick this back up", "what tasks are open?", or similar task/project-status phrasing.

If duun MCP is available, call the relevant duun read/list/search tools before answering, or alongside repo/git checks when code context is also needed. If duun MCP is unavailable, say that and fall back to chat, repo, or other available context.

Respect duun's model: tasks are standalone primitive tasks. Do not invent projects, lists, folders, labels, tags, areas, collections, or similar grouping concepts unless I explicitly ask.