[
https://issues.apache.org/jira/browse/CAMEL-22302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023755#comment-18023755
]
Otavio Rodolfo Piske commented on CAMEL-22302:
----------------------------------------------
I think this doesn't need to be within the Camel component after the
refactoring. Clients can provide their own Agent or AgentFactory instance which
can provide it, so it would help us couple too tightly w/ LangChain4j.
> camel-langchain4j-agent : add MCP Tool Pro
> ------------------------------------------
>
> Key: CAMEL-22302
> URL: https://issues.apache.org/jira/browse/CAMEL-22302
> Project: Camel
> Issue Type: New Feature
> Components: camel-ai
> Reporter: Zineb Bendhiba
> Assignee: Zineb Bendhiba
> Priority: Major
>
> The AIService created in the LangChain4j component is missing the MCP client
> feature.
> I propose that we can add that feature.
> +Many idea :+
> Create a dedicated MCP Tool Provider, based on a given JSON configuration.
> Example of what I imagine as JSON configuration file, presenting both stdio
> and HTTP transport types :
> {code:java}
> {
> "mcpServers": {
> "sqlite": {
> "type": "stdio",
> "command": [
> "/usr/bin/npm",
> "exec",
> "@modelcontextprotocol/[email protected]"
> ],
> "logEvents" : true
> },
> "wanaku": {
> "type": "http",
> "sseUrl": "http://localhost:8080/mcp/sse";,
> "logRequests" : true,
> "logResponses" : true
> }
> }
> }
> {code}
> Based on this list, create
> [McpTransport|https://docs.langchain4j.dev/tutorials/mcp#mcp-transport]
> beans, that from that a List of [MCP
> Client|https://docs.langchain4j.dev/tutorials/mcp#mcp-client] beans.
> With the MCP Client List, one can create a ToolProvider that could be used by
> our AIServiceAgent. See
> [documentation|https://docs.langchain4j.dev/tutorials/mcp#developing-the-tool-provider].
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
