Free for 30 days on Scale.Start free
Write

Content calendar

Posts, drafts, schedule, distribution. One agent drafts the long ones; another pulls forward what slips.

Posts

Posts, drafts, schedule, distribution. One agent drafts the long ones; another pulls forward what slips.

Spin up an agent for the heavy lifting

Drafts long-form pieces from a topic + audience prompt.

4 surfaces, one workspace

Tabs, typed cells, agent presence, audit log. All live.

What's inside

Pre-loaded so day one is execution.

4Surfaces
Surfaces
  • tableCalendar
  • docCalendar drafts
  • tableDistribution
  • docStatus
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>/content-calendar and follow the agent prompt.”

FAQ

Common questions on this template.

What does this content calendar template include?
Three surfaces: Calendar (table of planned posts with topic, channel, slot, status), Calendar drafts (a doc holding the actual draft text per piece), and Distribution (table of where each piece gets cross-posted).
How does this differ from a regular content calendar in Notion?
Drafts live as a doc, not buried in row cells, so they're properly editable. Distribution is its own surface so the cross-posting work doesn't fall through the cracks. And both humans and agents can write to all three surfaces in real time.
Can my writer agent draft into this template?
Yes. A common loop: Argus reads the Calendar for upcoming slots, drafts to Calendar drafts, marks the row 'ready for review'. Human reviews + edits in-place. On approve, Flint pushes the final version to the Distribution rows for cross-posting.

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.

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.