Skip to main content
Glama
arielaizn

vibe-code-mcp

by arielaizn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to vibe-code-mcp

No user-submitted related servers found.

    Related Servers

    • Vibe Design Guide MCP Server

      yathboss
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes The Vibe Coder's Web Design Guide as tools for AI agents, enabling lookups of UI design patterns, CSS/JS snippets, and composition of optimized front-end prompts.
      -

    • logoforge

      terravidhal
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI editors such as Claude, Cursor, Windsurf, and VS Code to search a library of 909 developer brand logos, list categories, fetch logo metadata, SVGs, and typed React components, and assemble logo clouds through natural-language tool calls.
      37
      -

    • Code Search MCP

      LLMTooling
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.
      8
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation3/5

    Most tools are distinct, but recommend_stack and route_project both provide recommendations based on a description, causing potential overlap. Descriptions help differentiate, but an agent may still be uncertain which to use for a given query.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_, list_, recommend_, refresh_, route_, search_), but catalog_status is a noun_noun phrase, breaking the convention. Overall, naming is largely consistent and intuitive.

    Tool Count5/5

    With 9 tools covering browsing, search, recommendation, status, and refresh, the count is well-scoped for a catalog server. Each tool has a clear role, and the number feels appropriate without being overwhelming or insufficient.

    Completeness4/5

    The server provides comprehensive browsing (by domain, section, tool), searching, recommendation, and status. Missing a direct 'list all tools' endpoint, but the combination of search and section browsing covers most discovery needs. Minor gap for read-only catalog.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources