Repository navigation
feat: Claude Code plugin and MCP Registry listing - #1772
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 inplugins/codeburn:npx -y codeburn mcp, toolsget_usageandget_savings);/codeburn:cost, a skill that runsnpx -y codeburn todayand 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, becausefilesonly includesdist.MCP Registry.
server.jsondescribes the npm package for the official registry, underio.github.getagentseal/codeburn.package.jsongets the matchingmcpName, 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 inserver.json, thenmcp-publisher publish.Checked:
claude plugin validate .andclaude plugin validate ./plugins/codeburn --strictboth pass;server.jsonvalidates against the 2025-12-11 registry schema with no errors;codeburn mcpanswers the MCP handshake and lists both tools;/codeburn:costran end to end in a headless Claude Code session with--plugin-dir.