That is the thing to understand before installing it. get-create-instructions, get-inspire-instructions and get-refine-instructions hand back steps for the editor's agent to carry out, and the create one says explicitly that the steps are to be followed one by one for generation to succeed. The components themselves come from the other three, which fetch metadata and code. So the two halves are a pair, and either one on its own is half a workflow.
A FlyonUI server in two parts: three tools that return the procedure an editor agent should follow, and three that fetch the block metadata and code it works from.
- get-create-instructions, returning the steps for generating a new block out of existing ones, to be followed in order
- get-inspire-instructions, for generating a block by taking its cue from existing FlyonUI blocks
- get-refine-instructions, for reworking a block that already exists
- get-blocks-metadata, the metadata for every FlyonUI block available for use
- get-block-meta-content and get-block-content, fetching metadata content and block code from a given endpoint
Network access to the FlyonUI endpoints the fetch tools read — get-block-content describes the URL it reads from as authenticated.
One command — npx -y flyonui-mcp