ZZ Stack — platform gateway

Every door below speaks MCP over streamable HTTP, and every MCP server
describes itself: connect and call tools/list to see exactly what it
offers, with each tool's arguments. Nothing here needs a manual.

https://api.zz-stack.com/core/mcp
    zz-core — everyone
    The process layer: skills, your team's knowledge store, documents and their gates, the sources behind them, and where each initiative stands.
    auth: Bearer <your token>

https://api.zz-stack.com/manage/mcp
    zz-access — everyone; the tool list is your role
    Access, yours and everybody's: your platform token, the team you act for and your client setup — and, if your role carries them, people, teams and who is on them. The tools you are offered are the ones your role can execute, so a tool you cannot see is a fact about you, not about the platform; whoami says which. Each tool still authorises per call, because a tool you can run for one team is not one you can run for another.
    auth: Bearer <your token>

https://api.zz-stack.com/eval/mcp
    zz-plugin-eval — everyone; a client reaches it through the zz-plugin-eval plugin
    Evaluating a plugin: what its real runs did, read from this platform's own door telemetry, and the ruler they are scored against. Separate from /core/mcp because it is one plugin's instrument rather than everybody's process layer — a client gets it by installing that plugin.
    auth: Bearer <your token>

No token yet?
  Sign in to the console with your passkey and issue one under Access:
  it is shown once, carries your identity and your team's access, and
  you can revoke it yourself at any time. No passkey yet? Ask a
  superadmin for an enrolment link. `client_setup` on the access door
  prints the setup for Claude Code.