AgentDock

1.7k
Dock Agent Api
Cline

Cline

Use Cline (the VS Code agent) with the Dock workspace. Add the MCP server in Cline's settings and the agent calls 38 AgentDock tools alongside its file edits.

Cline runs as a VS Code extension and supports MCP servers natively. Add the Dock workspace once and Cline can read your documents, draft new ones, propose tracked changes, manage citations, and publish, without leaving the editor.

Cline stores MCP server config inside VS Code's settings. Open the Command Palette (Cmd+Shift+P), run "Cline: MCP Servers," and add a new server with these fields:

FieldValue
Nameagentdock
TypeHTTP (streamable)
URLhttps://app.agentdock.ai/api/mcp
Headersx-api-key: ak_usr_YOUR_TOKEN

Or edit the JSON directly. Cline's MCP config file lives at ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json (macOS) or the equivalent VS Code globalStorage path on Linux/Windows:

{
  "mcpServers": {
    "agentdock": {
      "type": "http",
      "url": "https://app.agentdock.ai/api/mcp",
      "headers": {
        "x-api-key": "ak_usr_YOUR_TOKEN"
      }
    }
  }
}

Reload VS Code. The next Cline task sees the AgentDock tools.

Screenshot
Cline's MCP Servers panel in VS Code with agentdock listed and the green connected indicator.

npm install -g agentdockai
agentdock login

login opens the browser. After approval, the token lands at ~/.agentdock/config.json. Same token goes in Cline's MCP header.

Run agentdock mcp-setup to get the JSON with the token filled in; paste it into Cline's settings file.

Draft from a prompt without leaving VS Code

In Cline's chat panel:

Use the AgentDock prompt "feature spec" to draft a new spec called
"Realtime presence v2." Save it to the Dock workspace.

get_user_prompt -> create_document -> write_document. The spec lives in AgentDock, viewable from any browser.

Use the workspace as context for code work

Read the AgentDock document "Realtime presence v2 spec." Implement the
data model in `packages/database/src/agentdock-schema/presence.ts`
according to that spec.

Cline calls read_document, then uses its native file edit tools for the code change. The spec is the source of truth.

Propose tracked changes from inside the editor

The "Realtime presence v2 spec" needs revisions. The TTL is 60 seconds,
not 90 as written. Propose tracked changes; do not overwrite.

suggest_edits drops the find-and-replace into your AgentDock review queue.

Publish at the end of a task

The spec is finalized. Publish it to /p/realtime-presence-v2 with title
"Realtime Presence v2: TTL, Heartbeats, and Reconnects."

publish_document ships the page.

Video
90-second screencast of the four workflows above, taken from a real VS Code window.

Every call needs the x-api-key header today; authenticated, the full 38 tools light up. A keyless tier for the public prompt library is coming soon. Tokens are user-scoped.

Cline shows the server but tools do not appear. Cline does not always refresh the tool list when you edit settings. Run "Cline: Reload MCP Servers" from the Command Palette, or restart VS Code.

401 on every call. Token is missing or expired. agentdock login, re-export with agentdock mcp-setup, paste into Cline's settings.

Cline tries to write to your AgentDock document AND a local file with the same name. Be explicit: "save to Dock," not "save the document."

CLI ReferenceCursor