Is ai.trydock/dock safe to use?

ai.trydock/dock has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install ai.trydock/dock?

ai.trydock/dock can be installed by cloning its GitHub repository and following the setup instructions in the README.

ai.trydock/dock

The AI workspace for you, your team, and every agent you run. Tables and docs, one live surface.

0 tools GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Untested

Transport:

0 tools

Grade F

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Untested on Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ai-trydock-dock": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/ai-trydock-dock)](https://mcppedia.org/s/ai-trydock-dock)

Read me

What ai.trydock/dock does

The AI workspace for you, your team, and every agent you run. Tables and docs, one live surface.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

9/100across 5 weighted dimensions

How we score →

0255075100

−91

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is ai.trydock/dock safe to use?: ai.trydock/dock has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install ai.trydock/dock?: ai.trydock/dock can be installed by cloning its GitHub repository and following the setup instructions in the README.

Similar servers

Others in developer-tools

View all →

XcodeBuildMCP97

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

5.3k 1

Supabase MCP Server97

Manage Supabase projects — databases, auth, storage, and edge functions

2.6k 4

XcodeBuildMCP97

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

5.3k 2

Gemini Cli95

An open-source AI agent that brings the power of Gemini directly into your terminal.

102.0k 8

MCP Security Weekly

Get CVE alerts and security updates for ai.trydock/dock and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Untested on Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ai-trydock-dock": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/ai-trydock-dock)](https://mcppedia.org/s/ai-trydock-dock)

Read me

What ai.trydock/dock does

The AI workspace for you, your team, and every agent you run. Tables and docs, one live surface.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

@trydock/mcp

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

Get an API key in Dock's Settings → API keys (trydock.ai).
Add the config for your agent below.
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/:

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

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

9/100across 5 weighted dimensions

How we score →

0255075100

−91

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is ai.trydock/dock safe to use?: ai.trydock/dock has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install ai.trydock/dock?: ai.trydock/dock can be installed by cloning its GitHub repository and following the setup instructions in the README.