Free for 30 days on Scale.Start free
Build10 steps3-7 days

Connect Claude to your team data via MCP

A production MCP server that exposes your team's data to Claude with proper auth, deployed to a public URL, registered with Claude Desktop + Claude Code, and surviving real-world conversations without leaking secrets.

Open in DockSee every step →

A production MCP server that exposes your team's data to Claude with proper auth

A production MCP server that exposes your team's data to Claude with proper auth, deployed to a public URL, registered with Claude Desktop + Claude Code, and surviving real-world conversations without leaking secrets.

Spin up an agent for the heavy lifting

Drafts tool schemas and descriptions from your existing API surface area.

10 steps, 20 official links, 3 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
10Steps
3Agent prompts
20Official links
7Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docMCP integration plan
  • tableTools registry
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/connect-claude-to-your-data-via-mcp and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

What's the difference between MCP and OpenAI's function calling?
Function calling is per-conversation: you pass a list of tools when you make an API call, and the model can call them. MCP is a persistent protocol: a server runs alongside the client, exposes tools + resources, and the client (Claude Desktop, Claude Code, Cursor) auto-discovers them. MCP also supports resources (auto-loaded context) and prompts (saved templates), which function calling doesn't have. Both are useful, MCP is the right choice for a server that's always available, function calling for a per-request tool set.
Do I need to use Claude to use MCP?
No. MCP is an open standard. Claude Desktop, Claude Code, and Cursor speak it natively. There are community implementations for other clients. Any model that can do tool calls can be wired to MCP through a thin adapter. The spec at modelcontextprotocol.io is provider-neutral.
How does auth work for an MCP server with multiple users?
OAuth 2.1 with Dynamic Client Registration is the canonical multi-user pattern: the client registers with your server, the user approves once, your server issues a per-user token. The MCP spec at modelcontextprotocol.io/docs/concepts/authentication walks the flow. Static API key headers are simpler if every user has a long-lived token, but they don't scale to teams cleanly.
Can my MCP server call other MCP servers?
Yes, but it's an unusual pattern. Most servers expose primitives directly. If you find yourself wanting to chain servers, consider whether the work belongs in the client (the LLM agent) instead, agents are good at chaining tool calls across servers.
How do I version an MCP server without breaking existing clients?
MCP supports protocol-level capability negotiation, the client and server agree on a capability set on connect. For your tool surface area: add new tools freely, deprecate old tools by adding a deprecation note in the description for one release, then remove. Don't change the input schema of an existing tool, ship a new tool with the new schema and migrate clients over.
Can my AI agents help build the MCP server?
Yes. The template ships agent prompts for the slow parts: drafting tool schemas from your existing API, generating handler stubs, running the eval pass against the MCP Inspector, and analyzing tool-call logs to identify gaps. The Tools registry surface is the canonical record of what's shipped, what's deprecated, and what's queued.
Related templates

More from Build

BuildMixed
Launch your iPhone app on the App Store

10-step plan from 'I have a build on my Mac' to 'users are downloading from search.' Real Apple gates, real gotchas, real agent prompts.

BuildMixed
Build a webapp in a day

10-step plan from blank idea to deployed app with auth, a database, and a domain — all in 24 hours. Battle-tested defaults so you don't waste 6 hours picking a stack.

BuildMixed
Launch your Android app on Google Play

10-step plan from 'I have an APK on my laptop' to 'users are installing from Play search.' Real Google gates, real gotchas, real agent prompts.

Browse all Build templates →

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.