The High Council MCP Server

What this does

The High Council exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

ANTHROPIC_API_KEY
OPENAI_API_KEY
GOOGLE_API_KEY
MISTRAL_API_KEY
DEEPSEEK_API_KEY
GROQ_API_KEY
TOGETHER_API_KEY
COHERE_API_KEY
OPENROUTER_API_KEY
ZAI_API_KEY
MAX_USD_PER_RUN
COUNCIL_MAX_USD_LIMIT
COUNCIL_WORKDIR

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install The High Council?

Run the Claude Code command in the install section to add The High Council to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with The High Council?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to The High Council as well.

Does The High Council need an API key?

Yes. Before it can run, set these environment variables: ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, MISTRAL_API_KEY, DEEPSEEK_API_KEY, GROQ_API_KEY, TOGETHER_API_KEY, COHERE_API_KEY, OPENROUTER_API_KEY, ZAI_API_KEY, MAX_USD_PER_RUN, COUNCIL_MAX_USD_LIMIT, COUNCIL_WORKDIR. They go in the env block of your MCP config.