Invite-only.
Dock
Connect

curl / bash

Dock's REST API is plain HTTPS with JSON bodies. Every MCP tool has a REST equivalent. For quick scripts, CI steps, and one-off ops, curl is usually the fastest path.

Client
curl / bash
Universal. REST endpoints with Bearer auth.
HTTP JSON-RPC (streamable-http)
Dock MCP
trydock.ai/api/mcp
37 tools · OAuth 2.1 + DCR · Bearer
Auth path
1
Mint a dk_ key in Dock Settings → API keys.
2
Paste it as Authorization: Bearer dk_… in the client config.
3
Client calls Dock MCP directly on every request.

Prerequisites

  • curl installed (every macOS, most Linux, Windows 11).
  • A Dock dk_ key.
List workspacesbash
export DOCK_API_KEY=dk_live_c914f1c6...

curl https://trydock.ai/api/workspaces \
  -H "Authorization: Bearer $DOCK_API_KEY"
Append a rowbash
curl -X POST https://trydock.ai/api/workspaces/content-pipeline/rows \
  -H "Authorization: Bearer $DOCK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data":{"title":"From bash","status":"drafted"}}'
Patch a rowbash
curl -X PATCH https://trydock.ai/api/workspaces/content-pipeline/rows/row_01HX... \
  -H "Authorization: Bearer $DOCK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data":{"status":"sealed"}}'
Stream events (SSE)bash
curl -N https://trydock.ai/api/workspaces/content-pipeline/subscribe \
  -H "Authorization: Bearer $DOCK_API_KEY"

Verify

# A 200 plus a JSON body means you're wired up.
curl -i https://trydock.ai/api/me \
  -H "Authorization: Bearer $DOCK_API_KEY" | head

Troubleshooting

Symptom
Fix
401 on every request
Header format: Authorization: Bearer dk_live_... (exact capitalization, space, no quotes).
Pipe into jq for scripting
Every Dock endpoint returns JSON, perfect for jq. e.g. curl ... | jq '.workspaces[] | .slug'.

Related