Skip to main content
Glama

@trydock/mcp

npm version Published with provenance License: MIT

Local stdio bridge to the Dock MCP server. Point any MCP-capable agent (Claude Desktop, Cursor, Windsurf, Zed, Cline, Continue) at your Dock workspaces in one config change.

Do you need this package?

If your agent supports remote MCP connectors (Claude.ai web, Claude.ai Projects), you don't need this — add https://trydock.ai/api/mcp as a custom connector and follow the OAuth flow. See the MCP reference.

This package is for agents that only speak local stdio MCP — the dominant pattern for Claude Desktop and most code-editor agents today.

Quickstart

  1. Get an API key in Dock's Settings → API keys (trydock.ai).

  2. Add the config for your agent below.

  3. Restart the agent. You'll see Dock's 8 tools appear.

Related MCP server: Elasticflow MCP Server

Configs

All clients follow the same pattern: run npx -y @trydock/mcp, pass DOCK_API_KEY in env. Per-client JSON snippets are in configs/:

Client

File

Typical config path

Claude Desktop

configs/claude-desktop.json

~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

Cursor

configs/cursor.json

~/.cursor/mcp.json

Windsurf

configs/windsurf.json

~/.codeium/windsurf/mcp_config.json

Zed

configs/zed.json

~/.config/zed/settings.json (under context_servers)

Cline (VS Code)

configs/cline.json

VS Code settings → cline.mcpServers

Continue

configs/continue.json

~/.continue/config.json

Example (Claude Desktop):

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "dk_..."
      }
    }
  }
}

Tools

All 8 tools are forwarded to the hosted Dock server. JSON schemas live in schemas/.

Tool

Purpose

list_workspaces

Enumerate workspaces you can access

get_workspace

Fetch a workspace by slug

list_rows

Read rows from a table-mode workspace

create_row

Append a row

update_row

Partial-merge update

delete_row

Remove a row

create_workspace

Create a new workspace

get_recent_events

Read the activity log

Full reference with examples: trydock.ai/docs/mcp.

How the bridge works

The bridge is a ~100-line Node process (src/bridge.js). Every JSON-RPC message your agent writes on stdin is forwarded over HTTPS to https://trydock.ai/api/mcp with your DOCK_API_KEY as Bearer auth. The hosted server owns authentication, rate limits, audit, and tool execution. The bridge stores no state and logs no request bodies.

Environment variables:

Variable

Required?

Purpose

DOCK_API_KEY

yes

Bearer token (get one from Settings → API keys)

DOCK_MCP_URL

no

Override the upstream endpoint (staging / self-host). Default: https://trydock.ai/api/mcp

Security

  • Your API key is only held in the agent's environment and passed on each HTTPS call. It's never logged, never written to disk by this bridge.

  • Rotate keys any time in Dock's Settings → API keys. Old keys return 401 immediately on revocation.

  • Keys are stored as SHA-256 hashes on Dock's side, not plaintext. A Dock DB leak wouldn't expose usable credentials.

  • See the full security doc for the threat model, the revocation runbook, and what data is audited.

License

MIT. Copyright © 2026 Vector Apps, Inc.

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to search for available desk space, submit room reservations, and let admins approve or reject booking requests through a scoped MCP API.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to access and manage a Workel workspace through MCP tools, reading projects, tasks, comments, events, and members, and optionally creating or updating tasks, comments, and events when write scopes and local consent are enabled.
    9 npm
    MIT