[
https://issues.apache.org/jira/browse/CAMEL-22886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053465#comment-18053465
]
Christoph Deppisch commented on CAMEL-22886:
--------------------------------------------
Awesome idea! AI code assistance tools running in your Java IDE can easily make
use of the tools exposed by the Camel MCP server. Great!
[~Federico Mariani] I think users may just run the MCP server locally (e.g. via
Camel JBang) instead of using a shared MCP server instance running on Apache
infra. Running the server locally on demand makes sense, because it provides
tools that expose information about locally running Camel integrations.
We can think of a separate Camel JBang command to run the MCP server locally
(something like {_}camel mcp start{_}) or we add some flag to the _camel run_
command to enable the MCP server capabilities when running an integration
(something like {_}camel run route.yaml --mcp-dev{_}).
> Camel-Jbang: Add an MCP module
> ------------------------------
>
> Key: CAMEL-22886
> URL: https://issues.apache.org/jira/browse/CAMEL-22886
> Project: Camel
> Issue Type: New Feature
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.x
>
>
> We could add an MCP server based on camel-jbang CLI
> We could select what command to expose and how, in general it would be
> interesting to provide this stuff as part of a way of exposing the feature we
> have in the CLI and make it consumable in a standard and friendly way.
> I would probably go with the Java MCP SDK or quarkus mcp.
> What are your idea on this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
