[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:

GET  /api/v1/workspaces/{slug}/projects/{project_id}/pages/
POST /api/v1/workspaces/{slug}/projects/{project_id}/pages/
GET  /api/v1/workspaces/{slug}/pages/

Note: the public API reference (developers.plane.so) lists "List/Add Project Pages" and "List/Add Workspace Pages" under a Pages section, which implies these are meant to be public — but they aren't shipped to /api/v1/. So either the docs are ahead of the release, or the endpoints were never wired into the token API.

Request: expose Pages in the public REST API (list / create / get / update, both project- and workspace-scoped) with API-token auth, consistent with the other resources.

2. An official MCP server would be great

An official Model Context Protocol server for Plane would let AI assistants/agents manage Plane (work items, cycles, modules, and — once available — pages) natively over a token. Some tools in this space now ship a first-party /mcp endpoint; a native Plane MCP would make Plane a first-class citizen for agent-driven workflows.

Environment

• Self-hosted community, APP_RELEASE=v1.4.0-rc2 (also reproduced on stable)
• Auth: workspace API token (X-API-Key)

Why should this be worked on?

1. Pages are missing from the public (token) REST API

2. An official MCP server would be great

An official Model Context Protocol server for Plane would let AI assistants/agents manage Plane (work items, cycles, modules, and — once available — pages) natively over a token. Some tools in this space now ship a first-party /mcp endpoint; a native Plane MCP would make Plane a first-class citizen for agent-driven workflows.