Cloud MCPflags
flags
9 MCP tools on the Hanzo cloud door that call the flags API.
The 9 tools tools/list names for flags. Each dispatches to an operation in the flags API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_flags_defs_key | DELETE /v1/flags/defs/{key} | 1 | DeleteFlagDefinition removes one flag definition by key and records the deletion in the change log. |
get_v1_flags_activity | GET /v1/flags/activity | 1 | ListFlagActivity returns the caller's flag change log newest-first: every create, update and delete, |
get_v1_flags_defs | GET /v1/flags/defs | 0 | ListFlagDefinitions returns every flag definition in the caller's (org, project) store, by key, with |
get_v1_flags_defs_key | GET /v1/flags/defs/{key} | 1 | GetFlagDefinition returns one flag definition by key, or 404 when the caller's store has none under |
get_v1_flags_health | GET /v1/flags/health | 0 | Health reports that the flag engine is serving. |
get_v1_flags_waitlist | GET /v1/flags/waitlist | 1 | WaitlistMode reports whether ONE host is currently gated by the launch waitlist. |
post_v1_flags | POST /v1/flags | 3 | Evaluate runs the caller's flag definitions for one identity and returns the PostHog-shaped verdict: |
post_v1_flags_decide | POST /v1/flags/decide | 3 | Evaluate runs the caller's flag definitions for one identity and returns the PostHog-shaped verdict: |
put_v1_flags_defs_key | PUT /v1/flags/defs/{key} | 0 | PutFlagDefinition creates or replaces the flag definition at the path's key and returns the stored r |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?