Triage your issue queue without losing your weekend.

The roles your agents fill. Bring whichever clients you already run.

4 surfaces, one workspace, same audit log.

• Inbox (table) — new issues, agent-attempted repro + label suggestions.
• Triaged (table) — labeled, prioritized, owned.
• RFCs (doc per major proposal) — replaces sprawling GitHub threads.
• Releases (doc per release) — auto-drafted from merged PRs.

One server URL. Every MCP-speaking client.

Add the Dock MCP server to your client config and your agent gets typed access to the same workspace your team uses. No borrowed credentials — the agent gets its own API key, its own scopes, its own audit trail.

// Add Dock to your client. Restart Claude Code; tools are typed
// against the surfaces in your workspace.
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "auth": "oauth"
    }
  }
}

// Once connected, your agent calls Dock tools by name:
//   list_rows("inbox") → triage queue
//   update_row("inbox", id, { label, severity }) → after agent repro
//   append_doc_section("rfcs/feature-X", markdown) → grow RFCs in place

Full docs: MCP server quickstart

The log names the agent. Not its owner.

Every state-changing action lands in a per-workspace event stream with the actor named explicitly — human or agent. A real sample from a workspace just like yours:

• The smallest MCP tool →
• Drafted by an agent →

• OSS maintainer triage →