Add the Claude Code plugin manifests

[00PrabalK00]

/plugin marketplace add 00PrabalK00/Continuum
/plugin install continuum@continuum

Claude Code reads a marketplace straight from a repository, so this needs no directory listing and nobody's approval. It registers the MCP server on install.

Verified, not assumed

The manifests parse, and speaking MCP to the exact command they declare answers:

initialize -> {'name': 'continuum', 'version': '0.13.0'}
tools -> 25
has record_claim: True | save_progress: True | ask_agent: True

Six tests, because manifests rot quietly

A manifest is only read by someone else's tool, so when it drifts nothing here fails: the version disagrees with the package, or the declared command gets renamed, and the first person to find out is a stranger whose install did nothing. The tests check the version against __version__, the marketplace entry against the plugin, and that continuum mcp serve is still a real subcommand.

What it does not replace

The plugin still needs continuum on PATH, since that is the command it runs. And it only covers Claude Code, so continuum install remains the way to reach Codex, Gemini and anything else. The README says both.

ChatGPT is not included and cannot be with this design: connectors there need a remote HTTP endpoint, and this is a local stdio server whose whole premise is that nothing leaves your machine.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 816794a4a7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[00PrabalK00]

You were right, and exercising the flow found the manifest did not work.

Claude Code reads MCP servers from .mcp.json at the plugin root. I had declared the server as an mcpServers key inside plugin.json, which is ignored. The plugin installed cleanly and registered nothing:

$ claude plugin details continuum@continuum
Component inventory
  Skills (0)
  MCP servers (0)

while the README said installing registers the server. Every test passed, because they compared my JSON against my own expectations and never against the tool that consumes it. That is exactly the gap you named.

Moved to .mcp.json, matching the layout the official plugins use. After reinstalling:

Component inventory
  MCP servers (1)  continuum

Verified with the real CLI rather than by reasoning about it: claude plugin validate . passes, then marketplace add ./, install continuum@continuum, and plugin details reports the server. The local marketplace was removed afterwards so nothing is left on the machine.

Two tests added for the specific shape that looked right and did nothing: the server must be declared in .mcp.json, and plugin.json must not carry an mcpServers key. 750 in the suite.

Worth noting what I still cannot test in CI: whether Claude Code accepts the manifest is only checkable where the claude CLI exists, so these tests guard the layout rather than the acceptance. I verified acceptance by hand and recorded the commands above so it can be repeated.