Gutsy vs Glm MCP
A side-by-side look at the Gutsy and Glm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
GutsyCoding Agents · Local subprocess (stdio)Local gut check before risky agent actions: calibrated safe/intended probabilities, no API calls.41FairAuth: no auth requiredVerdict: choose Gutsy 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?
GChoose Gutsy when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
GUTSY_URL, GUTSY_INFERENCE_DIR, GUTSY_MODEL, GUTSY_PROCEED_MIN, GUTSY_BLOCK_MIN, GUTSY_API_KEY, GUTSY_HOOK_ALLOW_DENY.
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 | G Gutsy | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 41/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | GUTSY_URLGUTSY_INFERENCE_DIRGUTSY_MODELGUTSY_PROCEED_MINGUTSY_BLOCK_MINGUTSY_API_KEYGUTSY_HOOK_ALLOW_DENY | GLM_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gutsy | View Glm MCP |
Tools & capabilities
Gutsy tools
No tool names declared yet. Check the project README from the listing page.
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.
Gutsy
{
"mcpServers": {
"gutsy": {
"command": "uvx",
"args": [
"gutsy-mcp"
],
"env": {
"GUTSY_URL": "YOUR_GUTSY_URL_HERE",
"GUTSY_INFERENCE_DIR": "YOUR_GUTSY_INFERENCE_DIR_HERE",
"GUTSY_MODEL": "YOUR_GUTSY_MODEL_HERE",
"GUTSY_PROCEED_MIN": "YOUR_GUTSY_PROCEED_MIN_HERE",
"GUTSY_BLOCK_MIN": "YOUR_GUTSY_BLOCK_MIN_HERE",
"GUTSY_API_KEY": "YOUR_GUTSY_API_KEY_HERE",
"GUTSY_HOOK_ALLOW_DENY": "YOUR_GUTSY_HOOK_ALLOW_DENY_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
Gutsy is categorized under Coding Agents and uses a local stdio subprocess. Glm MCP belongs to Coding Agents and uses a local stdio subprocess. Pick Gutsy 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.
Gutsy is listed as free. Auth: no auth required. 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 gutsy and djerok-glm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gutsy has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Glm MCP has 55/100 (Good) with 7 views, 0 installs and 5 GitHub stars.