[
https://issues.apache.org/jira/browse/CAMEL-23705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104033#comment-18104033
]
Karol Krawczyk commented on CAMEL-23705:
----------------------------------------
I looked into this before picking it up, and the premise no longer holds — I
think this issue can be closed, or re-scoped to the one thing that genuinely is
unpublished.
h3. The marketplace is already set up
{{.claude-plugin/marketplace.json}} has been on {{main}} since 0624c536492a
(CAMEL-23639, PR #23613), merged on 30 May 2026 — a week before this issue was
filed. Together with {{plugins/camel-mcp/.claude-plugin/plugin.json}} and
{{plugins/camel-mcp/.mcp.json}}, that is the complete set of files a
marketplace needs.
h3. There is no registration step to perform
The issue assumes the {{apache/camel}} marketplace has to be "registered in
Claude's plugin system". No such step exists. Per the [marketplace
documentation|https://code.claude.com/docs/en/plugin-marketplaces], hosting a
marketplace means pushing {{marketplace.json}} to a git repository; {{plugin
marketplace add <owner>/<repo>}} resolves any git repository containing
{{.claude-plugin/marketplace.json}} directly, with no involvement from
Anthropic.
h3. Verified against Claude Code 2.1.228
{code}
$ claude plugin validate . -> Validation passed
$ claude plugin validate ./plugins/camel-mcp -> Validation passed
$ claude plugin marketplace add apache/camel -> Successfully added
marketplace: camel-marketplace
$ claude plugin install camel-mcp@camel-marketplace -> Successfully installed
plugin (scope: user)
$ claude plugin list ->
camel-mcp@camel-marketplace, version 0.1.0, enabled
{code}
Both commands in the documentation work today, unchanged. Note that
{{marketplace add}} clones from GitHub rather than reading a local checkout, so
this exercises the published state of {{main}}, not a working copy. The
installed plugin reports the version from {{plugin.json}} and registers the
{{camel}} MCP server from {{plugins/camel-mcp/.mcp.json}} as documented. I
uninstalled the plugin and removed the marketplace afterwards.
h3. One real drawback: repository size
Adding the marketplace shallow-clones the whole Camel monorepo in order to
deliver four small files:
{code}
414M ~/.claude/plugins/marketplaces/camel-marketplace (63M of it .git)
{code}
This cannot be fixed from inside {{apache/camel}} — the marketplace source is
the repository, so every user pays for a full checkout. The only way around it
would be a separate, small repository (something like
{{apache/camel-claude-plugins}}), which is an INFRA request and a PMC decision
rather than a code change. Worth weighing against the convenience of keeping
the plugin next to the code it describes.
h3. What actually is unpublished
There is an Anthropic-managed directory,
[anthropics/claude-plugins-official|https://github.com/anthropics/claude-plugins-official],
with an {{external_plugins}} section for third parties. Its README states that
third-party plugins can be submitted for inclusion, must meet quality and
security standards, and are submitted through a plugin directory submission
form (https://clau.de/plugin-directory-submission). Being listed there is what
would make the Camel MCP server discoverable through {{/plugin > Discover}},
rather than requiring users to know the {{apache/camel}} coordinates.
That is a form submission on behalf of the project, not a patch, so it should
come from someone representing the PMC rather than from a contributor via a
pull request.
h3. Suggested disposition
Either close this as Not A Problem, since the documented install path works as
written, or narrow it to "submit the Camel MCP server to the official Claude
Code plugin directory" and assign it to someone who can submit on behalf of the
project. The repository-size question is separable and could be its own issue
if there is appetite for a dedicated plugin repository.
[~davsclaus] since you reported it — happy to do the work either way, but as it
stands there is nothing here for me to implement.
_Reported by Claude Code on behalf of Karol Krawczyk_
> Publish Camel MCP Server to the Claude Code plugin marketplace
> --------------------------------------------------------------
>
> Key: CAMEL-23705
> URL: https://issues.apache.org/jira/browse/CAMEL-23705
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
>
> The Camel MCP Server (camel-jbang-mcp) documentation at
> https://camel.apache.org/manual/camel-jbang-mcp.html references Claude Code
> marketplace install commands:
> {code}
> claude plugin marketplace add apache/camel
> claude plugin install camel-mcp@camel-marketplace
> {code}
> However, the marketplace has not been set up yet. The {{apache/camel}}
> marketplace is not registered in Claude's plugin system, so users must fall
> back to manual {{.mcp.json}} configuration.
> Publishing to the Claude Code marketplace would allow users to install the
> Camel MCP Server with two simple commands instead of manually configuring
> JBang args and server settings.
> See: https://docs.anthropic.com/en/docs/claude-code/plugins for marketplace
> publishing details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
