Skip to content

Feature Request: reorder_children / move_node tool for MCP #2

@opalsaints

Description

@opalsaints

Feature Request: Reorder children within a parent node

Context: Using Paper MCP from Claude Code (Claude Agent SDK via MCP). Building long scrolling artboards (e.g., full landing page mockups with 11+ sections).

Problem

Currently write_html with insert-children mode always appends new nodes at the end of the parent's children list. There is no way to:

  1. Insert a child at a specific index (e.g., "insert after the 3rd child")
  2. Reorder existing children (e.g., "move child X to position 5")
  3. Move a node from one parent to another while preserving it

Current Workaround

When I need to insert a section between existing sections (e.g., adding "Stage: Live" between "Stage: Publish" and "Try It Now"), I have to:

  1. Delete all sections after the insertion point
  2. Add the new section
  3. Re-create all deleted sections from scratch

This is extremely wasteful — it requires re-writing potentially hundreds of nodes, loses any manual edits made in the Paper UI, and consumes many API calls.

Proposed Solutions

Any of these would solve the problem:

  • reorder_children tool — accepts a parent node ID and an ordered array of child IDs
  • move_node tool — accepts a node ID, target parent ID, and target index
  • write_html with insertAt parameter — e.g., mode: "insert-children" with an optional index or afterNodeId parameter

Use Case

Building full-page design mockups iteratively with an AI agent (Claude Code via MCP). The agent builds sections top-to-bottom, but frequently needs to insert, reorder, or fix sections in the middle without destroying everything below.

Environment

  • Claude Code (Claude Agent SDK)
  • Paper MCP server
  • Building complex multi-section artboards (1440px × 9000px+ desktop landing pages)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions