What is the key difference between Concord MCP and Glm MCP?

Concord MCP belongs to the Coding Agents category with cloud HTTP/SSE execution, while Glm MCP belongs to the Coding Agents category with local stdio execution.

How do I install Concord MCP or Glm MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Concord MCP and Glm MCP free or paid?

Concord MCP operates under a Free / Open Source model (No auth required). Glm MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Concord MCP lists 6 tools with 1 views and 398 GitHub stars. Glm MCP lists 6 tools with 6 views and 4 GitHub stars.

Can I use both Concord MCP and Glm MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Concord MCP vs Glm MCP

In-depth architectural comparison of the Concord MCP and Glm MCP 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.

At a Glance & Executive Verdict

Concord MCP

Coding Agents · Remote HTTP/SSE

Quality: 45/100 (Fair) | Auth: No auth required

Glm MCP

Coding Agents · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Verdict Summary: Choose Concord MCP if you need specialized Coding Agents tools running via a hosted cloud SSE transport. Choose Glm MCP if your workspace requires Coding Agents integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Concord MCP when:

You need dedicated capabilities in the Coding Agents domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: CONCORD_REPO_ROOT.
Primary tools included: Shared SQLite work-state, File and module overlap detection, Cross-harness prompts and replies.

Explore Concord MCP Details

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.

Feature & Specification Comparison

Specification	Concord MCP Coding Agents	Glm MCP djerok Coding Agents
Summary	Cross-harness communication and shared work-state for AI coding agents.	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.
Category & Scope	Coding Agents

Tools & Capabilities Breakdown

Concord MCP Tools (6)

Shared SQLite work-state

File and module overlap detection

Cross-harness prompts and replies

Task assignments and handoffs

Append-only ownership history

Review evidence and lifecycle states

Glm MCP Tools (6)

Repository-level GLM agent loop

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).

Concord MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "concord-mcp": {
      "url": "https://api.star-history.com/chart?repos=Get-Concord-AI/concord-mcp&type=date&theme=dark&legend=top-left&sealed_token=PLqZk9LDZSite53TJb5bwyYask4-B5wAFxLcp3Ki_mJ3KlMtSpH09lN3ohwJuoQNs5Kwg_0zPG2DEwcRzJZvCIP1Md6vMdHjNwF_WkjuX6gd44wkwWFzqrAWgXGx2bPFEuJFRhmuWUlbRLnPOw6uW7cVJzrlcxprXCDU3_hHmUlHaFjVjQulH7EkfyuA"
    }
  }
}

Glm MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Concord MCP is categorized under Coding Agents and uses a remote streaming HTTP/SSE transport. In contrast, Glm MCP belongs to Coding Agents using local stdio subprocess. Select Concord MCP when you need capabilities focused on coding agents and Glm MCP when you require tools for coding agents.

More alternatives to Concord MCP More alternatives to Glm MCP Coding Agents category hub

Related MCP Server Comparisons

Popular comparisons with Concord MCP

Popular comparisons with Glm MCP

Glm MCP vs Baton