CodeZaiku vs Consult MCP
A side-by-side look at the CodeZaiku and Consult MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CodeZaiku for coding agents work as a local process; choose Consult 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?
Choose CodeZaiku when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CODEZAIKU_PREFIX, CODEZAIKU_VERSION, CODEZAIKU_RUNTIME. - You want tools like
code, fix, explore_and_fix.
Choose Consult MCP 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
agent, model, effort.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 63/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | CODEZAIKU_PREFIXCODEZAIKU_VERSIONCODEZAIKU_RUNTIME | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 11 | 5 |
| Full listing | View CodeZaiku | View Consult MCP |
Tools & capabilities
CodeZaiku tools 11
codeRun CodeZaiku's coding familiar on an existing project: it reads the codebase, edits files, runs the toolchain, and verifies via the project's own tests. Use for bug-fix, add-feature, refactor, test-coverage, incident, and API-migration tasks. Blocks until the loop finishes.fixRun CodeZaiku's autonomous-SRE operator on a stack or host: senses health, localizes the root cause, applies a fix (validated card or read-only-recon-derived), verifies, rolls back on failure, and harm-checks. Bounded by blast-radius and an authority ladder (observe<localize<propose<guarded<unattended). Blocks until it concludes.explore_and_fixExplore an entire machine and fix what's broken ? boundary = THAT machine. Enumerates all docker compose stacks, failed systemd units, and host disk/memory pressure; runs the SRE operator on each unhealthy compose stack (blast-radius + authority-ladder bounded); surfaces systemd/host issues for attention. Use to autonomously triage a whole box, not one known stack.reviewREAD-ONLY code review: navigate a project (or a git diff) and return a structured findings list ([high|med|low] file:line ? problem ? suggested fix) covering correctness, security, and maintainability. Modifies nothing.researchResearch a question on the WEB (searches, fetches and reads real sources, then synthesizes a cited answer). mode=broad surveys the landscape across many sources; mode=depth reads the best sources thoroughly to answer one narrow question. Read-only.research_memoryInspect the RESEARCH MEMORY POOL ? findings accumulated from earlier research runs. Omit query for a summary of what has been researched; pass a query to recall relevant prior findings (so you can build on them instead of re-researching).investigateREAD-ONLY incident diagnosis / RCA on a stack or host: senses and localizes the root cause but does NOT remediate. The safe 'just tell me what's wrong' entry point.secureSECURITY review of a machine or stack: static posture (privileged containers, docker.sock mounts, datastores published on 0.0.0.0, weak/default credentials, image CVEs) PLUS runtime intrusion detections from the syscall detector, and for a live detection a read-only investigation proposing ONE surgical containment command. REPORTS ONLY ? it never applies a containment action, because a wrong containment is a self-inflicted outage.record_conventionRecord a CONVENTION for a project ? a norm the familiar should follow HERE (typically from a bondholder accept/correct on its work). Builds the project's coding DNA, which is loaded into context on future `code` runs for that project.show_conventionsShow a project's accumulated conventions (its coding DNA).job_statusPoll an async tool job submitted with async:true. Returns 'running', or the final result when the job is done/failed.
Consult MCP tools 5
agent`claude`, `codex`, `grok` or `agy` (Antigravity, Gemini models).modelpassed through to that CLI (`opus`, `gpt-6-astra`, `grok-4.7`, `gemini-3.1-pro-high`, …). Omit it to use the CLI's default.effort`low`, `medium` or `high`.session_idcontinues an earlier conversation with the same advisor.cwdthe directory the advisor can read. Defaults to the directory the host agent started the server in, which is normally its repo.
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.
CodeZaiku
{
"mcpServers": {
"codezaiku": {
"command": "npx",
"args": [
"-y",
"@wyrdsekai/codezaiku-mcp"
],
"env": {
"CODEZAIKU_PREFIX": "YOUR_CODEZAIKU_PREFIX_HERE",
"CODEZAIKU_VERSION": "YOUR_CODEZAIKU_VERSION_HERE",
"CODEZAIKU_RUNTIME": "YOUR_CODEZAIKU_RUNTIME_HERE"
}
}
}
}
Consult MCP
{
"mcpServers": {
"consult-mcp": {
"command": "npx",
"args": [
"-y",
"consult-mcp@latest"
]
}
}
}
Frequently asked questions
CodeZaiku is categorized under Coding Agents and uses a local stdio subprocess. Consult MCP belongs to Coding Agents and uses a local stdio subprocess. Pick CodeZaiku for coding agents work and Consult 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.
CodeZaiku has no declared pricing — check the project's own site. Consult MCP has no declared pricing — check the project's own site. 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 codezaiku and consult-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CodeZaiku has a quality signal of 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Consult MCP has 61/100 (Good) with 0 views, 0 installs and 1 GitHub stars.