[
https://issues.apache.org/jira/browse/CAMEL-23639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18084212#comment-18084212
]
Karol Krawczyk commented on CAMEL-23639:
----------------------------------------
Hi [~zbendhiba] , I'd like to work on this.
I have a working implementation ready:
- .claude-plugin/marketplace.json at the repo root defining a camel-marketplace
- plugins/camel-mcp/ shipping the plugin manifest (.claude-plugin/plugin.json)
and a .mcp.json that
launches the server over STDIO via JBang
- docs: a new "Install as a plugin" subsection in camel-jbang-mcp.adoc, keeping
the manual .mcp.json
setup as an alternative
I tested it locally: Claude Code validates both manifests, the marketplace
loads, and the MCP server
starts via JBang and exposes all 27 tools.
One question for the maintainers: .mcp.json has to pin a released
camel-jbang-mcp version. I used
4.20.0 (latest on Maven Central; 4.21.0 isn't released yet), but this means the
file needs a bump on
each release — would it make sense to wire that into the release process?
I don't have permission to self-assign — could a committer please assign this
to me
([~kkrawczyk]) and/or add me to the project's Contributor role?
PR: https://github.com/apache/camel/pull/23613.
> Publish the Camel JBang MCP server as a Claude Code plugin
> ----------------------------------------------------------
>
> Key: CAMEL-23639
> URL: https://issues.apache.org/jira/browse/CAMEL-23639
> Project: Camel
> Issue Type: New Feature
> Reporter: Zineb Bendhiba
> Priority: Major
>
> The https://camel.apache.org/manual/camel-jbang-mcp.html[Camel JBang MCP
> server] [Camel JBang MCP
> server|https://camel.apache.org/manual/camel-jbang-mcp.html] currently
> requires users to manually edit their project's .mcp.json to add the JBang
> invocation. Claude Code 1.x added a[plugin
> system|[https://code.claude.com/docs/en/plugins.md]] where MCP servers can be
> packaged and installed from a marketplace. We could use this.
> Once the plugin is published, setup becomes two one-time commands:
> {code:java}
> $ claude plugin marketplace add apache/camel # (or whatever repo hosts
> the marketplace)
> $ claude plugin install camel-mcp@camel-marketplace
> {code}
> No more manual .mcp.json editing per project.
> What needs to be added to apache/camel:
> * A .claude-plugin/marketplace.json at the repo root:
> {code:java}
> {
> "name": "camel-marketplace",
> "owner": { "name": "Apache Camel" },
> "description": "Apache Camel plugins for Claude Code",
> "plugins": [
> {
> "name": "camel-mcp",
> "description": "Camel JBang MCP server: catalog lookups, route
> validation, error diagnosis",
> "source": { "source": "github", "repo": "apache/camel", "path":
> "plugins/camel-mcp" }
> }
> ]
> }{code}
> * A plugins/camel-mcp/.claude-plugin/plugin.json with plugin metadata, and a
> plugins/camel-mcp/.mcp.json with the server config:
> {code:java}
> {
> "mcpServers": {
> "camel": {
> "command": "jbang",
> "args": ["-Dquarkus.log.level=WARN",
> "org.apache.camel:camel-jbang-mcp:LATEST:runner"]
> }
> }
> }{code}
> Note: Users still need JBang installed. The installation page should say so
> clearly.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
