glm-subagent-mcp
Related Servers
Alternatives to glm-subagent-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceDelegates coding tasks to the local Claude Code CLI via MCP, offering run, review, and status tools for MCP-compatible agents.14 npm-
- AlicenseNot gradedqualityDmaintenanceMCP bridge for calling local coding-agent CLIs (Codex, Claude) from another agent, enabling bounded tasks like code review, verification, and bug hunting.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables AI chat clients to delegate self-contained coding tasks to opencode's free-tier models as a one-shot subagent through a native MCP tool, without requiring shell commands or API keys.MIT
- AlicenseAqualityCmaintenanceMCP 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.4MIT
- AlicenseAqualityBmaintenanceEnables ChatGPT and Codex to safely work with explicitly authorized local project folders through MCP, providing constrained file reading, searching, patch editing, Git inspection, and whitelisted tasks without exposing arbitrary shell, deletion, or deployment capabilities.17MIT
TDQS
Scored across 1 tool
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.
The single tool uses snake_case (`glm_agent`), which is a standard, predictable convention. With only one tool, consistency is trivially satisfied.
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.
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.