Internal engineering marketplace
A private Claude Code marketplace for Seatfrog engineering — MCP servers, domain skills, agents and workflow automation. Merge to main, and the catalogue publishes and updates itself.
| Plugin | Version | Category | Channel |
|---|
Github → npm → edge
There's no manual publish step. A version bump merged to main rides the line end-to-end — build, publish, discover, install — with no tokens stored anywhere along the way.
The consumable marketplace at deploy.seatfrogpages.com/api/marketplace.json is a Cloudflare Worker that discovers the catalogue live from the npm registry — it lists the @seatfrog org, keeps every package tagged claude-code-plugin, and builds each entry from the claudePlugin block the publisher embeds.
Bootstrap-publish a package once and it appears in the catalogue within ~5 minutes — zero Worker changes per plugin. The result is edge-cached for 300s, and if the registry ever blips a static seed catalogue keeps installs working. (npm's push webhooks were sunset in 2024, so discovery is pull-based by design — see seatfrog-pages#1.)
The catalogue
Install from the seatfrog-tools marketplace in Claude Code. Two of these also ship to private npm for staff without GitHub access.
Before you install
Most plugins are pure skills and need nothing but Claude Code. The MCP servers and a few workflow plugins want the tools below. Each plugin card above lists exactly what it needs.
Getting started
Add the marketplace, then install any plugin. Requires GitHub access to the repo.
Drop this in a repo's .claude/settings.json so teammates are prompted to install on open.
No GitHub access needed. The npm-distributed plugins (seatfrog-mcp, zendesk-mcp) install straight from the auto-discovered catalogue.
Or run the guided browser setup at deploy.seatfrogpages.com/setup.
Add the name to PUBLISH_PLUGINS in publish.py, do a one-off bootstrap publish, then wire the trusted publisher on npmjs. After that, version bumps ship automatically.