FlyonUI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-create-instructionsB | 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-instructionsA | 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-instructionsA | 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. |
| get-blocks-metadataD | 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-block-meta-contentC | Fetch the content of the block metadata from the FlyonUI MCP server. Use this tool to retrieve the block metadata content. |
| get-block-contentC | Fetch the content of a block from a given URL. Use this tool to retrieve the code block content from the authenticated URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tools are largely distinct but 'get-block-meta-content' and 'get-blocks-metadata' could cause confusion as one fetches single block metadata content and the other all blocks metadata. Descriptions help disambiguate.
All tools follow a consistent 'get-{target}' pattern with hyphens, making them predictable and easy to understand.
With 6 tools, the server is well-scoped for its purpose of retrieving block content, metadata, and instructions without being bloated.
The tool set covers retrieval and workflow instructions but lacks actual create, update, or delete operations for blocks, leaving gaps in lifecycle coverage.