[ 
https://issues.apache.org/jira/browse/CAMEL-26355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-26355 started by Ramu.
------------------------------------
> camel-ai-prompt - new component: MCP prompts from Camel routes
> --------------------------------------------------------------
>
>                 Key: CAMEL-26355
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26355
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ai, camel-mcp-server
>            Reporter: Claus Ibsen
>            Assignee: Ramu
>            Priority: Major
>             Fix For: 4.24.0
>
>
> {{camel-mcp-server}} serves tools ({{ai-tool}}) and resources 
> ({{ai-resource}}), but not prompts. An MCP prompt is a template a user picks 
> in the client, for example "summarize account 42". It is listed by 
> {{prompts/list}} and fetched by {{prompts/get}} with arguments.
> h3. Proposal
> A new {{ai-prompt}} consumer that works like {{ai-resource}}.
> * Options:
> ** {{description}} and {{title}};
> ** the argument names, each with a description and whether it is required;
> ** {{tags}}, for the same opt-in selection as tools and resources.
> * The route gets the arguments, which are always strings in MCP. Its body 
> becomes the messages:
> ** a String is one {{user}} message;
> ** a {{List}} gives several messages, each a String (user) or a map with 
> {{role}} ({{user}} or {{assistant}}) and {{content}}. The content is a String 
> or an MCP content block.
> * A missing required argument is an argument error. Route exceptions are 
> hidden, as for tools, and the bridge applies a per-call timeout.
> * The Camel Main engine serves prompts over Vert.x HTTP and stdio, and sends 
> {{notifications/prompts/list_changed}}.
> * Opt-in on the SPI ({{supportsPrompts()}}).
> * The component goes under {{camel-ai}}, so it needs a MojoHelper entry, 
> catalog regeneration and a docs page.
> The Camel Main and Camel JBang engine is the reference implementation and 
> gets the complete feature; the Spring Boot and Quarkus engines follow in a 
> separate parity ticket, which does not block this one.
> _Filed by Claude Code on behalf of davsclaus_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to