/

/

Costory's FinOps agent, in Gemini CLI

Costory's FinOps agent, in Gemini CLI

Not yet documented

Costory's FinOps agent, in Gemini CLI

Generic remote MCP (direct URL config)

Why use Gemini CLI for FinOps

Gemini CLI is already where many engineers ask questions. With Costory's MCP server, those questions can be answered with your real cost data: spend from every provider, normalized and allocated to teams and features, with the deploys and metrics that explain changes.

Set up Costory in Gemini CLI

Gemini CLI supports MCP servers. Costory has not published a dedicated Gemini CLI guide yet.

What you can do

  • Investigate why spend moved, by team, service and environment.

  • Compare periods and see the deploys, incidents or provider events in the same window.

  • Create alerts, scheduled Slack reports (for example in #finops) and dashboards from the conversation.

  • Build and preview Virtual Dimensions to allocate spend when tagging is incomplete.

Example prompts

  • “Why did our cloud cost go up last week?”

  • “What does our OpenAI usage cost per feature this month?”

  • “Alert me if EC2 rises more than 10% vs the trailing 7 days.”

  • “Send a weekly report of the platform team's spend to #finops.”

FAQ

Is the Costory MCP server free to use with Gemini CLI?

The MCP server is included in Costory plans (from €250/month, billed annually, 30-day free trial).

Do I need to run anything locally?

No. Costory is a hosted remote MCP server with OAuth. Your client connects directly to https://app-api.costory.io/mcp; no local proxy or Node.js is needed.

Can the assistant change my cloud resources?

No. Costory has no write access to your cloud accounts.

Context layer

Your assistant starts from your Context layer: how cost is allocated, who owns what, which metrics explain it, and what past investigations concluded.

Set up Costory with one prompt

Set up Costory for my company. If the Costory MCP isn't connected yet, tell me how to add it (https://app-api.costory.io/mcp). Signing in creates my Costory account with a demo dataset. If my workspace only has the demo dataset, start there and walk me through two use cases before we touch my billing. 1) Allocation by team: draft a Team virtual dimension that maps AWS, GCP and Datadog costs to teams across all three providers, preview the cost per team and the unallocated share, and explain which rule caught what. No need to publish. 2) Unit economics: build a formula like cost per daily active user from a usage metric in the demo, show the trend and split it by team. If the demo has no usage metric, tell me which one I would connect. Then suggest one more demo use case worth trying. Once I've seen the results, help me connect my real cloud or LLM billing with Terraform so the same team split and formula run on my data.

The Costory MCP is hosted and requires a Costory account. Signing in creates one with a demo dataset, so you can try team allocation and unit economics before connecting your billing.

Connect in under 30 minutes, get your first optimization recommendation the next day.

30-day free trial. Plans from €250/month, billed annually. We recommend Team (€600/month) once more than one team uses Costory.

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Setup

Under 30 minutes

Data residency

EU

Access

Read-only on your cloud