Skip to content

feat: Claude Code plugin and MCP Registry listing - #1772

Merged
iamtoruk merged 1 commit into
mainfrom
feat/mcp-registry-plugin
Oct 20, 2026
Merged

iamtoruk merged 1 commit into
mainfrom
feat/mcp-registry-plugin

Conversation

@iamtoruk

Copy link
Copy Markdown
Member

Puts CodeBurn where people set up their AI agents.

Claude Code plugin. This repo becomes a plugin marketplace (.claude-plugin/marketplace.json) with one plugin in plugins/codeburn:

  • it registers the existing MCP server (npx -y codeburn mcp, tools get_usage and get_savings);
  • it adds /codeburn:cost, a skill that runs npx -y codeburn today and has Claude summarize today's spend in five bullets. Claude can also use it on its own when someone asks what they spent.

Install: /plugin install codeburn --marketplace getagentseal/codeburn (added to the README's "Inside your agent" section). Neither folder ships in the npm package, because files only includes dist.

MCP Registry. server.json describes the npm package for the official registry, under io.github.getagentseal/codeburn. package.json gets the matching mcpName, which the registry uses to check that we own the package. That check reads the published package, so the listing can go live only after the next npm release. RELEASING.md now has that step: bump both versions in server.json, then mcp-publisher publish.

Checked:

  • claude plugin validate . and claude plugin validate ./plugins/codeburn --strict both pass;
  • server.json validates against the 2025-12-11 registry schema with no errors;
  • codeburn mcp answers the MCP handshake and lists both tools;
  • /codeburn:cost ran end to end in a headless Claude Code session with --plugin-dir.

@iamtoruk
iamtoruk merged commit 360a9e2 into main Oct 20, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant