[
https://issues.apache.org/jira/browse/CAMEL-26364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133421#comment-18133421
]
Claus Ibsen edited comment on CAMEL-26364 at 10/28/26, 6:24 AM:
----------------------------------------------------------------
Not part of this PR: renaming the Claude Code plugin {{camel-mcp}} to
{{camel-cli-mcp}}. This plugin, in {{plugins/camel-mcp}}, launches the same
{{camel-jbang-mcp}} server, so {{camel-mcp}} is a third name for it. These are
the effects of renaming it.
*What changes*
* {{.claude-plugin/marketplace.json}}: the plugin name and source path, plus
the {{plugins/camel-mcp}} directory and {{plugin.json}}.
* {{camel-jbang-mcp.adoc}}: the install command {{claude plugin install
camel-mcp@camel-marketplace}}.
*Who is affected*
* Claude Code users who installed {{camel-mcp@camel-marketplace}}. The
marketplace is read from {{main}} of apache/camel ({{claude plugin marketplace
add apache/camel}}), not from a release. After the rename the marketplace no
longer lists {{camel-mcp}}, so their copy stops getting updates. They have to
uninstall it and install {{camel-cli-mcp}}.
* The tools of a plugin's MCP server carry the plugin name in their tool names
in Claude Code. Allow or deny rules in a user's {{settings.json}} that name the
old tools stop matching, and the user is asked for permission again.
* The plugin has shipped since 4.21.0, including the 4.22 LTS, and the manual
of each of those releases documents {{claude plugin install
camel-mcp@camel-marketplace}}. The 4.22 LTS manual stays on the website for the
whole LTS period, so either the camel-4.22.x branch docs get the new command
too, or {{marketplace.json}} keeps a {{camel-mcp}} entry until 4.22 reaches end
of life, with a description that says it was renamed. Installing both plugins,
though, gives the agent every tool twice.
*Not affected*
* The Maven artifact {{camel-jbang-mcp}}, the {{camel mcp}} command, and the
{{-runner}} jar.
* MCP configurations written by hand for other tools (Cursor, VS Code,
JetBrains, Claude Desktop) and the {{camel}} server key in them.
*Assessment*
The name only shows in the install command and the plugin list, so the rename
gains little and breaks existing installs. The plugin is already in an LTS
release, so renaming it now costs more than it would have before 4.21. If we do
it anyway, update the camel-4.22.x docs as well and add a note to the 4.24
upgrade guide.
_Claude Code on behalf of davsclaus_
was (Author: davsclaus):
Not part of this PR: renaming the Claude Code plugin {{camel-mcp}} to
{{camel-cli-mcp}}. This plugin, in {{plugins/camel-mcp}}, launches the same
{{camel-jbang-mcp}} server, so {{camel-mcp}} is a third name for it. These are
the effects of renaming it.
*What changes*
* {{.claude-plugin/marketplace.json}}: the plugin name and source path, plus
the {{plugins/camel-mcp}} directory and {{plugin.json}}.
* {{camel-jbang-mcp.adoc}}: the install command {{claude plugin install
camel-mcp@camel-marketplace}}.
*Who is affected*
* Claude Code users who installed {{camel-mcp@camel-marketplace}}. The
marketplace is read from {{main}} of apache/camel ({{claude plugin marketplace
add apache/camel}}), not from a release. After the rename the marketplace no
longer lists {{camel-mcp}}, so their copy stops getting updates. They have to
uninstall it and install {{camel-cli-mcp}}.
* The tools of a plugin's MCP server carry the plugin name in their tool names
in Claude Code. Allow or deny rules in a user's {{settings.json}} that name the
old tools stop matching, and the user is asked for permission again.
* The 4.23 manual on the website keeps the old install command, which then
fails because 4.23.0 already shipped {{marketplace.json}}. An alternative is to
keep a {{camel-mcp}} entry for one release and say in its description that it
was renamed. Installing both plugins, though, gives the agent every tool twice.
*Not affected*
* The Maven artifact {{camel-jbang-mcp}}, the {{camel mcp}} command, and the
{{-runner}} jar.
* MCP configurations written by hand for other tools (Cursor, VS Code,
JetBrains, Claude Desktop) and the {{camel}} server key in them.
*Assessment*
The name only shows in the install command and the plugin list, so the rename
gains little and breaks existing installs. If we do it, do it before 4.24.0,
while the plugin is new (version 0.1.0, added 2026-10-09), and add a note to
the 4.24 upgrade guide.
_Claude Code on behalf of davsclaus_
> Docs - tell the Camel CLI MCP server and the camel-mcp-server component apart
> -----------------------------------------------------------------------------
>
> Key: CAMEL-26364
> URL: https://issues.apache.org/jira/browse/CAMEL-26364
> Project: Camel
> Issue Type: Improvement
> Components: documentation
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Two different things are both called "MCP Server" in the docs:
> * camel-mcp-server (component mcp-server): exposes the ai-tool / ai-resource
> routes of your own integration as MCP tools and resources.
> * camel-jbang-mcp ({{camel mcp}}): the developer tool that gives an AI coding
> assistant Camel knowledge (catalog, validation, runtime tools). Its manual
> page is titled "Camel MCP Server", which reads like the camel-mcp-server
> artifact.
> Neither page links to the other.
> Fix (docs only, no artifact renames):
> # Retitle the manual page camel-jbang-mcp.adoc to "Camel CLI MCP Server" and
> update the nav entry and xref labels (the file name stays, so no links break).
> # Add a note at the top of both pages that points to the other one.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
