DokkitAgents

Agents

Let an agent wire your apps in, then let it watch with you. Everything goes through one API, and a token decides how far it may go.

Wire an app in

Hand your agent this prompt in the app's repository. It reads one file about Dokkit, describes the app, adds the library and proves it, before any server exists.

A Claude Code plugin that does this for you soon

/dokkit as a plugin: it wires the repo in, connects the MCP with a token you paste, and answers "what broke since my last deploy" from inside the editor.

Connect it to your server

Make a token in Settings, then give it to the agent. The MCP address is your server's address with /mcp on the end.

For Claude Code, one line:
claude mcp add --transport http dokkit https://your.domain.com/mcp --header "Authorization: Bearer dku_..."

For any other MCP client, this in its settings:

{
  "mcpServers": {
    "dokkit": {
      "type": "http",
      "url": "https://your.domain.com/mcp",
      "headers": { "Authorization": "Bearer dku_..." }
    }
  }
}

For a script, the same token on the API:
curl -H "Authorization: Bearer dku_..." https://your.domain.com/api/v1/inbox

dokkit.dev's own MCP, with no account soon

An MCP at dokkit.dev/mcp any agent can use before you install anything: write a dokkit.toml for a described service, check a file, list the library calls for a language, explain an error from dokkit check.

What its token allows

The agent is offered only the tools its token allows. Switch them on and ask it something.

A token for an agentdku_… · made in Settings

Read states, issues, jobs and errorson

Read what is written in the logs

Snooze, mark as seen, watch, plan downtime

Everything you can do: keys, people, rules, checks

Tools this token is offered

Every tool, with its arguments

Sample answers on the sample company. The tool names are the real ones.

What it reads

Plain files at stable addresses. Paste one link and an agent knows the rest.

https://dokkit.dev/llms-full.txtEverything in one file: the API, every command, the MCP tools and the dokkit.toml reference.

https://dokkit.dev/llms.txtThe index of what there is to read.

https://dokkit.dev/api.mdEvery API call, with what to send and what comes back.

https://dokkit.dev/openapi.jsonThe same API as an OpenAPI file.

https://dokkit.dev/cli.mdEvery command of the dokkit program.

Install the serverSo there is something for the agent to watch The librariesEleven languages, the same calls in each Every MCP toolAll 76, with the token access each needs Read the whole APIEvery call an agent or a script can make Back to the startWhat Dokkit is, and the working sample

Wire an app in

Connect it to your server

What its token allows

What it reads

Next: