Hanzo
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.

ToolRouteArgumentsDescription
delete_v1_flags_defs_keyDELETE /v1/flags/defs/{key}1DeleteFlagDefinition removes one flag definition by key and records the deletion in the change log.
get_v1_flags_activityGET /v1/flags/activity1ListFlagActivity returns the caller's flag change log newest-first: every create, update and delete,
get_v1_flags_defsGET /v1/flags/defs0ListFlagDefinitions returns every flag definition in the caller's (org, project) store, by key, with
get_v1_flags_defs_keyGET /v1/flags/defs/{key}1GetFlagDefinition returns one flag definition by key, or 404 when the caller's store has none under
get_v1_flags_healthGET /v1/flags/health0Health reports that the flag engine is serving.
get_v1_flags_waitlistGET /v1/flags/waitlist1WaitlistMode reports whether ONE host is currently gated by the launch waitlist.
post_v1_flagsPOST /v1/flags3Evaluate runs the caller's flag definitions for one identity and returns the PostHog-shaped verdict:
post_v1_flags_decidePOST /v1/flags/decide3Evaluate runs the caller's flag definitions for one identity and returns the PostHog-shaped verdict:
put_v1_flags_defs_keyPUT /v1/flags/defs/{key}0PutFlagDefinition creates or replaces the flag definition at the path's key and returns the stored r

All 834 tools · The door

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?