feat: enable catalog-pages GET endpoints in MCP

[jeff-schnitter]

Summary

• Adds listCatalogPages (GET /api/v1/catalog-pages) and getCatalogPage (GET /api/v1/catalog-pages/{slug}) as MCP tools by setting x-cortex-mcp-enabled: true on their GET operations in swagger.json
• Adds the CatalogPage and CatalogPageListResponse schemas they depend on

Context

Per product request, all public GET APIs should be accessible via MCP. This wires up the newly-added catalog-pages API endpoints.

Test plan

• Confirm listCatalogPages and getCatalogPage appear in tool list when server starts
• Call listCatalogPages via MCP and verify it returns catalog data
• Call getCatalogPage with a valid slug and verify it returns the correct catalog

🤖 Generated with Claude Code

[keithfz]

@jeff-schnitter it might make sense to do a full regen rather than a targeted one, i think this might be out of date with some other changes i recently made to the api specs

[ashiramin]

We really should have this automated cuz this annoying and painful to do

[jeff-schnitter]

@keithfz - yep, I see it now. The real change here should be in brain-backend to enable the MCP on the API methods:

@MCPFeature(enabled = true)

Then pull openapi.json from cortexapps/schemas.

Since the build of the openapi is automated we just need one more step to push to this repo and cortexapps/brainpower (our new docs repo) while we're at it.