Costory
About
Ask your AI assistant a cost question. Get allocation, correlation, and explanation in one response. Costory connects Claude, Codex, or Cursor to normalized cost data across AWS, GCP, Azure, Datadog, OpenAI, and Anthropic.
Details
- Author
- costory-io
- Categories
- Cloud Service, Infrastructure, Other
Jump to
Setup
Install Costory in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/costory-io/costory-plugin
Follow the installation instructions in the repository README, then restart your MCP client.
Costory FinOps MCP: agent skills and plugin
TheCostory FinOps MCPis a hostedModel Context Protocolserver that lets Claude, Cursor, VS Code, Codex, or Dust answer questions about your cloud and AI spend.
Feeding raw AWS or GCP billing lines into a prompt does not work. Costory acts as acontext layer: it normalizes billing from AWS, GCP, Azure, Snowflake, Datadog, OpenAI, and Anthropic into one schema, allocates shared and untagged cost from real usage metrics, and correlates spend with deploy events and incidents. The assistant then calls structured tools against data that is already allocated and explained.
This repository holds theagent skillsthat sit on top of those tools: the workflows that turn "why did prod cost jump last week" into the right sequence of tool calls.
- Full MCP documentation:docs.costory.io/features/mcp
- Endpoint:https://app-api.costory.io/mcp
- Auth:OAuth, no IAM credentials, no Docker, no local server
You need a Costory workspace withbilling data connected. A 15-day trial is available.
Claude Desktop / Claude Code / Cursor / VS Code:add a custom connector pointing athttps://app-api.costory.io/mcp, then complete the OAuth login in the browser window that opens. Per-client walkthroughs with screenshots are in theMCP docs.
This repo ships an.mcp.jsonyou can copy:
{ "mcpServers": { "costory": { "type": "http", "url": "https://app-api.costory.io/mcp", "oauth": { "callbackPort": 8080 } } } }
For clients without native remote-MCP support, proxy it withmcp-remote:
{ "mcpServers": { "costory": { "command": "npx", "args": ["-y", "mcp-remote", "https://app-api.costory.io/mcp"] } } }
The server exposes tools in five groups. Names and payloads are versioned; theAPI referenceis the source of truth.
Write tools act only inside your Costory workspace. Query scoping follows the calling user's workspace role.
Skills are the workflow layer: each one encodes how to sequence the tools above for a class of question, so the assistant does not have to rediscover it.
Recipes currently cover budget-vs-actual dashboards, EC2 spike alerts, prod-vs-R&D splits, untagged coverage, marketplace spend, provider credits, namespace cost, compute drilldowns, and period-change explanation. Seeplugins/costory/skills/recipes/.
# Claude Code claude plugin marketplace add costory-io/costory-finops-mcp-skills claude plugin install costory@costory # Codex codex plugin marketplace add costory-io/costory-finops-mcp-skills codex plugin add costory@costory
.mcp.json ← ready-to-copy MCP client config skills.json ← MCP skillId -> SKILL.md path .claude-plugin/marketplace.json plugins/costory/ .claude-plugin/plugin.json skills/ query/SKILL.md virtual-dimensions/SKILL.md dashboards/SKILL.md reports/SKILL.md recipes/SKILL.md + recipe library
{ "skillId": "dashboards", "path": "plugins/costory/skills/dashboards/SKILL.md" }
SeeAGENTS.mdfor layout rules, version bumps, and validation. UseSKILL_TEMPLATE.mdwhen adding a skill.
Deploy and operate workloads, secrets, and networking across AWS, GCP, Azure, and private clouds.
Retrieve AWS spend data from Cost Explorer and Amazon Bedrock usage data from CloudWatch logs.
Manage virtual machines across multiple cloud providers, including AWS EC2, Azure Virtual Machines, and GCP Compute Engine.
Local-first FinOps copilot: ask about your AWS, Azure, GCP, and SaaS costs in plain English. Anomaly detection, rightsizing, idle-resource cleanup, and Jira/Linear ticketing, all in your own Claude. Credentials never leave your machine.
An MCP server for managing Red Hat OpenShift clusters via the OCM API.
Manage cloud infrastructure using Pulumi's Infrastructure as Code (IaC) platform. Requires the Pulumi CLI to be installed.
Unified API for AI agents to deploy cloud infrastructure across AWS, Azure, and GCP autonomously
MCP server to query and govern your AWS, GCP & Azure cloud estate (and AI runtimes like Bedrock & Vertex AI) from Claude Code or Cursor surfaces waste, cost, ownership, and 400+ audit findings across 200+ resource types.
An MCP server for querying and interacting with AWS Athena.
Get prescriptive CDK advice, explain CDK Nag rules, check suppressions, generate Bedrock Agent schemas, and discover AWS Solutions Constructs patterns.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
