Claude Code plugin

The Bridge Town plugin packages everything Claude Code needs to work with your models:

Component	What it adds
MCP server	The bridge-town server at https://api.bridgetown.builders/mcp, signed in with OAuth. No API token.
Skills	working-with-bridge-town (tool discovery, sandbox rules, how results are displayed) plus 19 workflow skills: revenue, expense, headcount, cash flow, unit economics, usage-based pricing and marketplace GMV models; scenario analysis; native sheets; Google Sheets; Excel conversion; dashboards; data discovery; collaboration.
Agent	model-reviewer runs the base and changed versions of a model branch or pull request, compares the runs, and reports findings without merging anything.
Command	/bridge-town:status checks the connection and summarizes recent runs.
Guardrail	Claude Code asks you to confirm before any delete, rollback, merge, sharing change, or Google Sheet publish.

Skills load only when a task needs them, so the plugin adds detailed guidance without adding to every conversation’s context. Use the plugin when you work in Claude Code. If you use Bridge Town from Claude.ai, see Connecting Claude.ai.

Bridge Town is bring-your-own-agent. Claude Code is your chosen AI client: your configured model provider processes the conversation under your agreement with that provider. Bridge Town does not invoke server-side language models; the plugin’s skills and agent run inside Claude Code and call Bridge Town’s MCP tools with the access you grant.

Install

In Claude Code, add the Bridge Town marketplace and install the plugin:

/plugin marketplace add Bridge-Town/claude-plugins
/plugin install bridge-town@bridge-town

Or from a terminal:

claude plugin marketplace add Bridge-Town/claude-plugins
claude plugin install bridge-town@bridge-town

Sign in

1. Run /mcp, select bridge-town, and choose Authenticate.
2. Sign in to Bridge Town in the browser tab that opens and approve access.
3. Back in Claude Code, run /bridge-town:status.

If you have already connected Bridge Town on Claude.ai with the same account, Claude Code uses that connection, and the plugin’s skills, agent and guardrails apply to it. You do not need to sign in again.

Use it

Ask for the outcome; Claude picks the matching skill:

Build a three-year headcount model for our engineering and sales teams in the fy27-plan model.

Create an upside scenario branch with 15% faster ARR growth and compare it to main.

Review the open pull request on fy27-plan before I merge it.

You can also invoke a skill directly, for example /bridge-town:create-revenue-model.

Roll out to a team

Administrators can make the plugin available to everyone through Claude Code managed settings:

{
  "extraKnownMarketplaces": {
    "bridge-town": {
      "source": { "source": "github", "repo": "Bridge-Town/claude-plugins" }
    }
  },
  "enabledPlugins": {
    "bridge-town@bridge-town": true
  }
}

Each person still signs in with their own Bridge Town account, so workspace roles and permissions apply as usual.

Update or remove

claude plugin marketplace update bridge-town
claude plugin uninstall bridge-town@bridge-town

Token-based setup

If you need a non-interactive connection (CI, a remote shell without a browser), skip the plugin’s sign-in and add the server with a workspace API token as described in Connecting Claude Code.

Troubleshooting

bridge-town shows “needs authentication” in /mcp

• Choose Authenticate and complete the browser sign-in.

You added Bridge Town earlier with claude mcp add

• That connection keeps working, and the plugin’s skills, agent and guardrails apply to it. To switch to OAuth sign-in instead of a token, remove it with claude mcp remove bridge-town and authenticate the plugin’s server.

A delete or merge asks for confirmation even though you allowed it

• This is intended. The plugin’s guardrail asks before irreversible or sharing actions regardless of other permission settings.