Skip to main content
Glama
Sign In
legwork-mcp

legwork-mcp

by kumarganduri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to legwork-mcp

No user-submitted related servers found.

    Related Servers

    • Gitingest-MCP

      ryuji1315
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Desktop, Cline, and Cursor to extract information from GitHub repositories, including repository summaries, project directory structure, and file contents. It exposes these capabilities as tools that can be invoked directly from a natural-language chat session.
      -

    • Gitingest-MCP

      JasonDunn02
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Desktop, Cline, and Cursor to quickly extract information about GitHub repositories, including repository summaries, project directory structures, and file contents.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role in the discover-install-monitor-use lifecycle, and descriptions clarify boundaries. Minor potential confusion exists between find_tools (search remote/cache) and list_installed_tools (list local installs), but the descriptions make the distinction clear.

    Naming Consistency4/5

    All names use snake_case and start with a verb, giving a predictable verb_noun pattern overall. Small inconsistencies exist (find_tools plural vs use_tool singular, install_status using a state noun), but they remain readable and consistent enough.

    Tool Count5/5

    Five tools is well-scoped for the server's purpose: find, install, check status, list installed tools, and use a tool. Each tool earns its place without redundancy.

    Completeness4/5

    The core lifecycle is covered: discovery, installation, status polling, listing installed tools, and invoking them. Minor gaps exist around uninstalling/removing installed tools or updating grants, but these are not central to the primary workflow.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources