[
https://issues.apache.org/jira/browse/CAMEL-23056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060349#comment-18060349
]
Claus Ibsen commented on CAMEL-23056:
-------------------------------------
Or do you mean to only generate?
rest().openApi().specification("xxxx.json");
That is usually all it takes. But it can also generate routes that are linked
via direct:operationId for each API in the spec file. Then the end user can
continue from these routes to implement what they are supposed to do
> Camel JBang MCP - Add contract-first OpenAPI REST DSL support tools
> --------------------------------------------------------------------
>
> Key: CAMEL-23056
> URL: https://issues.apache.org/jira/browse/CAMEL-23056
> Project: Camel
> Issue Type: Task
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.19.0
>
>
> Add MCP tools to the camel-jbang-mcp server that help AI agents guide users
> through the contract-first REST DSL approach (introduced in Camel 4.6), where
> the OpenAPI spec is referenced directly at runtime rather than generating
> code.
> 1. camel_openapi_validate — Validate an OpenAPI spec against Camel support
> Parse an OpenAPI 3.x spec and report:
> - Unsupported features (e.g., WebSockets from OpenAPI 3.1, security schemes
> not currently used by Camel)
> - Missing operationId fields (required for direct: routing)
> - Schema or structural issues that would cause runtime failures
> - Warnings for features Camel will silently ignore
> 2. camel_openapi_scaffold — Scaffold direct: route stubs for each operationId
> Given an OpenAPI spec, generate the contract-first YAML with route stubs:
> - The rest.openApi block referencing the spec
> - A direct: route for each operationId in the spec
> - Correct Content-Type headers based on the spec's produces/consumes
> - Appropriate HTTP response codes from the spec's responses
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
