[feature] Page tools: support parentPageId and collection on create, plus update, move and reparent tools

[reyemb]

Summary

The current page tools (create_page, retrieve_page, list_pages) cannot reproduce a page hierarchy or place pages into a collection or teamspace, which makes bulk wiki migration into Plane or the general use of mcp impractical.

Current behaviour

create_page accepts name, description_html, project_id, access, color, is_locked, archived_at, view_props, logo_props, external_id and external_source. It does not accept:

1. parent_id (or parentPageId), so it cannot create subpages and everything lands at root.
2. a collection or teamspace id, so it cannot file a page into a collection.

There is also no update_page, delete_page or move_page tool, so structure cannot be fixed after creation either.

Concrete use case

Migrating an internal wiki (around 70 pages, 3 collections, two to three levels deep) from Docmost into Plane Pages. Content pushes fine, but hierarchy and collection placement cannot be set via MCP, forcing roughly 70 manual drag and nest operations in the UI.

Requested

1. parentPageId (and collection or teamspace id) params on create_workspace_page and create_project_page.
2. A move_page or reparent tool that can change parent and collection.
3. update_page and delete_page (overlaps with Add pages/ tools for projects and workspace #82, linking for context).

Related

1. Add pages/ tools for projects and workspace #82 (update page tools)
2. [feature]: Add API Endpoints for Creating and Editing Pages plane#7319 (page CRUD API endpoints)
3. GitHub markdown -> Plane Pages sync with public API support plane#8815 (Pages API including nested hierarchy)

Backend dependency

This likely needs the public Plane API to expose parent_id and collection on page create, plus a PATCH or move route first (see makeplane/plane#7319). Happy to test against the MCP server once available.