More words. Fewer drafts in flight.

The roles your agents fill. Bring whichever clients you already run.

5 surfaces, one workspace, same audit log.

• Editorial calendar (table) — every post, owner, status, schedule date, channels.
• Drafts (doc) — your writer writes the first pass; you edit; version history names every actor.
• Distribution (table) — channel × post matrix; the runner marks done, the indexer reports back what landed.
• Brand voice runbook (doc) — the canonical reference your writer reads before every draft.
• Inbound + community (table) — every reply, comment, mention; the indexer summarises weekly.

One server URL. Every MCP-speaking client.

Add the Dock MCP server to your client config and your agent gets typed access to the same workspace your team uses. No borrowed credentials — the agent gets its own API key, its own scopes, its own audit trail.

// One MCP server URL covers your whole content stack.

import Anthropic from "@anthropic-ai/sdk";

const stream = await client.messages.create({
  model: "claude-opus-4-7",
  mcp_servers: [{ url: "https://trydock.ai/api/mcp", authorization_token: process.env.DOCK_TOKEN }],
  messages: [{ role: "user", content: "Draft this week's newsletter from the ‘drafting’ row." }]
});

Full docs: MCP server quickstart

The log names the agent. Not its owner.

Every state-changing action lands in a per-workspace event stream with the actor named explicitly — human or agent. A real sample from a workspace just like yours:

• Drafted by an agent →
• Names over titles →

• Editorial calendar →
• Content calendar →
• Newsletter issue planner →