# zcouncil

> Ask default AI council members through MCP. zcouncil routes one prompt to the Auto council members in parallel and returns each reply alongside a short synthesis. Available over an MCP server, a web app, and the `@zcouncil/cli` bridge.

## MCP

- Endpoint: https://api.zcouncil.com/mcp
- Transport: streamable HTTP, JSON-RPC 2.0
- Auth: `Authorization: Bearer <API token>` on every request
- Tool: `ask_council`
- Input: `{ "prompt": "..." }`
- Output: Markdown in `content` plus a canonical JSON mirror in `structuredContent`
- No public model, member, council, mode, or timeout knobs
- Discovery: https://zcouncil.com/.well-known/mcp.json

## Bridge

- Optional `@zcouncil/cli` bridge, powered by Agent Bridge, that routes supported Auto council members through local subscriptions (ChatGPT/Codex and Claude Code)
- Run: `npx -y @zcouncil/cli@latest bridge start`
- Default URL: `wss://api.zcouncil.com/bridge`
- MCP callers do not choose bridge routes; bridge presence is an internal routing detail

## Docs

- [MCP Quickstart](https://zcouncil.com/docs): Connect zcouncil to your MCP client in two minutes.
- [Bridge](https://zcouncil.com/docs/bridge): Use local subscriptions for supported council members.
- [API Tokens](https://zcouncil.com/docs/api-tokens): Authenticate the MCP server, `@zcouncil/cli` bridge, and any external integration.
- [MCP Tools](https://zcouncil.com/docs/mcp-tools): Wire-level reference for the ask_council MCP tool.

## Account

- Sign in: https://zcouncil.com/sign-in
- API tokens: https://zcouncil.com/chat#settings/tokens
- MCP setup guide: https://zcouncil.com/docs