10 actions in 1 pieces of software · ranked by words, meaning and measured trust · 498 ms

1. 1termframedemo or tutorialno passport yet

   MCP serversubodh-thallada/termframe

   • get_screen

     Render a screen and describe its layers. Returns the screen as plain text inside a numbered border (exactly what a terminal prints, minus colors), then a layer tree: one line per layer with its id, type, name, cell geometry [x,y width×height] and properties (layout, border, style, widget props). Use

   • check_design

     Check screens for problems: content that overflows the terminal size, unknown color tokens, broken prototype links, contrast and color-only meaning issues (where available). Returns issues with severity, the screen and the layer id.

   • create_screen

   • list_screens

     List the pages and screens (frames) in the design file with ids, sizes, themes and interaction counts, plus the color tokens, text styles and components you can use. Start here.

   • add_interaction

     Link screens into a clickable prototype (used by the editor's player, `termframe play` and code export). Triggers: "key" (a key press: "enter", "escape", "tab", "space", "up", "down", "left", "right", "backspace", a character like "q", or a chord like "ctrl+c"), "delay" (after ms on the screen, e.g.

   • insert_nodes

   • set_theme

   • list_templates

     List the document templates the editor and `termframe init --template <id>` can start from.

   • export_code

   • list_widgets

     List the widget kinds with what they are for and their default props (the values you get for any prop you leave out).