Skip to main content
Glama
wllcyg

local-component-mcp

by wllcyg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to local-component-mcp

No user-submitted related servers found.

    Related Servers

    • strata-mcp

      Shironim
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides precise AST-based code search and structural intelligence across Vue, Astro, and React/Next projects, including component usage audits, dependency trees, route scanning, state impact tracing, and dead component detection.
      390 npm
      2
      MIT

    • Frontend Code Analysis MCP

      cmc12138
      A
      license
      Not graded
      quality
      D
      maintenance
      Analyzes frontend project code (React, Vue, Angular) and converts it into AI-understandable flow diagrams and object structures. Provides tools for code analysis, variable/function/component inspection, and project structure insights.
      4 npm
      MIT

    • SigmaUI DS MCP Server

      ribsousa
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes SigmaUI Design System components to AI assistants, providing tools for component documentation, search, usage examples, and design tokens to accelerate Vue 3 and Nuxt 3 UI development.
      -

    • storybook-mcp

      aransword
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read and analyze local Storybook component specifications, including component listings, props, and source code examples.
      5 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    Both tools have clearly distinct purposes: one searches for component files, the other parses a specific component's metadata. No overlap in functionality.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern (get_component_detail, search_components), making it easy to predict their actions.

    Tool Count3/5

    With only 2 tools, the server feels minimal. While they cover basic search and detail retrieval, the scope is thin for a component management server.

    Completeness2/5

    The server lacks essential operations for a complete component workflow, such as listing all components, creating, updating, or deleting. Users can only search and get details, which is a notable gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources