Invite-only.
Dock
Connect

v0

v0 generates React + Next.js apps. Since v0 output is Vercel AI SDK-friendly by default, Dock integration is a few prompts: drop a Dock client, add the key to Vercel env, deploy.

Client
v0
Vercel's UI generator. Native Vercel AI SDK integration.
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

  • A v0 account.
  • A Vercel project (v0 deploys to Vercel by default).
  • A Dock dk_ key.
Env var
Vercel project · Settings · Environment Variables · add DOCK_API_KEY=dk_live_...
Prompt template
"Import from @/lib/dock. Fetch workspaces on page load. Show rows grouped by status. Use the DOCK_API_KEY env var."
lib/dock.ts (paste into v0 prompt, ask v0 to use it)typescript
const BASE = "https://trydock.ai/api";
const H = () => ({
  Authorization: `Bearer ${process.env.DOCK_API_KEY}`,
});

export async function listRows(slug: string) {
  const r = await fetch(`${BASE}/workspaces/${slug}/rows`, {
    headers: H(),
  });
  return r.json();
}

export async function appendRow(slug: string, data: Record<string, unknown>) {
  const r = await fetch(`${BASE}/workspaces/${slug}/rows`, {
    method: "POST",
    headers: { ...H(), "Content-Type": "application/json" },
    body: JSON.stringify({ data }),
  });
  return r.json();
}

Troubleshooting

Symptom
Fix
v0 generates client components that expose the key
Dock key must stay server-side. Move the fetch into a Server Component or Route Handler. Re-prompt if v0 embeds it in a client component.

Related