In-depth architectural comparison of the Llm Council and Standard Vocal MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Llm Council
Conversational AI · Local stdio
Quality: 43/100 (Fair) | Auth: API Key required
Standard Vocal MCP
Conversational AI · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Llm Council if you need specialized Conversational AI tools running via a local process. Choose Standard Vocal MCP if your workspace requires Conversational AI integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Llm Council when:
You need dedicated capabilities in the Conversational AI domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: OPENROUTER_API_KEY.
Multi-LLM deliberation with anonymized peer review. Runs a 3-stage council: parallel responses → anonymous ranking → synthesis. Based on Andrej Karpathy's LLM Council concept.
Voice Agent Factory for Vapi phone agents: vertical templates, self-testing agents, audio forensics, prompt versioning, and CI regression gates. npx -y standard-vocal-mcp
Category & Scope
Tools & Capabilities Breakdown
Llm Council Tools (6)
Three-stage multi-LLM deliberation
Anonymous response ranking
Chairman-based final synthesis
Decision trace and ranking persistence
Local JSON conversation history
Server-Sent Events progress updates
Standard Vocal MCP Tools (6)
list_agents
Lists the assistants on the account (id, name, model, voice, transcriber) — the entry point to find an `assistantId`.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Llm Council is categorized under Conversational AI and uses a local stdio subprocess. In contrast, Standard Vocal MCP belongs to Conversational AI using local stdio subprocess. Select Llm Council when you need capabilities focused on conversational ai and Standard Vocal MCP when you require tools for conversational ai.
One tool = one full vertical deployment. `deploy_agent(vertical: elagueur\
run_eval
The agent tests itself.** Fetches the live system prompt, simulates N scripted scenarios against the configured LLM, scores behavior (close speed, no price quoting, spelled digit confirmation, urgency priority, solicitation refusal), returns a `/100` grade with PASS / WARN / FAIL. No audio, no bill…
audio_forensics
Downloads the 3 recording tracks of a call (mono / customer / assistant), runs RMS-per-window analysis, and **locates the noise source**. Automates the exact manual investigation that found a "computer noise" issue was injected downstream of the caller's mic, not in Vapi.
prompt_diff
Prompts as code. `snapshot` captures the live prompt into local history, `diff` compares two versions, `rollback` pushes an old prompt back to Vapi.
regression_gate
CI for prompts.** Runs `run_eval` and blocks the update if the score regressed vs the stored baseline. Returns allow/deny with the reason.