Skip to main content
Glama

Related Servers

Alternatives to claude-design-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      Not graded
      maintenance
      Bridges Claude Desktop, Claude Code CLI, and Claude Code for VS Code, enabling developers to plan in Desktop, save specs to project directories, and invoke Claude Code CLI with seamless state sharing across interfaces.
      4
      -
    • F
      license
      A
      quality
      D
      maintenance
      Bridges Claude Design projects into existing Claude Desktop sessions by fetching code files, chat history, and project bundles.
      7
      1
      -
    • F
      license
      B
      quality
      B
      maintenance
      Drives the real Claude Design web app from your editor or agent, enabling creation, iteration, and retrieval of designs generated on your own claude.ai account via automated browser interaction.
      10
      4
      -
    • A
      license
      A
      quality
      A
      maintenance
      Bridges Claude Code and OpenAI Codex CLI for an interactive plan-execute-review workflow, enabling Claude to interview, design, and review while Codex implements code changes.
      7
      291 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables working with and exporting live Claude Design projects and prototypes through a local bridge that handles OAuth authentication and adds tools to download files and export projects.
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      The self-hosted MCP bridge between Claude Chat and Claude Code.
      46
      AGPL 3.0

    TDQS

    A3.9/5.0

    Scored across 23 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: list_* covers different entities, delete_* differentiates by object, and read_chat vs read_file vs screenshot are clearly separate. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (list_chats, create_project, delete_files, etc.), with only minor exceptions like screenshot that are still readable and predictable.

    Tool Count3/5

    At 23 tools, the set is within the 16-25 range that feels heavy for a typical MCP server. While each tool seems necessary for the broad domain, the count is borderline and may overwhelm agents.

    Completeness4/5

    Core workflows for projects, chats, files, design systems, and external links are covered, but there are minor gaps: no explicit create_chat tool for starting a fresh thread in an existing project, and no list_repositories to discover available GitHub repos before choosing one.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive