Skip to main content
Glama
HOWILLMAKEIT

glm-subagent-mcp

by HOWILLMAKEIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to glm-subagent-mcp

No user-submitted related servers found.

    Related Servers

    • Claude Code MCP

      sarthchawla
      A
      license
      Not graded
      quality
      D
      maintenance
      Delegates coding tasks to the local Claude Code CLI via MCP, offering run, review, and status tools for MCP-compatible agents.
      16 npm
      MIT

    • Houtini LM

      Nguyen53
      F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets Claude Code or any MCP client hand bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model, an OpenAI-compatible endpoint, a router, or a cheap cloud API, so those files never enter the orchestrator's context window. This cuts token spend and quota use while providing a second model to sanity-check results.
      -

    • Jev Reflex

      EternitiesAi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to make small, bounded decisions around tasks via stdio MCP, supporting source-bound context, durable budgets, bulk jobs, and measured outcomes while leaving planning and reasoning with the main model.
      MIT

    • local-llm-mcp

      drangoht
      A
      license
      A
      quality
      D
      maintenance
      MCP server connecting Claude Code to LM Studio, delegating token-expensive tasks to a local model while keeping the cloud model in control. It reduces cloud context usage by reading files locally and returning only the processed results.
      4
      MIT
    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

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool is exposed, so there is zero risk of selecting the wrong tool. Its purpose—delegating a self-contained coding task to a GLM sub-agent—is clearly stated and distinct.

    Naming Consistency5/5

    The single tool uses snake_case (`glm_agent`), which is a standard, predictable convention. With only one tool, consistency is trivially satisfied.

    Tool Count4/5

    One tool is slightly below the typical 3–15 range, but the server is a focused, single-purpose delegation wrapper. The tool is substantial rather than trivial, so the count is reasonable though thin.

    Completeness4/5

    The tool covers the core delegation lifecycle: accept a task, run it in a workdir, return summary and changed files. However, it lacks follow-up operations like status, cancellation, or session continuation, which could be useful for long tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources