get-block-content
Fetch the content of a block from a given URL. Use this tool to retrieve the code block content from the authenticated URL.
LABSCO SUMMARY
Three of the six tools return a procedure, not a component.
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.
What it is
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.
What you get
- 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
Requirements
Network access to the FlyonUI endpoints the fetch tools read — get-block-content describes the URL it reads from as authenticated.
Setup effort
One command — npx -y flyonui-mcp
USE CASES
01
Generating a new FlyonUI component without inventing the markup
The instruction tool returns the steps to follow in order, the metadata says which blocks exist, and the content call fetches the code the new component is assembled from.
02
Reworking a component that is already in the codebase
Refinement has its own procedure rather than being a re-generation, and the block's metadata content is pulled for the piece being changed instead of the whole library.
03
Building something new that keeps the look of an existing block
The inspire path takes an existing block as a reference rather than a template, so the result follows the library's conventions without being a copy of one component.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-block-meta-content
Fetch the content of the block metadata from the FlyonUI MCP server. Use this tool to retrieve the block metadata content.
get-blocks-metadata
Fetch the metadata of a block from a given URL. Use this tool to retrieve the block metadata. This will provide the metadata of all the FlyonUI blocks available for use.
get-create-instructions
Get instructions for creating FlyonUI blocks using existing blocks. This tool provides instructions for creating new FlyonUI blocks using existing blocks. Use this tool when the user requests to generate a new component. mentions /create-flyonui or /cui. Strictly follow the steps one by one to ensure successful code generation.Retrieves Instructions for IDE agent to follow for creating/generating/updating FlyonUI blocks.
get-inspire-instructions
Get instructions for working with FlyonUI blocks. This tool provides instructions for creating new FlyonUI blocks by taking the inspiration from existing FlyonUI blocks. Use this tool when the user requests to generate a new component by inspirations. mentions /inspire-flyonui or /iui.
get-refine-instructions
Get instructions for refining FlyonUI blocks. This tool provides instructions for refining existing FlyonUI blocks. Use this tool when the user requests to refine an existing component. mentions /refine-flyonui or /rui.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"flyonui-mcp": {
"command": "npx",
"args": [
"-y",
"flyonui-mcp"
]
}
}
}npx
TERMINAL
npx -y flyonui-mcp
