Invite-only.
Dock
Connect

Bolt.new

Bolt.new generates full-stack apps from prompts. No native MCP yet, but Bolt-built apps can call Dock's REST API from the generated code. Store the key as a project env secret and let Bolt wire the fetch calls.

Client
Bolt.new
StackBlitz app builder. REST via fetch + env secret.
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

  • Bolt.new account (free tier works).
  • A Dock dk_ key.
Env secret
Bolt project · .env · DOCK_API_KEY=dk_live_...
Prompt template
"Use the DOCK_API_KEY env var. Dock base URL is https://trydock.ai/api. Auth is Bearer on every call. Append rows to /workspaces/<slug>/rows when the form submits."
Generated server action (Bolt will produce something like)typescript
export async function addTask(title: string, status: string) {
  const res = await fetch(
    "https://trydock.ai/api/workspaces/content-pipeline/rows",
    {
      method: "POST",
      headers: {
        Authorization: `Bearer ${process.env.DOCK_API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ data: { title, status } }),
    }
  );
  if (!res.ok) throw new Error(await res.text());
  return res.json();
}

Troubleshooting

Symptom
Fix
Bolt hard-codes the key in source
Re-prompt with "use process.env.DOCK_API_KEY, never inline the literal key".
Preview works, deployed app 401s
Env secret only in dev. Add it in Bolt's deploy config too.

Related