Invite-only.
Dock
Connect

ChatGPT (Custom GPT + Actions)

OpenAI's ChatGPT (Plus and Team) can call arbitrary HTTPS APIs via the Actions feature in a Custom GPT. Dock is a plain REST API with Bearer auth, so this wires in directly. When ChatGPT adds first-class MCP, swap to that (our MCP server has the same tools).

Client
ChatGPT (Custom GPT + Actions)
ChatGPT doesn't speak MCP yet. Use Dock's REST API via Actions.
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

  • ChatGPT Plus or Team (to create Custom GPTs).
  • A Dock dk_ key.
UI path
ChatGPT · Explore GPTs · Create · Configure · Actions
Auth type
API key · Auth Type "Bearer" · paste dk_live_...
OpenAPI schema
Fetch from https://trydock.ai/openapi.json (we publish a condensed OpenAPI 3.1 spec for exactly this use case).

The full REST surface is large. For a Custom GPT, keep the OpenAPI schema focused on the 5-6 endpoints your GPT actually calls (list workspaces, list rows, create row, update row, post comment). Less is faster for both the user and the model.

Verify

In your Custom GPTtext
List my Dock workspaces, then append a row to content-pipeline.

Troubleshooting

Symptom
Fix
ChatGPT says "Action failed: unauthorized"
The Auth Type must be "Bearer", and the API key you pasted should NOT include the word "Bearer" (OpenAI adds that prefix for you).
Actions time out on list-workspaces
OpenAI enforces ~30s on Action calls. Dock responses are well under that; a timeout usually means the request didn't reach Dock. Check the OpenAPI schema's servers array points at https://trydock.ai.

Related