[
https://issues.apache.org/jira/browse/CAMEL-23852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-23852:
--------------------------------
Description:
h3. Background
The Camel MCP Server currently runs as a standalone JBang process:
{code:java}
jbang org.apache.camel:camel-jbang-mcp:LATEST:runner
{code}
This works for AI coding assistants that need catalog access, but there is no
{{camel mcp}} subcommand in the Camel CLI, and no way to run the MCP server
embedded inside a running Camel application.
The TUI already embeds an MCP server inside the running Camel process — the
same approach should be available for the MCP server so that a Camel
application can expose both the catalog tools and runtime introspection tools
through a single MCP server running inside the application.
h3. Proposal
*1. Add camel mcp CLI subcommand*
Add a proper {{camel mcp}} subcommand to the Camel CLI that starts the MCP
server. This makes the MCP server a first-class citizen in the CLI alongside
{{{}camel dev{}}}, {{{}camel run{}}}, {{{}camel trace{}}}, etc.
h3. Documentation update
The current documentation at camel-jbang-mcp.adoc should also be updated to:
* Document the {{camel mcp}} subcommand with usage examples
* Explain how to run the MCP server standalone vs embedded in a Camel
application
* Add a clear Getting Started section showing the simplest path: install
JBang, run {{{}camel mcp{}}}, connect an AI assistant
* Document the STDIO vs HTTP/SSE transport options with concrete examples for
each
was:
h3. Background
The Camel MCP Server currently runs as a standalone JBang process:
{code}
jbang org.apache.camel:camel-jbang-mcp:LATEST:runner
{code}
This works for AI coding assistants that need catalog access, but there is no
{{camel mcp}} subcommand in the Camel CLI, and no way to run the MCP server
embedded inside a running Camel application.
The TUI already embeds an MCP server inside the running Camel process — the
same approach should be available for the MCP server so that a Camel
application can expose both the catalog tools and runtime introspection tools
through a single MCP server running inside the application.
h3. Proposal
*1. Add camel mcp CLI subcommand*
Add a proper {{camel mcp}} subcommand to the Camel CLI that starts the MCP
server. This makes the MCP server a first-class citizen in the CLI alongside
{{camel dev}}, {{camel run}}, {{camel trace}}, etc.
*2. Support running MCP server embedded in a Camel application*
Similar to how the TUI runs embedded in the Camel process, allow the MCP server
to run inside a {{camel run}} or {{camel dev}} process. This enables AI agents
to interact with a running Camel application through MCP — accessing both
catalog tools and runtime introspection tools (routes, health, tracing, send,
etc.) from a single embedded server.
h3. Documentation update
The current documentation at camel-jbang-mcp.adoc should also be updated to:
* Document the {{camel mcp}} subcommand with usage examples
* Explain how to run the MCP server standalone vs embedded in a Camel
application
* Add a clear Getting Started section showing the simplest path: install JBang,
run {{camel mcp}}, connect an AI assistant
* Document the STDIO vs HTTP/SSE transport options with concrete examples for
each
> Add camel mcp CLI command
> -------------------------
>
> Key: CAMEL-23852
> URL: https://issues.apache.org/jira/browse/CAMEL-23852
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.22.0
>
>
> h3. Background
> The Camel MCP Server currently runs as a standalone JBang process:
> {code:java}
> jbang org.apache.camel:camel-jbang-mcp:LATEST:runner
> {code}
> This works for AI coding assistants that need catalog access, but there is no
> {{camel mcp}} subcommand in the Camel CLI, and no way to run the MCP server
> embedded inside a running Camel application.
> The TUI already embeds an MCP server inside the running Camel process — the
> same approach should be available for the MCP server so that a Camel
> application can expose both the catalog tools and runtime introspection tools
> through a single MCP server running inside the application.
> h3. Proposal
> *1. Add camel mcp CLI subcommand*
> Add a proper {{camel mcp}} subcommand to the Camel CLI that starts the MCP
> server. This makes the MCP server a first-class citizen in the CLI alongside
> {{{}camel dev{}}}, {{{}camel run{}}}, {{{}camel trace{}}}, etc.
> h3. Documentation update
> The current documentation at camel-jbang-mcp.adoc should also be updated to:
> * Document the {{camel mcp}} subcommand with usage examples
> * Explain how to run the MCP server standalone vs embedded in a Camel
> application
> * Add a clear Getting Started section showing the simplest path: install
> JBang, run {{{}camel mcp{}}}, connect an AI assistant
> * Document the STDIO vs HTTP/SSE transport options with concrete examples
> for each
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
