Glm MCP vs Citio

In-depth architectural comparison of the Glm MCP and Citio MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Glm MCP when:

• You need dedicated capabilities in the Coding Agents domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: GLM_API_KEY.
• Primary tools included: Repository-level GLM agent loop, Read, write, edit, list, and Bash tools, Dry-run diff preview and Git revert guidance.

Explore Glm MCP Details

Choose Citio when:

• You need dedicated capabilities in the Coding Agents domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: other (BYOK (Pay Provider Direct)).
• Primary tools included: Slack DMs and channel mentions, Claude Code and OpenAI Codex support, Controlled MCP tool layer.

Feature & Specification Comparison

Specification	Glm MCP djerok Coding Agents	Citio lawrencehui Coding Agents
Summary	Run GLM (Zhipu/Z.ai) as a real sub-agent inside Claude Code or GitHub Copilot. GLM gets its own agent loop (read/write/edit/run) on your repo — not a single LLM call — with peak-aware Opus-vs-GLM routing, diff/dry-run/git-revert oversight, and a usage ledger. 10x cheaper than Opus. Requires a Z.ai GLM Coding Plan key.	Self-hosted AI teammate in Slack: @mention it and Claude Code or Codex investigates CloudWatch logs, runs tests, and opens pull requests. The bundled MCP server holds all credentials (GitHub, AWS, Slack) so the agent never sees keys. One-command deploy to your own AWS. MIT.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "djerok-glm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "glm-mcp-claude"
      ],
      "env": {
        "GLM_API_KEY": "YOUR_GLM_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "lawrencehui-citio": {
      "command": "npx",
      "args": [
        "-y",
        "@lawrencehui/citio"
      ]
    }
  }
}

Related MCP Server Comparisons