Cursor MCP vs Glm MCP
A side-by-side look at the Cursor MCP and Glm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Cursor MCPCoding Agents · Local subprocess (stdio)Cursor's agent (cursor-agent CLI) through MCP: any model your plan offers, resumable sessions.52GoodAuth: not declaredVerdict: choose Cursor MCP for coding agents work as a local process; choose Glm MCP for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Cursor MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CURSOR_MAX_CONCURRENCY, CURSOR_ALLOW_YOLO, CURSOR_SANDBOX, CURSOR_KILL_GRACE_MS. - You want tools like
cursor_agent, cursor_reply, cursor_models.
Choose Glm MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GLM_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Cursor MCP | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 52/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | CURSOR_MAX_CONCURRENCYCURSOR_ALLOW_YOLOCURSOR_SANDBOXCURSOR_KILL_GRACE_MS |
Tools & capabilities
Cursor MCP tools 5
cursor_agentExecute a prompt using Cursor's AI agentcursor_replyContinue an existing agent sessioncursor_modelsList the model ids the installed CLI offerscursor_sessionsList agent sessions (this server instance)cursor_healthCheck installation, auth, and config
Glm MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cursor MCP
{
"mcpServers": {
"cursor-mcp": {
"command": "npx",
"args": [
"-y",
"@qmediat.io/cursor-mcp"
],
"env": {
"CURSOR_MAX_CONCURRENCY": "YOUR_CURSOR_MAX_CONCURRENCY_HERE",
"CURSOR_ALLOW_YOLO": "YOUR_CURSOR_ALLOW_YOLO_HERE",
"CURSOR_SANDBOX": "YOUR_CURSOR_SANDBOX_HERE",
"CURSOR_KILL_GRACE_MS": "YOUR_CURSOR_KILL_GRACE_MS_HERE"
}
}
}
}
Glm MCP
{
"mcpServers": {
"djerok-glm-mcp": {
"command": "npx",
"args": [
"-y",
"glm-mcp-claude"
],
"env": {
"GLM_API_KEY": "YOUR_GLM_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Cursor MCP is categorized under Coding Agents and uses a local stdio subprocess. Glm MCP belongs to Coding Agents and uses a local stdio subprocess. Pick Cursor MCP for coding agents work and Glm MCP for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cursor MCP has no declared pricing — check the project's own site. Glm MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cursor-mcp and djerok-glm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cursor MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Glm MCP has 51/100 (Good) with 6 views, 0 installs and 5 GitHub stars.
