Brutalist MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_BIN | No | Path to the Antigravity (agy) CLI binary. If not set, the server will look in default locations like ~/.local/bin/agy. | |
| BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE | No | Set to 'true' to allow Brutalist to pass the model parameter to Codex CLI. Default is 'false'. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roastA | Unified 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_debateA | Deploy 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_discoverB | Discover relevant brutalist tools based on your intent. Returns the top 3 most relevant analysis tools. |
| cli_agent_rosterA | Know 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
roast and roast_cli_debate overlap: both deliver adversarial AI critique via CLI agents, with the debate being a specialized variant. brutalist_discover and cli_agent_roster are both meta/informational tools that could be confused about their distinct roles, though descriptions do clarify them somewhat.
Names mix conventions: a bare verb (roast), a prefixed verb (roast_cli_debate), and two differently-prefixed nouns (brutalist_discover, cli_agent_roster). The roast_ prefix appears on unrelated tools and prefix families (brutalist_, cli_, roast_) don't follow a single predictable pattern.
Four tools is slightly thin but reasonable for a focused critique/debate server. The presence of a discovery tool hints at a larger intended toolset that isn't surfaced, but the count itself isn't problematic.
The surface covers single-panel critique, multi-agent debate, agent discovery, and roster inspection — a fairly full lifecycle for adversarial analysis. Minor gap: discovery implies additional brutalist tools that aren't actually exposed here.