Integrations

MCP Server

AI Council includes a Model Context Protocol (MCP) server for integration with AI assistants like Claude and Cursor.

ai-council mcp

The MCP server exposes AI Council's functionality as tools that can be invoked by AI assistants, enabling them to request code reviews during conversations.

All analysis tools accept optional parameters:

• gitScope: which working-tree changes to include: "auto" (default; staged → unstaged → HEAD fallback), "staged", "unstaged", or "all".
• suggestions: when true, agents include code fix examples in their vote when they recommend REVISE or REJECT. See Fix Suggestions.
• preContext: when true, enrich reviewer prompts with AST-extracted, embedding-ranked code context. See Pre-Review Context.
• preContextTopK: number of top code units to inject (implies preContext, default: 5).
• deepAnalysis: when true, use file-by-file deep review with structured findings and project-rule awareness. See Deep Analysis.
• agent: when true, use two-pass Claude Agent SDK review with codebase exploration (implies deepAnalysis). See Agent Review.
• graph: when true, force-enable graph context discovery. See Graph Context.
• noGraph: when true, disable graph context for this tool call (cannot combine with graph).
• cwd: working directory for git commands (defaults to process cwd). Useful when the assistant is not running in the repo root.

Claude Integration

Add AI Council to Claude Code for seamless code review within your Claude conversations. The plugin is the shortest path: it registers the MCP server for you and adds slash commands and skills on top.

claude plugin marketplace add Zelltron/ai-council-plugin
claude plugin install ai-council@ai-council

Restart Claude Code, then run /mcp and confirm ai-council is connected. Plugins load at session start, so a correct install looks broken until you restart. The plugin fetches the review engine on demand, so it needs no separate CLI install.

Alongside the review tools, it adds five slash commands for seating a specific panel:

• /council-review: quality, hidden risk, and unnecessary complexity
• /council-security: trust boundaries, injection, and unsafe assumptions
• /council-perf: CPU, allocation, render frequency, async and IO
• /council-arch: whether the abstraction is justified, and what hurts in 6 to 12 months
• /council-sanity: whether this is over-engineered, and the simplest acceptable version

Each accepts the same arguments as the tools, for example /council-review --branch=main --suggestions or /council-security --pr=123. Two skills ship with it as well: one that lets Claude convene the Council on its own judgment, and one that diagnoses license and API key problems during setup.

Registering the server manually

If you prefer not to use the plugin, install the CLI and register the MCP server directly.

claude mcp add --transport stdio ai-council -- ai-council mcp

Once configured, Claude can invoke AI Council to review code snippets or git diffs during your conversation. You get the same review tools this way, without the slash commands or skills.

Cursor Integration

Configure AI Council as an MCP server in Cursor for integrated code review.

{
  "mcpServers": {
    "ai-council": {
      "command": "ai-council",
      "args": ["mcp"],
      "env": {
        "AI_COUNCIL_LICENSE_KEY": "your-license-key",
        "OPENAI_API_KEY": "your-openai-key",
        "GEMINI_API_KEY": "your-gemini-key",
        "AI_COUNCIL_MODEL": "gpt-5.4-mini",
        "AI_COUNCIL_GEMINI_MODEL": "gemini-3.6-flash"
      }
    }
  }
}