Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
kiro logo

Kiro

Kiro is AWS's agentic coding IDE with native MCP support. Add Dock once and Kiro's spec-driven workflows can read and write Dock workspaces alongside your codebase.

Client
Kiro
AWS agentic IDE. MCP via Kiro settings.
HTTP JSON-RPC (streamable-http)
Dock MCP
trydock.ai/api/mcp
37 tools · OAuth 2.1 + DCR · Bearer
Auth path
1
Mint a dk_ key in Dock Settings → API keys.
2
Paste it as Authorization: Bearer dk_… in the client config.
3
Client calls Dock MCP directly on every request.

Prerequisites

  • Kiro installed.
  • A Dock dk_ key.
Config file
~/.kiro/mcp.json
Reload
Kiro hot-reloads MCP configs on save.
~/.kiro/mcp.jsonjson
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_c914f1c6..."
      }
    }
  }
}

Verify

@dock list my workspaces

Troubleshooting

Symptom
Fix
Tools not offered in spec planning
Tools need to be enabled per-spec. Open the spec settings, check the boxes for the Dock tools you want available.

Frequently asked questions

How do I connect Dock to Kiro?
Add Dock as a remote MCP server in Kiro. Either let Kiro's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Kiro's MCP config under the `Authorization: Bearer dk_…` header.
Does Kiro work with Dock's MCP server?
Yes. Dock exposes 43 MCP tools at `https://trydock.ai/api/mcp` over HTTP transport with OAuth 2.1 + DCR and Bearer-token auth. Any MCP-spec-compliant client, including Kiro, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Kiro can write to?
When you mint the `dk_` key for Kiro in Settings → API keys, pick the workspace from the dropdown. The key returns 403 on every other workspace regardless of what the prompt asks. To scope across multiple, mint multiple keys or add the agent as an explicit member of each. Learn more →
How do I see what Kiro did in my Dock workspace?
Open the workspace in your browser. Every row Kiro created or updated is stamped with the agent's identity (orb + name) in the createdBy / updatedBy field. The workspace activity feed shows every action chronologically. Learn more →
How do I undo a row Kiro wrote to Dock?
Open the row, click the kebab menu, choose Delete (soft-delete preserves history). For bulk reverts use the activity feed to find the agent's session and delete its rows in batch. To prevent future writes, revoke Kiro's `dk_` key in Settings → API keys.
Can multiple Kiro sessions share state through Dock?
Yes. Every Kiro session reads and writes the same workspace, so handoffs across machines or across long-running multi-session workflows just work. The Dock workspace IS the shared state; no separate message bus required.
Does Kiro need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Kiro hits Dock's discovery endpoint at `/.well-known/oauth-authorization-server` and auto-registers as a client. The `dk_` Bearer token path is fine for owned-code agents and CI scripts; pick whichever fits your stack. Learn more →
How do I add Dock to Kiro's MCP config?
Open Kiro Settings → MCP servers, add a new server with URL `https://trydock.ai/api/mcp`, transport HTTP, paste your Bearer token. Save and reload; the Dock tools surface via Kiro's standard tool-discovery handshake.
Does Kiro's spec-driven workflow work well with Dock?
Yes. Kiro can read your spec from a Dock doc surface and write its implementation plan back to the same workspace as a separate doc surface. Your team reviews the plan in the Dock web UI before Kiro starts coding.
Can I have Kiro's spec writer and Claude Code's implementer share a Dock workspace?
Yes. Each agent has its own `dk_` key and signed-agent identity. Kiro writes specs to one surface, Claude Code reads them and writes implementation notes to another surface. Real-time SSE keeps them in sync.

Related

Updated