{
  "markdown": "# @trydock/mcp\n\n[![npm version](https://img.shields.io/npm/v/%40trydock%2Fmcp?color=0A84FF&label=npm)](https://www.npmjs.com/package/@trydock/mcp)\n[![Published with provenance](https://img.shields.io/badge/npm-published%20with%20provenance-06D6A0?logo=npm)](https://docs.npmjs.com/generating-provenance-statements)\n[![License: MIT](https://img.shields.io/badge/license-MIT-8499B1)](./LICENSE)\n\nLocal stdio bridge to the [Dock](https://trydock.ai) MCP server. Point any\nMCP-capable agent (Claude Desktop, Cursor, Windsurf, Zed, Cline, Continue)\nat your Dock workspaces in one config change.\n\n> **Do you need this package?**\n>\n> If your agent supports **remote MCP connectors** (Claude.ai web,\n> Claude.ai Projects), you don't need this — add\n> `https://trydock.ai/api/mcp` as a custom connector and follow the OAuth\n> flow. See the [MCP reference](https://trydock.ai/docs/mcp).\n>\n> This package is for agents that only speak **local stdio MCP** — the\n> dominant pattern for Claude Desktop and most code-editor agents today.\n\n## Quickstart\n\n1. Get an API key in Dock's Settings → API keys\n   ([trydock.ai](https://trydock.ai)).\n2. Add the config for your agent below.\n3. Restart the agent. You'll see Dock's 8 tools appear.\n\n## Configs\n\nAll clients follow the same pattern: run `npx -y @trydock/mcp`, pass\n`DOCK_API_KEY` in env. Per-client JSON snippets are in\n[`configs/`](./configs):\n\n| Client | File | Typical config path |\n|---|---|---|\n| Claude Desktop | [`configs/claude-desktop.json`](./configs/claude-desktop.json) | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) |\n| Cursor | [`configs/cursor.json`](./configs/cursor.json) | `~/.cursor/mcp.json` |\n| Windsurf | [`configs/windsurf.json`](./configs/windsurf.json) | `~/.codeium/windsurf/mcp_config.json` |\n| Zed | [`configs/zed.json`](./configs/zed.json) | `~/.config/zed/settings.json` (under `context_servers`) |\n| Cline (VS Code) | [`configs/cline.json`](./configs/cline.json) | VS Code settings → `cline.mcpServers` |\n| Continue | [`configs/continue.json`](./configs/continue.json) | `~/.continue/config.json` |\n\nExample (Claude Desktop):\n\n```json\n{\n  \"mcpServers\": {\n    \"dock\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@trydock/mcp\"],\n      \"env\": {\n        \"DOCK_API_KEY\": \"dk_...\"\n      }\n    }\n  }\n}\n```\n\n## Tools\n\nAll 8 tools are forwarded to the hosted Dock server. JSON schemas live\nin [`schemas/`](./schemas).\n\n| Tool | Purpose |\n|---|---|\n| [`list_workspaces`](./schemas/list_workspaces.json) | Enumerate workspaces you can access |\n| [`get_workspace`](./schemas/get_workspace.json) | Fetch a workspace by slug |\n| [`list_rows`](./schemas/list_rows.json) | Read rows from a table-mode workspace |\n| [`create_row`](./schemas/create_row.json) | Append a row |\n| [`update_row`](./schemas/update_row.json) | Partial-merge update |\n| [`delete_row`](./schemas/delete_row.json) | Remove a row |\n| [`create_workspace`](./schemas/create_workspace.json) | Create a new workspace |\n| [`get_recent_events`](./schemas/get_recent_events.json) | Read the activity log |\n\nFull reference with examples: [trydock.ai/docs/mcp](https://trydock.ai/docs/mcp).\n\n## How the bridge works\n\nThe bridge is a ~100-line Node process ([`src/bridge.js`](./src/bridge.js)).\nEvery JSON-RPC message your agent writes on stdin is forwarded over HTTPS\nto `https://trydock.ai/api/mcp` with your `DOCK_API_KEY` as Bearer auth.\nThe hosted server owns authentication, rate limits, audit, and tool\nexecution. The bridge stores no state and logs no request bodies.\n\nEnvironment variables:\n\n| Variable | Required? | Purpose |\n|---|---|---|\n| `DOCK_API_KEY` | yes | Bearer token (get one from Settings → API keys) |\n| `DOCK_MCP_URL` | no | Override the upstream endpoint (staging / self-host). Default: `https://trydock.ai/api/mcp` |\n\n## Security\n\n- Your API key is only held in the agent's environment and passed on\n  each HTTPS call. It's never logged, never written to disk by this\n  bridge.\n- Rotate keys any time in Dock's Settings → API keys. Old keys return\n  401 immediately on revocation.\n- Keys are stored as SHA-256 hashes on Dock's side, not plaintext. A\n  Dock DB leak wouldn't expose usable credentials.\n- See the full [security doc](https://trydock.ai/docs/security) for the\n  threat model, the revocation runbook, and what data is audited.\n\n## License\n\nMIT. Copyright © 2026 Vector Apps, Inc.\n",
  "bytes": 4367,
  "sha": "7bb3710e137c73a84bfaac9fcb7369712f28b6ea59b211fa0b689f00a9c1e20c",
  "repo_slug": "try-dock-ai/mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_trydock_dock_a349a869/readme"
}