MCP Server

hypertune

io.usefulapi/hypertune
Developer Tools Public & reachable MCP 2026-07-28

What this MCP does

Evaluates, inspects, lists, and queries Hypertune feature flags through its GraphQL endpoint.

hypertune_evaluate
Evaluate feature flags
Evaluate one or more feature flags for a given context and get their resolved values. Builds `query { root(context: <context>) { <selection> } }`. Provide `selection` = the flag fields to read (e.g. `exampleFlag anotherFlag { nestedField }`) and `context` = the evaluation context (environment + user/attributes). Every field must supply all of its arguments (Hypertune reduces the flag logic to a JSON result). Use hypertune_list_flags / hypertune_introspect first if you don't know the flag names.
Read only
Input schema
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['selection'], 'properties': {'context': {'type': 'object', 'description': 'Evaluation context object, inlined as the `context` arg. e.g. {"environment":"production","user":{"id":"u_123","email":"a@b.com"}}. Omit to return the flag LOGIC instead of a reduced value.', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'selection': {'type': 'string', 'description': 'GraphQL selection of flag fields under root, e.g. `exampleFlag` or `homePage { showBanner } exampleFlag`.'}}}
hypertune_get_logic
Get flag logic (unreduced)
Fetch the underlying LOGIC of flags without reducing them — i.e. `query { root { <selection> } }` with no context. Returns the flag's conditional expression / rules rather than a single resolved value, useful for inspecting how a flag is configured. If the schema requires a context arg you can still pass a partial one via `context`.
Read only
Input schema
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['selection'], 'properties': {'context': {'type': 'object', 'description': 'Optional partial context, inlined as the `context` arg if the schema requires it.', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'selection': {'type': 'string', 'description': 'GraphQL selection of flag fields under root, e.g. `exampleFlag`.'}}}
hypertune_introspect
Introspect the GraphQL schema
Run a GraphQL introspection query to discover the project's schema — all types and fields, including the available flags and the shape of the evaluation context. Best-effort: some edge deployments disable introspection, in which case this returns a clear error (use hypertune_query with a known flag name instead).
Read only
Input schema
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {}}
hypertune_list_flags
List feature flags
List the project's top-level feature flags (the fields of the query root type) with their return types and descriptions, derived from GraphQL introspection. A convenient first call to see what flags exist before evaluating. Requires introspection to be enabled on the edge endpoint.
Read only
Input schema
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {}}
hypertune_query
Run a raw GraphQL query
Run an arbitrary GraphQL query (and optional variables) against the Hypertune edge endpoint. Power-user escape hatch for full control — each Hypertune project has its own generated schema, so this handles any flag shape, nested selections, inline enum literals, or variables the convenience tools can't express. The query root field is `root(context: ...)`.
Read only
Input schema
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': 'A complete GraphQL query string, e.g. `query { root(context: {environment: "production"}) { myFlag } }`.'}, 'variables': {'type': 'object', 'description': "Optional GraphQL variables object matching the query's declared variables.", 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}}}
Changed
hypertune_list_flags
Oct. 1, 2026, 2:43 a.m.
Changed
hypertune_introspect
Oct. 1, 2026, 2:43 a.m.
Changed
hypertune_query
Oct. 1, 2026, 2:43 a.m.
Changed
hypertune_get_logic
Oct. 1, 2026, 2:43 a.m.
Changed
hypertune_evaluate
Oct. 1, 2026, 2:43 a.m.
Added
hypertune_list_flags
Sept. 21, 2026, 2:44 a.m.
Added
hypertune_introspect
Sept. 21, 2026, 2:44 a.m.
Added
hypertune_query
Sept. 21, 2026, 2:44 a.m.
Added
hypertune_get_logic
Sept. 21, 2026, 2:44 a.m.
Added
hypertune_evaluate
Sept. 21, 2026, 2:44 a.m.