Skip to main content
Glama
djerok

GLM Subagent MCP

by djerok

Related Servers

Alternatives to GLM Subagent MCP

  • A
    license
    A
    quality
    C
    maintenance
    Enables Claude to consult GLM-4.6's architectural intelligence for system design, code analysis, scalability patterns, and technical decision-making. Provides specialized tools for enterprise architecture consultation, distributed systems design, and code review through the Model Context Protocol.
    5
    15
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Run DeepSeek as a real sub-agent inside Claude Code / Codex CLI — not just a single LLM call. DeepSeek gets its own 7-tool agent loop (Read/Write/Edit/Bash/Glob/Grep/NotebookEdit) inside a sandboxed workspace.
    2
    31
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude Code (Anthropic Sonnet) to invoke Z.AI's GLM-4.6 model through a secondary Claude instance. Supports code generation, deep analysis, and general queries while maintaining file tracking and secure token management.
    1
    -
  • A
    license
    A
    quality
    A
    maintenance
    Exposes Z.ai GLM models (GLM-5.3 and siblings) as callable tools within Claude Code and Claude Desktop, enabling large-context second opinions, bulk grunt work, and independent model reasoning mid-conversation.
    3
    264 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Delegates autonomous coding tasks to Z.ai's GLM models with a genuine agent loop, file operations, and verification via git and real process results.
    46 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude Code to delegate tasks to Google Antigravity (Gemini) as an autonomous subagent, including codebase exploration, architecture analysis, multi-file code generation, and technical Q&A, without requiring external API keys.
    MIT

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: glm_agent performs full repo work with file access, glm_delegate handles text-only subtasks, glm_recommend advises on model choice, and glm_status shows usage and config. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent 'glm_' prefix followed by a descriptive word (agent, delegate, recommend, status). The pattern is uniform with lowercase and underscores, making it easy to understand each tool's function.

Tool Count5/5

With 4 tools, the set is well-scoped for the server's purpose of providing GLM subagent capabilities. Each tool justifies its existence, covering distinct modes of interaction without unnecessary bloat or deficiency.

Completeness5/5

The tool surface covers the full lifecycle: doing work (agent and delegate), getting advice on which to use (recommend), and monitoring usage (status). There are no obvious gaps for the intended use case of a GLM subagent.

Maintenance

ActivityStale
ResponsivenessNo issues