Skip to main content
Glama
Aniket-Sharma27

component-mcp-server

by Aniket-Sharma27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to component-mcp-server

No user-submitted related servers found.

    Related Servers

    • Design System MCP Server

      Thaynah
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.
      280 npm
      MIT

    • bunge-ds-mcp

      tabaldi98
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes the @bunge/ds-components design system catalog, allowing AI assistants to list, search, and retrieve component details including inputs, outputs, usage examples, and import instructions.
      4
      MIT

    • docs-mcp-server

      DewminK
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
      -

    • Markdown RAG MCP

      mohllal
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides semantic search over markdown documentation using RAG, allowing natural language queries and integration with MCP clients.
      1
      MIT

    • mcp-wiki-server

      AustinAbhari
      F
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible clients to search and read local markdown documentation, allowing agents to retrieve relevant doc snippets or full files by path.
      2
      -
    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

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists available components, the other retrieves detailed content for a specific component. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with snake_case (list_components, get_component_context), making the naming predictable and clear.

    Tool Count3/5

    With only two tools, the server feels minimal but still covers basic discovery and retrieval. However, for a server named 'component-mcp-server', a few more tools (e.g., search or create) might be expected, so the count is borderline.

    Completeness2/5

    The server only supports reading components (list and get). Missing create, update, and delete operations leave significant gaps for full component lifecycle management, limiting its usefulness for agents needing to modify components.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources