Skip to content

docs: correct the plugin install steps in the README - #23

Merged
stormcat24 merged 1 commit into
mainfrom
docs/plugin-install-notes
Jul 20, 2026
Merged

docs: correct the plugin install steps in the README#23
stormcat24 merged 1 commit into
mainfrom
docs/plugin-install-notes

Conversation

@stormcat24

Copy link
Copy Markdown
Member

Verified the plugin install path end to end on a real machine and found three places the README was off.

  • Restart is not required. /reload-plugins registers the MCP server in the running session. The README said to restart Claude Code. Added claude mcp list as the confirmation step, along with the name the entry takes (plugin:ctxpack:ctxpack).
  • Double registration is easy to hit. Installing the plugin and running claude mcp add ctxpack registers the same server twice, so the agent sees two of every tool. Called out that the two paths are alternatives. Also noted that plugin-provided tools are named mcp__plugin_ctxpack_ctxpack__pack, not mcp__ctxpack__pack — permission rules have to match that.
  • The CTXPACK_BIN troubleshooting step had no exit for plugin users. It told the reader to add an env block to .mcp.json, but the plugin's config ships inside this repository and the user has no copy to edit. Points at the process environment or manual registration now.

Also added the -s user variant of claude mcp add, since registering once for every project is the common case.

Docs only — no code, no config changes. Plugin manifests were checked and are correct as-is: the marketplace name nandemo-ya and plugin name ctxpack match the documented /plugin install ctxpack@nandemo-ya, and the two version fields agree at 0.1.0.

🤖 Generated with Claude Code

Installing the plugin does not need a Claude Code restart; /reload-plugins
registers the server in the running session. Name it, along with the
`claude mcp list` entry that confirms the result.

Add the two things a first install trips over: installing the plugin and
running `claude mcp add` registers the same server twice, and the plugin
exposes its tools under `mcp__plugin_ctxpack_ctxpack__*`, which permission
rules have to match.

The CTXPACK_BIN troubleshooting step told the reader to edit an `env` block
that a plugin install gives them no copy of. Point at the environment or at
manual registration instead.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@stormcat24
stormcat24 merged commit c3a64e2 into main Jul 20, 2026
7 checks passed
@stormcat24
stormcat24 deleted the docs/plugin-install-notes branch July 20, 2026 07:38
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