fix(ord): catalog MCP surfaces in ORD document (bump @cap-js/ord ^1.9.3) (#2249) - #2255
Merged
Merged
Conversation
…2249) @cap-js/ord 1.9.1 dropped protocols missing from its CAP→ORD protocol map, so the 5 MCP-enabled services never appeared in the generated ORD document. 1.9.2 added `mcp` to the map; 1.9.3 is the current patch. Verified via `cds compile srv --to ord`: apiResources now include 5 mcp entries (AdminService, DeveloperService, HomepageService, KnowledgeGraphService, SearchService) alongside odata-v4/graphql/rest, with no "Unknown protocol 'mcp'" warnings. Remaining websocket skips (DisplayService, EventStreamService) are expected — not an ORD protocol.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2249.
What
Bumps
@cap-js/ordfrom^1.9.1→^1.9.3.Why
The plugin was already integrated at 1.9.1 with
cds.ordconfig, but MCP surfaces were not being cataloged in the generated ORD document. 1.9.1 silently dropped any CAP protocol missing from its internal CAP→ORD protocol map, andmcpwas not in that map (only odata/rest/graphql/ina).@cap-js/ord1.9.2 addedmcpto the map; 1.9.3 is the current patch.This directly delivers part (a) of the issue — generating ORD API resources for OData, REST, GraphQL, MCP, and INA protocols.
Verification (TEST THE ACTUAL THING)
cds compile srv --to ordafter the bump — apiResources went from 25 → 30, with 5 newmcpentries:New
mcpapiResources:AdminService,DeveloperService,HomepageService,KnowledgeGraphService,SearchService. The prior "Unknown protocol 'mcp' is not supported, and skipped" warnings are gone. The only remaining skips arewebsocket(DisplayService, EventStreamService) — expected, as WebSocket is not an ORD protocol.Notes / out of scope
test/smoke/public-endpoints.test.jsremainit.skip("routes not active in production CSN") — a separate, pre-existing plugin-wiring investigation, not addressed here.cds buildgeneration (part c) from the issue are runtime/deploy concerns not exercised by this dependency bump.