Flux UI MCP Server
Allows Codeium (through Windsurf) to access Flux UI component documentation and examples through a series of tools for component discovery and reference.
Provides reference information for Flux UI components, including component documentation, usage examples, props, and code samples scraped from the official Flux UI documentation site.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Flux UI MCP Server show me examples for the Button component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Flux UI MCP Server
MCP server for Flux UI component references
This is a TypeScript-based MCP server that provides reference information for Flux UI components. It implements a Model Context Protocol (MCP) server that helps AI assistants access Flux UI component documentation and examples.
Features
Tools
list_flux_components- Get a list of all available Flux UI componentsget_flux_component_details- Get detailed information about a specific componentget_flux_component_examples- Get usage examples for a specific componentsearch_flux_components- Search for components by keyword
Functionality
This server scrapes and caches information from:
The official Flux UI documentation site (https://fluxui.dev)
It provides structured data including:
Component descriptions
Usage examples
Props
Code samples
Related MCP server: WordPress Design System MCP Server
Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchInstallation
Claude Desktop Configuration
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Option 1: Using local build
{
"mcpServers": {
"fluxui-server": {
"command": "/path/to/fluxui-mcp-server/build/index.js"
}
}
}Option 2: Using npx command
{
"mcpServers": {
"fluxui-server": {
"command": "npx",
"args": ["-y", "fluxui-mcp-server"]
}
}
}Windsurf Configuration
Add this to your ./codeium/windsurf/model_config.json:
{
"mcpServers": {
"fluxui-server": {
"command": "npx",
"args": ["-y", "fluxui-mcp-server"]
}
}
}Cursor Configuration
Add this to your .cursor/mcp.json:
{
"mcpServers": {
"fluxui-server": {
"command": "npx",
"args": ["-y", "fluxui-mcp-server"]
}
}
}Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Available Tools
4 toolsget_flux_component_detailsC
Get detailed information about a specific Flux UI component
Inputs: componentName (required).
get_flux_component_examplesC
Get usage examples for a specific Flux UI component
Inputs: componentName (required).
list_flux_componentsB
Get a list of all available Flux UI components
Inputs: no named parameters.
search_flux_componentsC
Search for Flux UI components by keyword
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing all components, searching by keyword, getting details, and getting examples. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern with 'flux_component' as the common noun, using snake_case uniformly. The verbs (list, search, get) are clear and predictable.
With 4 tools, this server is well-scoped for its purpose of exploring Flux UI components. Each tool serves a specific, non-redundant function, making the count appropriate and efficient.
The toolset covers core exploration needs (list, search, details, examples) for a UI component library, but lacks CRUD operations like creating or updating components, which might be expected if the server also managed components. However, for a read-only documentation or reference server, it is largely complete.
Maintenance
Related MCP Connectors
Find Flood UI components, recipes, tokens, and design skills for coding agents.
Find UI components and themes, retrieve code, and generate with hosted 21st AI when enabled.
Orvain UI design system for React and Vue: real component props, variants and tokens for AI tools
The docs, rules, blocks, charts and design tokens of nuvui, a React UI library, for coding agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides AI coding assistants with on-demand access to component specs, test scenarios, accessibility requirements, and build guides from the Web UI Component Specification.10MIT
- AlicenseNot gradedqualityFmaintenanceProvides AI assistants with access to WordPress Design System component information and design guidance.9GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access documentation of Vue UI components, including props, events, and slots, for generating correct usage code.7MIT
- AlicenseAqualityDmaintenanceProvides access to Aceternity UI component library documentation, enabling AI assistants to browse, search, and retrieve detailed information about components.315 npmMIT