AI Council← Back to app

MCP server · hosted

Run the Council from inside Claude.

Add the AI Council to Claude.ai, Claude Desktop, Claude Code, or any MCP-aware agent. Call list_council_models and run_council as tools. Nothing to install. The server is hosted at https://salvusai.app/api/connect/mcp and auth is handled with a one-click OAuth sign-in. Works on every plan; council runs debit your normal monthly quota.

list_council_models

Discover the catalog (so the host LLM can pick the panel)

run_council

5-model debate → Decision Brief, with chosen modelIds

1

Pick how you want to connect

Claude.ai, ChatGPT, Cursor, and VS Code connect directly. Claude Desktop and Claude Code use a small bridge.

In Claude.ai open Settings → Connectors → Add custom connector and paste:

MCP URL

https://salvusai.app/api/connect/mcp

Leave the OAuth Client ID + Secret fields blank, and Claude.ai will register itself automatically. Click Add, then click the new connector and sign in. We'll redirect you to a Salvus consent screen; one click and Claude.ai gets a token.

Once connected, ask Claude something like "Use the AI Council to debate whether we should ship the new pricing this quarter. Put GPT 5.5, Opus 4.7, and Gemini 3.1 Pro on the panel."

2

Try a call

Restart your client. The Council, chat, research, and image tools appear under MCP.

→ Use the AI Council to weigh in on whether we should migrate Postgres to ClickHouse for analytics.

→ List the available council models. I want to pick the panel myself.

→ Run the council with modelIds=["gpt-5.5", "claude-opus-4-7", "gemini-3.1-pro-preview"] on this question.

3

Optional: REST API keys

Only needed if you want to call /api/v1/council directly. MCP clients don't need this; they use OAuth.

Runs from MCP are saved to your history just like the web app. Public docs: github.com/john-salvus-ai/ai-council-mcp. Need help? info@salvus-ai.com.