[feature]: Public (token) REST API is missing Pages endpoints; request for an official MCP server

Is there an existing issue for this? • I have searched the existing issues Summary 1. Pages are missing from the public (token) REST API The public API (/api/v1/..., X-API-Key) fully covers projects, work items, cycles, modules, labels, states, members, etc. — but not Pages. In the deployed backend code, the page routes live only in the internal app API (plane/app/urls/page.py, session/cookie auth). The public API package (plane/api/urls/) has no page module — its URL modules are: asset, cycle, estimate, intake, invite, label, member, module, project, schema, state, sticky, user, work_item. Result: an integration or automation authenticating with a workspace API token can create and manage issues, cycles, modules and labels, but cannot create / list / update Pages — even though the UI exposes Pages prominently. Programmatic knowledge-base management is impossible. Concretely, these all return 404 {"error": "Page not found."} with a valid X-API-Key: …