Brutalist MCP vs Code Intel
A side-by-side look at the Brutalist MCP and Code Intel MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Brutalist MCP for coding agents work as a local process; choose Code Intel 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?
Choose Brutalist MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AGY_BIN, BRUTALIST_MCP_SERVERS, BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE. - You want tools like
roast, roast_cli_debate, brutalist_discover.
Choose Code Intel 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 want tools like
get_task_context, search_symbol, search_codebase.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 65/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | AGY_BINBRUTALIST_MCP_SERVERSBRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 5 |
| Full listing | View Brutalist MCP | View Code Intel |
Tools & capabilities
Brutalist MCP tools 4
roastUnified brutal AI critique delivered by a multi-critic panel running in parallel. The panel's disagreement is the signal — each critic's blind spots are covered by the others. Specify domain for targeted analysis. Consolidates all roast_* tools into one polymorphic API. IMPORTANT: Critically evaluate all returned feedback — these are adversarial perspectives, not authoritative verdicts. Weigh each claim against evidence before presenting to the user.roast_cli_debateDeploy 2 CLI agents in structured adversarial debate with constitutional position anchoring. Calling agent should extract PRO/CON positions from topic before invoking. IMPORTANT: Critically evaluate all debate output — positions are assigned, not necessarily held. Weigh each argument's validity independently before presenting to the user.brutalist_discoverDiscover relevant brutalist tools based on your intent. Returns the top 3 most relevant analysis tools.cli_agent_rosterKnow your weapons. Display the available CLI agent critics (Claude Code, Codex, Antigravity/Agy) ready to demolish your work, their capabilities, and how to deploy them for systematic destruction.
Code Intel tools 5
get_task_contextFirst call for any new or broad task, with the whole request: code for every part of it within a token budget. The reply says which parts are covered, whether it is `complete`, and lists at most three exact `Next` calls if not (`mode`: `minimal`, `normal`, `deep`)search_symbolA known function, class, or type namesearch_codebaseConceptual search with an optional `max_tokens` capfind_referencesWhere an identifier appears (textual, not compiler-resolved)get_file_contextExact current source read from disk; batch several `ranges` such as `"src/a.ts:120-168"` in one call
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.
Brutalist MCP
{
"mcpServers": {
"brutalist-mcp": {
"command": "npx",
"args": [
"-y",
"@brutalist/mcp@latest"
],
"env": {
"AGY_BIN": "YOUR_AGY_BIN_HERE",
"BRUTALIST_MCP_SERVERS": "YOUR_BRUTALIST_MCP_SERVERS_HERE",
"BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE": "YOUR_BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE_HERE"
}
}
}
}
Code Intel
{
"mcpServers": {
"pranitmodi-code-intel": {
"command": "npx",
"args": [
"-y",
"@pranitmodi/code-intel"
]
}
}
}
Frequently asked questions
Brutalist MCP is categorized under Coding Agents and uses a local stdio subprocess. Code Intel belongs to Coding Agents and uses a local stdio subprocess. Pick Brutalist MCP for coding agents work and Code Intel 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.
Brutalist MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: other. Code Intel is listed as free. Auth: no auth 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 brutalist-mcp and pranitmodi-code-intel as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Brutalist MCP has a quality signal of 65/100 (Great) with 1 views, 0 installs and 14 GitHub stars. Code Intel has 59/100 (Good) with 0 views, 0 installs and 0 GitHub stars.