Skip to main content
Glama

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 components

  • get_flux_component_details - Get detailed information about a specific component

  • get_flux_component_examples - Get usage examples for a specific component

  • search_flux_components - Search for components by keyword

Functionality

This server scrapes and caches information from:

It provides structured data including:

  • Component descriptions

  • Usage examples

  • Props

  • Code samples

Related MCP server: WordPress Design System MCP Server

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

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 inspector

The Inspector will provide a URL to access debugging tools in your browser.

Available Tools

4 tools
get_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

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers