MCP App Store
by KeenEthics
Mavvrik icon

Mavvrik MCP Server for ChatGPT

By Mavvrik

Overview

Mavvrik connects ChatGPT to your Mavvrik tenant so you can ask cloud cost questions and get answers from your actual data – no dashboard required. Ask about spend trends, cost drivers, budget variances, anomalies, and savings recommendations in plain language. Built for FinOps practitioners, cloud engineers, and anyone who needs fast cost intelligence without manually filtering reports. Current coverage includes Cloud Cost, Cost Variances, Recommendations, and Anomalies across your connected cloud accounts.

How to connect

  1. ChatGPT: Open the Mavvrik listing in the ChatGPT app directory and choose Connect. ChatGPT listing Mavvrik exposes 7 tools here.

Tools

execute

ChatGPT
Execute a GraphQL operation. Use the introspect tool to get information about the GraphQL schema. Always use the schema to create operations - do not try arbitrary operations. If available, first use the validate tool to validate operations. DO NOT try to execute introspection queries. Hint: Execution Rules Sequence: helloMCP → introspect → validate → execute. helloMCP supplies the reference date and display currency, introspect the field/argument/enum names, and validate catches schema errors before a query runs. Field and type names that were not read from introspect fail at validate or execute. PRE-FLIGHT CHECKLIST — 4 rules validate can't catch (they fail only at execute) 1. Series (`costs`/`aiCosts`/`saasCosts`/`k8sCosts`): pass BOTH `groupBy` and `xAxis` (never category). 2. `limit`: only `10/20/30/50/100`, or `-1` for all/total — never 0 or arbitrary ints; always set it (default 20). REQUIRED for *TopEntries AND costVariances (no backend default → omitting fails with Unrecognized name: undefined). 3. `options` (cloud/resource): `discount`/`refund`/`tax` + exactly one of `default`/`net`/`amortized`/`net_amortized` — the baseline is ["default","discount","refund","tax"]; swap only the variant when the user asks (SaaS / GenAI / agent / code-assist: []; K8s cost / datacenter: ["default"]). Other strings are silently dropped. 4. Introspect `Filter` before building one — it's flat typed fields, no json wrapper. Two totals that are computed, not read - Cost-variance net = (this-period total) − (prior-period total). Summing the per-group deltas is approximate — they are rounded and drop unattributed rows. - Coverage is ONE month's row: Usage Hours is the covered (ri+sp) hours, not total hours. STEP 0 — Session context: helloMCP is the source of the current date/time and the tenant's display currency. helloMCP.datetime is the reference point for every relative date ("last 7 days", "this month"); the server clock and the tenant's date are not otherwise knowable here. helloMCP.currency (e.g. "USD", "EUR") is the currency every cost figure in the session is denominated in, and both values hold for the whole session. helloMCP returns { name, datetime, currency, settings, tagPolicies }. It does NOT return default cost options — for standard cloud cost + resources use the fixed baseline ["default","discount","refund","tax"] (variant default = actual/blended on-demand, NOT amortized); only when the user asks for a different variant, swap the single variant flag per the Cost Variant Selection rule (e.g. ["amortized","discount","refund","tax"]). There is NO field echoing back which options ran: CostTopEntriesResponse returns only topEntries and total, so the variant a figure used is knowable only from the request that produced it. Also cache helloMCP.settings — the tenant's saved defaults, each an array of {id,name,scope,...} groups, that feed your thresholds (anomaly) and savings-floor inputs: - settings["cost-anomalies"] → the tenant's anomaly threshold ALREADY in the canonical GROUPED shape [{id,name,scope,thresholds:[{type,value,relationship}]}]. AnomalyOption.thresholds is OPTIONAL and the server applies NO default — it filters by EXACTLY what you pass, so omitting it returns EVERY anomaly (sub-dollar noise included). So pass one in almost every case: for "the configured / my usual threshold" (the common case) pass this VERBATIM as AnomalyOption.thresholds; to override, keep that exact grouped shape and change only the inner rule values; only OMIT thresholds when the user explicitly wants ALL anomalies. NEVER flatten it to [{type,value}] (without the wrapping {id,name,scope,thresholds:[...]} group the server can't key on it and the filter is dropped). A settings group may carry an alerts array; strip it, only {id,name,scope,thresholds} is read. - settings["savings-thresholds"] → the tenant's savings floor [{id,name,scope,threshold:<number>}] — pass it as the thresholds for recommendation/savings …

helloMCP

ChatGPT
mvk-hello Session initialization — call ONCE at the start of every session. Returns a Json object: { "name": "...", "datetime": "...", reference timestamp for all date-sensitive queries "currency": "USD", tenant display currency "uiOptions": { the effective cost options / anomaly thresholds this tenant/user "cost": { "options": ["discount","refund","tax"] }, gets when those inputs are OMITTED "anomaly": { "thresholds": [{ "id":"default","name":"Default","scope":null, "thresholds":[{"type":"amount","value":0.01,"relationship":"AND"}] }] } } } REUSE uiOptions.anomaly.thresholds VERBATIM as AnomalyOption.thresholds whenever the user wants "the configured / my usual threshold" — it is already in the canonical GROUPED shape [{ id, name, scope, thresholds:[{type,value,relationship}] }]. To override, keep that exact grouped shape and change only the inner rule values (e.g. value: 50) — never flatten it to [{type,value}]. A hello group may also carry an alerts array — strip it; only {id,name,scope,thresholds} is read. uiOptions is the no-override default and may age within a session. The server applies NO anomaly-threshold default — it filters by EXACTLY the thresholds you pass, so pass uiOptions.anomaly.thresholds (omitting it returns ALL anomalies).

introspect

ChatGPT
Get GraphQL type information - T=type,I=input,E=enum,U=union,F=interface;s=String,i=Int,f=Float,b=Boolean,d=ID;@D=deprecated;!=required,[]=list,<>=implements; Hint: Schema Discovery This tool reports what the schema actually declares. Field, argument and type names that did not come from it fail at validate or execute — the schema is the only record of what exists. Workflow Step 0 — Session context: helloMCP carries the current date/time for the session; date-sensitive queries depend on it. Step 1 — Initialize: Run ONE introspection on the root Query type at depth 1. This gives you the full list of available queries and their signatures. Step 2 — Deep Dive: For each query you plan to execute, introspect its dependencies: - Return types: If it returns an OBJECT, INTERFACE, or UNION → introspect that type to discover selectable fields. - Input types: If it takes INPUT_OBJECT arguments (option, filter, search) → introspect to learn its inputFields. Json-typed fields inside them (thresholds, tags, vtags) are free-form scalars — nothing to introspect. Step 3 — Mark Required Fields: Note every field marked "EFFECTIVELY REQUIRED" or ending with !. A query omitting one of these fails. Key Principles - Introspection results are your ONLY authority on what fields exist and what's required. - Never guess enum values (groupBy, yAxis, etc.) — always derive them from introspecting the relevant enum type. - Results are valid for the entire session, so a type already introspected does not change; a field error is the signal that one needs re-reading. - If a field name or type is ambiguous, introspect again — don't assume.

list_tenants

ChatGPT
List the tenants you're authorized to switch to (for use with the tenant_id parameter on execute/execute_sql/rest_invoke). Root sees all; admins see their children.

rest_invoke

ChatGPT
Read one Mavvrik REST management resource discovered via rest_search, using structured arguments (no code). GET operations only — this surface cannot create, update or delete. Targets the Mavvrik management API at https://api.mavvrik.ai. Your tenant is applied automatically from your credentials — do NOT put a tenant in args. To query a DIFFERENT tenant you are authorized for, pass the optional top-level tenant_id. Example: operation="get_tenantId_budget_budgetId", args={"budgetId": "z4ssydfhwq"}.

validate

ChatGPT
Validates a GraphQL operation against the schema. Use the introspect tool first to get information about the GraphQL schema. Operations should be validated prior to calling the execute tool. Hint: Validation validate checks an operation against the schema without running it, so a schema error surfaces here rather than as an execute failure. - If validation passes → proceed to execute. - If validation fails → re-introspect the failing type. Do NOT guess the fix. - If validation fails twice on the same type → re-introspect from the root query signature down to the failing type, then try again.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/mavvrik"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/mavvrik)