Free for 30 days on Scale.Start free
Build9 steps1-2 weeks (most of it the first review + permission justifications)

Ship a Chrome extension to the Web Store

Your Chrome extension live in the Chrome Web Store with a working listing, MV3 manifest, accurate permission justifications, and a clean review history so updates clear in days.

Open in DockSee every step →

Your Chrome extension live in the Chrome Web Store with a working listing

Your Chrome extension live in the Chrome Web Store with a working listing, MV3 manifest, accurate permission justifications, and a clean review history so updates clear in days.

Spin up an agent for the heavy lifting

Reads the codebase to surface every API, permission, and host the extension actually uses so justifications match reality.

9 steps, 20 official links, 2 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
9Steps
2Agent prompts
20Official links
5Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docWeb Store launch plan
  • tableSubmission log
  • 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>/ship-a-chrome-extension and follow the agent prompt.”

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

Common questions on this template.

How long does Chrome Web Store review take?
First submissions: 1-7 days, sometimes 14+ if reviewers flag it for human review (high-permission extensions, single-purpose ambiguity, remote-code suspicion). Subsequent updates from a clean account: a few hours to a couple of days. Updates on flagged accounts can take as long as the first review.
What gets first-time Chrome extensions rejected?
The top three: (1) vague or missing per-permission justifications, especially host_permissions and tabs / scripting, (2) missing privacy policy URL when the extension touches any user data, (3) Single Purpose violations (an extension that does too many unrelated things). Read the cited policy paragraph in the rejection email.
Can I charge for a Chrome extension?
The Chrome Web Store stopped processing paid extensions in 2020. The extension itself is free; you handle billing in your own backend (Stripe / Lemon Squeezy / your auth flow). Many extensions ship a free tier + login for a paid tier.
Can my AI agents help with the extension submission?
Yes. Agents are particularly useful for: auditing manifest.json + source to draft accurate per-permission justifications, drafting the listing description, drafting the privacy policy from a data audit, and triaging review responses on rejection. The template ships agent prompts inline.
What does shipping a Chrome extension cost?
$5 one-time developer registration fee. The Web Store does not charge listing fees, transaction fees, or annual fees. Hosting your own backend (if any) is your own cost. No revenue share applies because the Web Store doesn't process payments.
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.