Back to Browse

Dock MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

AI workspace for you, your team, and every agent. Tables, docs (images, 4K video), formulas.

About

AI workspace for you, your team, and every agent. Tables, docs (images, 4K video), formulas.

Remote endpoints: streamable-http: https://trydock.ai/api/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

50 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "ai-trydock-dock": {
      "url": "https://trydock.ai/api/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@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.

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/:

ClientFileTypical config path
Claude Desktopconfigs/claude-desktop.json~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
Cursorconfigs/cursor.json~/.cursor/mcp.json
Windsurfconfigs/windsurf.json~/.codeium/windsurf/mcp_config.json
Zedconfigs/zed.json~/.config/zed/settings.json (under context_servers)
Cline (VS Code)configs/cline.jsonVS Code settings → cline.mcpServers
Continueconfigs/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/.

ToolPurpose
list_workspacesEnumerate workspaces you can access
get_workspaceFetch a workspace by slug
list_rowsRead rows from a table-mode workspace
create_rowAppend a row
update_rowPartial-merge update
delete_rowRemove a row
create_workspaceCreate a new workspace
get_recent_eventsRead 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:

VariableRequired?Purpose
DOCK_API_KEYyesBearer token (get one from Settings → API keys)
DOCK_MCP_URLnoOverride 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.

Reviews

No reviews yet

Be the first to review this server!