A side-by-side look at the Consult MCP and Omnara MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Consult MCP for coding agents work; choose Omnara for coding agents as a local process. You can also run both side by side in one mcpServers block.
agent, model, effort.OMNARA_TOKEN.Rows where the two servers differ are marked.
| Spec | C Consult MCP | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 56/100 · Good | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OMNARA_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,947 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Consult MCP | View Omnara |
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.No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Consult MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"omnara": {
"command": "npx",
"args": [
"-y",
"omnara"
],
"env": {
"OMNARA_TOKEN": "YOUR_OMNARA_TOKEN_HERE"
}
}
}
}