feat: Notion Bridge — Page move between workspaces (notion_write_move_page)

[Delqhi]

Enhancement Request

Add notion_write_move_page tool to the Notion MCP bridge for moving pages between workspaces or within the same workspace.

API Capability

The Notion API supports PATCH /v1/pages/{page_id} with parent field to move pages:

{
  "parent": {
    "type": "page_id",
    "page_id": "new-parent-id"
  }
}

Requirements

• Move pages between workspaces (if permissions allow)
• Move pages within the same workspace
• Preserve all block content and properties
• Follow Bridged-External pattern (M6)
• Permission: ask (destructive move)

Acceptance Criteria

• Tool moves pages via vibe-notion raw API
• Cross-workspace moves supported
• Intra-workspace moves supported
• Content preserved after move
• Tests pass with go test -race
• CHANGELOG.md + AGENTS.md updated

References

• Notion API: https://developers.notion.com/reference/update-a-page
• Related: issue feat: Notion Bridge — In-place block editing (notion_write_update_block) #495 (in-place editing)

[Delqhi]

Deep Research: Notion API Page Moving

API Capability (Verified)

The Notion API supports moving pages via two mechanisms:

1. PATCH /v1/pages/{page_id} — Update Parent Field (Legacy)

{
  "parent": {
    "type": "page_id",
    "page_id": "<new-parent-page-id>"
  }
}

2. POST /v1/pages/{page_id}/move — Dedicated Move Endpoint (New)

{
  "parent": {
    "type": "page_id",
    "page_id": "f336d0bc-b841-465b-8045-024475c079dd"
  }
}

Move into a database:

{
  "parent": {
    "type": "data_source_id",
    "data_source_id": "1c7b35e6-e67f-8096-bf3f-000ba938459e"
  }
}

Key detail: When moving into a database, you must use data_source_id (not database_id). Retrieve this via the "Retrieve a database" endpoint.

vibe-notion CLI Support (Verified)

The CLI has block move --parent for blocks, but not a dedicated page move:

# This works for blocks:
vibe-notion block move <block_id> --parent <new_parent_id>

# For pages, we need to use raw CLI or the API directly
vibe-notion raw-cli ['pages', 'move', '<page_id>', '--parent', '<new_parent_id>']

❌ CRITICAL LIMITATION: Cross-Workspace Moves

The Notion API operates within a single workspace only.

Each integration (bot) is bound to one workspace. There is no cross-workspace move endpoint. To "move" a page between workspaces you must:

1. Export/copy page content via the API in workspace A
2. Create a new page in workspace B via a separate integration token
3. Recreate children blocks recursively

This is a fundamental API limitation, not a bug.

Permission Requirements

Requirement	Detail
Auth	Bearer token (Internal Integration or OAuth)
Bot access	Must have edit access to the page being moved
New parent access	Bot must have edit access to the target parent page/database
Capability	Connection needs update_content capability

Children Blocks — Preserved on Move

When you move a page, all child blocks (children) move with it. The page is removed from its current parent and re-attached to the new parent. The block tree is preserved intact. No separate operation is needed for children.

Limitations & Gotchas

Gotcha	Detail
No cross-workspace	API is single-workspace only
Regular pages only	page_id must be a regular Notion page, not a database
Database parent requires data_source_id	Cannot use database_id; must use the data source UUID
Rate limits	429 Too Many Requests — bulk moves need throttling
No batch move	Must move pages one at a time via individual API calls
Properties may not match	Moving from database to page parent (or vice versa) loses/inherits different property schemas

Archive vs Delete vs Move

Action	API	Effect	Reversible?
Archive	PATCH /v1/pages/{page_id} with {"archived": true}	Removes from view, retains in page history	Yes
Delete (Trash)	DELETE /v1/blocks/{block_id} or set {"in_trash": true}	Moves to Trash, soft-delete	Yes
Move	POST /v1/pages/{page_id}/move with new parent	Relocates page + children	Yes (move again)

Proposed Tool Signature

@mcp.tool()
def notion_write_move_page(
    page_id: str,
    new_parent_id: str,
    parent_type: str = "page_id",  # "page_id" or "data_source_id"
) -> dict[str, Any]:
    """Move a page to a new parent location within the same workspace.
    
    ⚠️ CRITICAL: Cross-workspace moves are NOT supported by the Notion API.
    This tool can only move pages within the same workspace.
    
    Args:
        page_id: ID of the page to move
        new_parent_id: ID of the new parent page or data_source_id
        parent_type: Type of parent ("page_id" for regular pages, "data_source_id" for databases)
    """
    # Use the dedicated move endpoint
    payload = {
        "parent": {
            "type": parent_type,
            "parent_type": new_parent_id
        }
    }
    
    return _run(["raw-cli", "pages", "move", page_id, "--data", json.dumps(payload)])

Example Usage

# Move a page to a new parent page
notion_write_move_page(
    page_id="abc123",
    new_parent_id="def456",
    parent_type="page_id"
)

# Move a page into a database
notion_write_move_page(
    page_id="abc123",
    new_parent_id="ghi789",
    parent_type="data_source_id"
)

References

• Notion API: Update a Page
• Notion API: Move a Page (new endpoint)
• Notion API: Retrieve a Database (for data_source_id)