Plugins

Plugins are Claude Code plugin packages that configure MCP (Model Context Protocol) servers. They give Bucky access to external tools like Sourcegraph, Grafana, Rollbar, and PostHog during Claude sessions.

Plugin structure

Each plugin lives in plugins/<name>/ and contains:

plugins/<name>/
├── .claude-plugin/
│   └── plugin.json      # Metadata (name, version, description)
├── .mcp.json             # MCP server configurations
└── README.md             # Plugin documentation

The repository acts as a plugin_marketplaces source for the anthropics/claude-code-action GitHub Action.

Available plugins

`common/`

Core tools included in every preset.

MCP Servers: Sourcegraph, Grafana, Rollbar
Required env vars: SOURCEGRAPH_TOKEN, ROLLBAR_TOKEN

Provides code search across all repos (Sourcegraph), observability dashboards and metrics (Grafana), and error tracking (Rollbar).

`web/`

Frontend-specific tools. Included in the web preset.

MCP Servers: PostHog
Skills: playwright-cli for interactive browser automation
Required env vars: POSTHOG_TOKEN

Provides product analytics (PostHog) and browser automation capabilities for visual testing, screenshot capture, and form interactions.

`golang/`

Go-specific tools. Included in the golang preset.

MCP Servers: None (language server provided by gopls-lsp from official plugins)
Required env vars: None

Official plugins

In addition to buck-bronson plugins, workflows register the official Claude plugins marketplace:

Plugin	Marketplace	Preset
`typescript-lsp`	`claude-plugins-official`	`web`
`frontend-design`	`claude-plugins-official`	`web`
`gopls-lsp`	`claude-plugins-official`	`golang`

These provide language server protocol support and specialized capabilities for their respective ecosystems.

Updating a plugin

Push changes to plugins/<name>/ on main
Consuming repos pick up changes on the next workflow run (plugins are fetched fresh each time)
For local development: claude plugin update <name>@buck-bronson

Plugin versioning

Plugins that contain skills use the version field in .claude-plugin/plugin.json to track changes. When modifying any file in a skill-based plugin (skill content, .mcp.json, README), bump the patch version in that plugin’s plugin.json as part of the same change.