Skip to main content
Glama
seonmikii

gdc-claude-plugin

by seonmikii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to gdc-claude-plugin

No user-submitted related servers found.

    Related Servers

    • claude-code-mcp

      xihuai18
      A
      license
      A
      quality
      D
      maintenance
      Wraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.
      4
      34 npm
      20
      MIT

    • Herald

      kOlapsis
      A
      license
      Not graded
      quality
      F
      maintenance
      The self-hosted MCP bridge between Claude Chat and Claude Code.
      46
      AGPL 3.0

    • code-bridge

      ITSWProj
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.
      2 npm
      MIT

    • GoPeak

      HaD0Yun
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to edit, run, inspect, and fix Godot 4 projects through an MCP server with dynamic tool groups and setup-gated capabilities.
      126 npm
      258
      MIT
    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

    A3.9/5.0

    Scored across 28 tools

    Disambiguation4/5

    Each tool has a clear primary purpose, and potentially overlapping tools like list_my_tasks, list_tasks, and search_tasks are explicitly differentiated in their descriptions. Some pairs (list_my_notifications vs list_my_mentions) are similar but serve distinct use cases.

    Naming Consistency3/5

    Most tool names follow a verb_noun pattern (list_*, get_*, update_*, delete_*), but there are inconsistencies such as 'task_from_doc' (noun-first), 'gdc_login' (prefix + verb), and 'link_task_to_doc' (verb + object + preposition). This breaks a fully predictable naming scheme.

    Tool Count2/5

    With 28 tools, the count exceeds the 'heavy' threshold of 25, making selection more difficult. Although the scope is broad (workspaces, projects, tasks, comments, notifications, docs), several tools are close variants of task listing/filtering and could be consolidated.

    Completeness5/5

    The tool set covers the full task lifecycle (create, read, update, delete, restore, archive), comments (list, add, update, delete), notifications (read-only), and document integration (link, create, sync). No critical operations are missing for the domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources