Tiling Trees MCP Server

Create a new tiling tree to explore a problem/challenge. The tree starts with a root tile representing the complete solution space, which you'll then split recursively using MECE (Mutually Exclusive, Collectively Exhaustive) principles.

Split a tile into MECE (Mutually Exclusive, Collectively Exhaustive) subsets using a specific attribute/dimension. This is the core operation of the tiling trees method - partitioning the solution space systematically. Use physics/math-oriented splits when possible.

Add additional tiles to an existing split (when you realize a category was missed). This invalidates the MECE validation and requires re-verification.

Mark a split as validated for MECE (Mutually Exclusive, Collectively Exhaustive) properties. Verify that the children completely cover the parent space with no overlaps.

Evaluate a leaf tile (concrete idea/project) on impact, feasibility, and uniqueness. Include any calculations or pilot studies performed.

Update a tile's information (title, description, split attributes, etc.)

Get all tiling trees

Get details of a specific tile

Explore the tree structure from a specific tile, showing the hierarchical breakdown

Get all leaf tiles (concrete ideas/projects) from a tree

Get tiles that haven't been split yet - these are gaps in your solution space exploration

Get the highest-rated leaf tiles based on evaluation criteria

Search for tiles by content

Analyze the completeness of solution space exploration for a tree. Shows unexplored branches, unvalidated splits, and suggestions for next steps.

Get overall statistics about all tiling trees

Export a tiling tree in various formats for visualization or documentation

Validate split quality and detect common antipatterns (vague language, catch-all buckets, mixed dimensions, retroactive splitting, incomplete coverage). Returns a detailed quality report with issues and recommendations.

Get validation report for all splits in a tree. Identifies antipatterns and provides an overall quality score. Use this after building a tree to check for common failure modes.