Costory FinOps MCP changelog

https://docs.costory.io/llms.txt

− - [Welcome to Costory](https://docs.costory.io/get-started/welcome.md): Cloud cost reporting for DevOps: connect AWS, GCP, and Azure billing, use Costory MCP with Claude or Cursor, and automate FinOps updates.− - [Quickstart: How to set up automated cloud cost reporting in 30 minutes](https://docs.costory.io/get-started/quickstart.md): Step-by-step guide to connect AWS, GCP, Azure and Datadog to Costory. Set up automated FinOps Slack & Teams cost reports in 30 minutes, free trial included.− - [Billing Data](https://docs.costory.io/setup/billing.md): Set up cloud billing data sources in Costory via Terraform or manual configuration. Supports AWS CUR 2.0, GCP BigQuery, Azure Cost Management, Oracle Cloud, Snowflake, Scaleway, Cloudflare, and SaaS providers.− - [Azure Billing Setup](https://docs.costory.io/setup/billing/azure.md): Connect Azure Cost Management exports to Costory via Terraform or manual setup.− - [BytePlus Billing Setup](https://docs.costory.io/setup/billing/byteplus.md): Connect BytePlus Platform billing to Costory with an IAM Access Key. Import account bill details, including Seedance and ModelArk, into Explorer next to AWS, GCP, and Azure.− - [Elastic Cloud Billing Setup](https://docs.costory.io/setup/billing/elastic-cloud.md): Connect Elastic Cloud organization billing to Costory with an Organization API key. Covers setup, historical sync, and what cost grain and dimensions you get in Explorer.− - [Kling AI Billing Setup](https://docs.costory.io/setup/billing/kling-ai.md): Connect Kling AI Open Platform pack usage and wallet charges to Costory with a Bearer API key. Import video-generation spend into Explorer next to AWS, GCP, and Azure.− - [FinOps MCP: Cloud Cost Automation for AI Assistants and Slack](https://docs.costory.io/features/mcp.md): Use the Costory FinOps MCP to query AWS, GCP, and Azure spend from Claude, Cursor, or VS Code. Investigate cost spikes, create alerts, and send Cost Reports via Model Context Protocol.− - [Explorer](https://docs.costory.io/features/cost-explorer.md): Use Costory Explorer to query AWS, GCP, and Azure costs with filters, group-bys, comparison periods, and saved context before turning the result into dashboards, alerts, reports, or MCP prompts.− - [Dashboard Templates](https://docs.costory.io/features/dashboards/templates.md): Use pre-built FinOps dashboard templates for executive cloud cost reporting, team showback, Savings Plan coverage, Kubernetes cost allocation, network costs, and storage optimization.− - [Dashboard Widgets and Chart Types](https://docs.costory.io/features/dashboards/widgets.md): Choose dashboard widgets and chart types for cloud cost dashboards, including bar charts, line charts, waterfall charts, doughnut charts, tables, KPI cards, budget trackers, and BigQuery SQL export.− - [Tag & Allocate Cloud Costs](https://docs.costory.io/features/tagging.md): FinOps cost allocation made simple. Create dimensions, allocate untagged resources, and split shared costs across AWS, GCP, and Azure without touching your cloud console.− - [Dimensions](https://docs.costory.io/features/tagging/dimensions.md): Create cloud cost allocation dimensions that merge native AWS, GCP, and Azure tags, normalize values, and define rule-based virtual dimensions for team, product, or environment reporting.− - [Split Shared Infrastructure Costs Across Teams](https://docs.costory.io/features/tagging/shared-cost-allocation.md): Allocate shared cloud infrastructure costs like Cloud SQL, RDS, or network to teams based on actual usage metrics from any External metric source: Datadog, Datadog CI Visibility, Amplitude, BigQuery, Google Sheets, Tsuga, CloudWatch, S3, Snowflake, or Custom metrics.− - [Cost Reports](https://docs.costory.io/v2/Automate/reports.md): Schedule recurring cloud cost reports to Slack, Microsoft Teams, or email from a dashboard, widget, or Explorer view, in the UI, from chat, or via the API.− - [Cost Digest: automate your FinOps reporting](https://docs.costory.io/features/digest.md): Automatically surface and triage the cloud cost changes that matter for FinOps reporting. Digest ranks every significant cost shift by dollar impact and generates AI incident reports with root cause analysis.− - [Alerts](https://docs.costory.io/features/alerts.md): Monitor cloud spend and custom formulas against a single trigger condition. Build alerts in the UI or through the Costory MCP with the same condition string, then get notified in Slack, Teams, or email.− - [Contracted Cost vs Billed Cost: Savings Plan discount sharing issues](https://docs.costory.io/docs/savings-plan-cost-fluctuation.md): Learn why Contracted Cost gives platform and engineering teams a stable, usage-driven view of AWS and GCP cloud spending, avoiding misleading Savings Plan cost fluctuations.− - [Settings](https://docs.costory.io/get-started/settings.md): Invite users as an Admin from the account name in the left sidebar. Find Costory settings, organization Invites, Teams, data integrations, API keys, plans, and invoices.− - [Identity and Access](https://docs.costory.io/docs/sso-access-control.md): Compare Costory identity and access options across Starter, Team, Business and Custom, including auto-join, single sign-on, directory sync, role-based access control, and security scope.− - [LLM Cost Allocation: Track AI Spend by Team, Feature, and Customer](https://docs.costory.io/use-cases/llm-ai-cost.md): Allocate and track LLM costs from Anthropic, OpenAI, Azure OpenAI, AWS Bedrock, GCP Vertex, and Mistral across teams and features. Learn cost per token attribution, showback, and chargeback strategies for shared API keys.− - [Split Shared API Costs Across Teams Using Usage Metrics](https://docs.costory.io/use-cases/reallocate_api_costs.md): Allocate untagged or shared API costs to the right teams based on actual usage data. This guide walks you through usage-based shared cost allocation with Costory, from connecting an external metric to building a reusable chargeback model.− - [Automate Monthly Cloud Cost Reporting](https://docs.costory.io/automate-reporting/monthly-reviews.md): Stop spending hours building monthly cloud cost reports. Use a Cost digest inside Costory Reports to generate executive summaries, root-cause analyses, and shareable Slack or email digests.− - [Decentralize FinOps with Per-Team Cost Reports](https://docs.costory.io/automate-reporting/decentralize-finops.md): Scale cost visibility across engineering teams by scoping automated reports to each squad. Deliver cloud cost insights via Slack, Teams, or email, no billing console access needed.− - [Enrichments API](https://docs.costory.io/api-reference/enrichments/overview.md): Upload, test, and publish Costory enrichment lookup files over HTTP. Store drafts, publish the set in one call, and trace a billed row before the next billing update.− - [ ](https://docs.costory.io/docs/finops-memes.md)+ - [Welcome to Costory](https://docs.costory.io/get-started/welcome.md): Costory is the cost context your engineers and their AI assistants work from: every bill in one model, allocated with YAML in git, answered in Claude, Cursor and Slack.+ - [Concepts](https://docs.costory.io/get-started/concepts.md): The five ideas Costory is built on: allocation as code, context and memory, every feature at a fair price, a product operated by humans or agents, and FinOps data pushed and pulled where engineering and product teams work.+ - [Quickstart: connect your first bill in 30 minutes](https://docs.costory.io/get-started/quickstart.md): Connect AWS, Google Cloud, Azure or an LLM provider with Terraform, CloudFormation or by hand, then get cost by team in Slack and in Claude. 30-day free trial, no credit card.+ - [Billing Data](https://docs.costory.io/setup/billing.md): Connect cloud and SaaS billing data to Costory via Terraform or the UI: AWS CUR 2.0, GCP BigQuery, Azure Cost Management, Oracle Cloud, Snowflake, and more.+ - [Azure Billing Setup](https://docs.costory.io/setup/billing/azure.md): Connect Azure Cost Management exports to Costory with a Google federated credential. Paste Azure client ID and tenant ID. No SAS token.+ - [BytePlus Billing Setup](https://docs.costory.io/setup/billing/byteplus.md): Connect BytePlus Platform billing to Costory with an IAM Access Key and import account bill details, including Seedance and ModelArk, into Explorer.+ - [Elastic Cloud Billing Setup](https://docs.costory.io/setup/billing/elastic-cloud.md): Connect Elastic Cloud organization billing to Costory with an Organization API key: setup, historical sync, and the cost grain you get in Explorer.+ - [Kling AI Billing Setup](https://docs.costory.io/setup/billing/kling-ai.md): Connect Kling AI Open Platform pack usage and wallet charges to Costory with a Bearer API key, and see video-generation spend in Explorer.+ - [Nebius Billing Setup](https://docs.costory.io/setup/billing/nebius.md): Connect Nebius AI Cloud FOCUS 1.2 billing to Costory with a customer-owned Object Storage bucket, a periodic export, and a read-only access key.+ - [Costory FinOps MCP: setup for Claude, Claude Code, Cursor and Copilot](https://docs.costory.io/features/mcp.md): Connect the hosted Costory MCP to Claude, Claude Code, Cursor, VS Code (Copilot) or Dust with one URL and OAuth. Query allocated cloud, Kubernetes, data and LLM cost, and create alerts and reports from chat.+ - [Costory skills for AI assistants](https://docs.costory.io/features/skills.md): Open-source skills that teach Claude, Cursor, Codex and other agents how to run FinOps workflows on the Costory MCP, and how to install them.+ - [Terraform provider for Costory](https://docs.costory.io/setup/terraform.md): Install the Costory Terraform provider, authenticate with an API token, and manage billing datasources, enrichments and teams as code.+ - [Explorer](https://docs.costory.io/features/cost-explorer.md): Query AWS, GCP, and Azure costs in Costory Explorer with filters, group-bys and comparison periods, then turn the result into dashboards, alerts, or reports.+ - [Dashboard Templates](https://docs.costory.io/features/dashboards/templates.md): Pre-built FinOps dashboard templates for executive reporting, team showback, Savings Plan coverage, Kubernetes cost allocation, network, and storage.+ - [Dashboard Widgets and Chart Types](https://docs.costory.io/features/dashboards/widgets.md): Choose cloud cost dashboard widgets: bar, line, waterfall and doughnut charts, tables, KPI cards, budget trackers, and BigQuery SQL export.+ - [Tag & Allocate Cloud Costs](https://docs.costory.io/features/tagging.md): Create dimensions, allocate untagged resources, and split shared costs across AWS, GCP, and Azure in Costory, without touching your cloud console.+ - [Dimensions](https://docs.costory.io/features/tagging/dimensions.md): Create cost allocation dimensions that merge AWS, GCP, and Azure tags, normalize values, and define rule-based virtual dimensions for team reporting.+ - [Split Shared Infrastructure Costs Across Teams](https://docs.costory.io/features/tagging/shared-cost-allocation.md): Allocate shared cloud costs like Cloud SQL, RDS, or network to teams using usage metrics from Datadog, Amplitude, BigQuery, CloudWatch, Snowflake and more.+ - [Cost Reports](https://docs.costory.io/features/slack-reports.md): Schedule recurring cloud cost reports to Slack, Microsoft Teams, or email from a dashboard, widget, or Explorer view, in the UI, from chat, or via the API.+ - [Cost Digest: automate your FinOps reporting](https://docs.costory.io/features/digest.md): Digest ranks every significant cloud cost shift by dollar impact and generates incident reports with root cause analysis, so you triage what matters.+ - [Alerts](https://docs.costory.io/features/alerts.md): Monitor cloud spend and custom formulas against one trigger condition, built in the UI or through the Costory MCP, with Slack, Teams, or email notifications.+ - [Contracted Cost vs Billed Cost: Savings Plan discount sharing issues](https://docs.costory.io/docs/savings-plan-cost-fluctuation.md): Why Contracted Cost gives engineering teams a stable, usage-driven view of AWS and GCP spend, without misleading Savings Plan cost fluctuations.+ - [Settings](https://docs.costory.io/get-started/settings.md): Find Costory settings: invite users as an Admin, and manage organization Invites, Teams, data integrations, API keys, plans, and invoices.+ - [Security](https://docs.costory.io/docs/security.md): Costory cloud security controls, audits, and data protection practices+ - [Identity and Access](https://docs.costory.io/docs/sso-access-control.md): Compare Costory identity and access options across plans: auto-join, single sign-on, directory sync, role-based access control, and security scope.+ - [ ](https://docs.costory.io/docs/finops-memes.md)+ - [LLM Cost Allocation: Track AI Spend by Team, Feature, and Customer](https://docs.costory.io/use-cases/llm-ai-cost.md): Allocate and track LLM costs from Anthropic, OpenAI, Azure OpenAI, AWS Bedrock, GCP Vertex, and Mistral across teams, with showback and chargeback.+ - [Split Shared API Costs Across Teams Using Usage Metrics](https://docs.costory.io/use-cases/reallocate_api_costs.md): Allocate untagged or shared API costs to teams based on usage data, from connecting an external metric to a reusable chargeback model in Costory.+ - [Automate Monthly Cloud Cost Reporting](https://docs.costory.io/automate-reporting/monthly-reviews.md): Use a Cost digest in Costory Reports to generate monthly executive summaries, root-cause analyses, and shareable Slack or email cloud cost digests.+ - [Give every team its own cost report](https://docs.costory.io/automate-reporting/team-cost-reports.md): Scope automated cost reports to each engineering team and deliver them by Slack, Teams, or email, with no billing console access needed.+ - [Enrichments API](https://docs.costory.io/api-reference/enrichments/overview.md): Upload, test, and publish Costory enrichment lookup files over HTTP: store drafts, publish the set in one call, and trace a billed row.

description

FinOps harness MCP: cloud, data and LLM bills normalized and allocated to teams. Cloud read-only. → FinOps harness MCP: allocated cloud, data and LLM bills. Build on it or switch. Cloud read-only.

version

1.0.4 → 1.0.5

description

FinOps agent MCP: one allocated view of cloud, AI and data costs for your team. Starter $300/mo → FinOps harness MCP: cloud, data and LLM bills normalized and allocated to teams. Cloud read-only.

version

1.0.2 → 1.0.4

https://docs.costory.io/llms.txt

− - [FinOps MCP: Cloud Cost Automation for AI Assistants](https://docs.costory.io/features/mcp.md): Use the Costory FinOps MCP to query AWS, GCP, and Azure spend from Claude, Cursor, or VS Code. Investigate cost spikes, create alerts, and send Cost Reports via Model Context Protocol.− - [Get published label transformations](https://docs.costory.io/api-reference/dimensions/get-published-label-transformations.md): The currently published label configuration: which source columns are merged into each engineered dimension and how their values are mapped. This is the live configuration, not a draft — the client holds label edits until it calls `POST /dimensions/publish`.+ - [Databricks Billing Setup](https://docs.costory.io/setup/billing/databricks.md): Connect Databricks DBU billing and full workload cost (DBUs plus cloud VMs) in Costory. Level 2 ties each instance to the cluster and job that ran on it.+ - [FinOps MCP: Cloud Cost Automation for AI Assistants and Slack](https://docs.costory.io/features/mcp.md): Use the Costory FinOps MCP to query AWS, GCP, and Azure spend from Claude, Cursor, or VS Code. Investigate cost spikes, create alerts, and send Cost Reports via Model Context Protocol.+ - [Get published label transformations](https://docs.costory.io/api-reference/dimensions/get-published-label-transformations.md): The currently published label configuration: which source columns are merged into each engineered dimension and how their values are mapped. This is the live configuration, not a draft — the client holds label edits until it calls `POST /dimensions/publish`. `computeByName` is the per-label billing…

https://docs.costory.io/llms.txt

− - [Identity and Access](https://docs.costory.io/docs/sso-access-control.md): Compare Costory identity and access options across Copilot and Copilot Pro, including auto-join, single sign-on, directory sync, role-based access control, and security scope.+ - [Plans and fair use](https://docs.costory.io/get-started/plans.md): Costory plans (Starter, Team, Business, Custom), what each includes, how fair use on app usage and AI works, and how spend bands act as a guardrail.+ - [BigQuery jobs](https://docs.costory.io/setup/usage-metrics/bigquery-jobs.md): Beta: attach BigQuery job metadata to GCP cost, reallocate slots to the user who ran each query, and see on-demand and reservation spend in one view.+ - [Identity and Access](https://docs.costory.io/docs/sso-access-control.md): Compare Costory identity and access options across Starter, Team, Business and Custom, including auto-join, single sign-on, directory sync, role-based access control, and security scope.

https://raw.githubusercontent.com/costory-io/costory-finops-mcp-skills/HEAD/AGENTS.md

− - **`powers/costory/`** is the Kiro power. Its single skill (`costory-finops`) is a condensed playbook that points to the MCP `get_skill` ids; it is not served by `get_skill` and is not listed in `skills.json`. When you change tool names, safety rules, or the multi-organization rule in a skill, update `powers/costory/skills/costory-finops/SKILL.md` too, and keep `powers/costory/plugin.json` `version` in step with the other manifests.+ - **`powers/costory/`** is the Kiro power. Its single skill (`costory-finops`) is a condensed skill that points to the MCP `get_skill` ids; it is not served by `get_skill` and is not listed in `skills.json`. When you change tool names, safety rules, or the multi-organization rule in a skill, update `powers/costory/skills/costory-finops/SKILL.md` too, and keep `powers/costory/plugin.json` `version` in step with the other manifests.

description

FinOps agent MCP: allocated AWS, GCP, Azure, Kubernetes, SaaS & AI cost for Claude or any agent → FinOps agent MCP: one allocated view of cloud, AI and data costs for your team. Starter $300/mo

version

1.0.1 → 1.0.2

https://docs.costory.io/llms.txt

− - [Create a metrics datasource](https://docs.costory.io/api-reference/admin-metrics-datasources/create-a-metrics-datasource.md)− - [Validate metrics datasource configuration](https://docs.costory.io/api-reference/admin-metrics-datasources/validate-metrics-datasource-configuration.md)− - [Get a metrics datasource](https://docs.costory.io/api-reference/admin-metrics-datasources/get-a-metrics-datasource.md)− - [Archive a metrics datasource](https://docs.costory.io/api-reference/admin-metrics-datasources/archive-a-metrics-datasource.md)− - [Update an AWS S3 v2 metrics datasource definition](https://docs.costory.io/api-reference/admin-metrics-datasources/update-an-aws-s3-v2-metrics-datasource-definition.md)− - [openapi](/api-reference/openapi.json)+ - [Enrichments](https://docs.costory.io/features/tagging/enrichments.md): Beta lookup files that fill business columns from a billing column. Publish static values or a dynamic split from a BigQuery usage table.+ - [Enrichments API](https://docs.costory.io/api-reference/enrichments/overview.md): Upload, test, and publish Costory enrichment lookup files over HTTP. Store drafts, publish the set in one call, and trace a billed row before the next billing update.+ - [List live enrichments](https://docs.costory.io/api-reference/enrichments/list-live-enrichments.md): Live enrichment documents as summaries, sorted by priority then name. `entries` and `conditions` are omitted; read one document with `GET /enrichments/{name}`. Any member.+ - [Get one live enrichment document](https://docs.costory.io/api-reference/enrichments/get-an-enrichment.md): One live document in the JSON form of the YAML file. A response saved unmodified is a valid `PUT` body. `conditions` is the stored CEL and is omitted when unset. Any member.+ - [Store an enrichment document as a draft](https://docs.costory.io/api-reference/enrichments/store-an-enrichment-draft.md): Stores the document as a draft. Publish makes it live. A body equal to the live document drops its draft and returns `unchanged`.+ - [Draft the removal of an enrichment](https://docs.costory.io/api-reference/enrichments/draft-an-enrichment-removal.md): Drafts the removal of a live document, or drops the draft of a document that is not live yet. `404` when there is neither. Org admin only.+ - [Get pending enrichment drafts](https://docs.costory.io/api-reference/enrichments/get-enrichment-drafts.md): The live set with every draft applied. The body is `null` when there is nothing to publish. `errors` is empty when the pending set compiles. Org admin only.+ - [Discard pending enrichment drafts](https://docs.costory.io/api-reference/enrichments/discard-enrichment-drafts.md): Deletes every pending enrichment draft. Org admin only.+ - [Publish pending enrichment drafts](https://docs.costory.io/api-reference/enrichments/publish-enrichment-drafts.md): Compiles the live set with every draft applied and, when it compiles, stores that set in one transaction and starts the update workflow.+ - [List columns needed to trace a row](https://docs.costory.io/api-reference/enrichments/list-enrichment-trace-inputs.md): Billing columns to fill in order to trace one row, with the entry keys the mappings list. `draft` is null when there are no drafts. Org admin only.+ - [Trace one row through the enrichments](https://docs.costory.io/api-reference/enrichments/trace-an-enrichment-row.md): Runs one billed row through the live set with the drafts applied. `published` is the same trace on the live set alone and is present when drafts exist. Org admin only.+ - [Duplicate a cost alert](https://docs.costory.io/api-reference/alerts-v2/duplicate-a-cost-alert.md)+ - [Bulk update cost alert metadata](https://docs.costory.io/api-reference/alerts-v2/bulk-update-cost-alert-metadata.md): Metadata-only patch of visibility, owner, team, and tags for cost alerts. Any id missing or not editable returns 403 for the whole batch.+ - [Bulk archive cost alerts](https://docs.costory.io/api-reference/alerts-v2/bulk-archive-cost-alerts.md)+ - [Bulk restore cost alerts](https://docs.costory.io/api-reference/alerts-v2/bulk-restore-cost-alerts.md)+ - [Update cost alert metadata](https://docs.costory.io/api-reference/alerts-v2/update-cost-alert-metadata.md): Metadata-only patch (visibility, owner, team, tags). Does not rewrite thresholds or condition.+ - [Restrict label dimensions to org admins](https://docs.costory.io/api-reference/dimensions/restrict-label-dimensions-to-org-admins.md): Sets whether only org admins can add, edit, delete, and publish label dimensions. Virtual dimensions stay open to every member. Org admin only.+ - [List live enrichments](https://docs.costory.io/api-reference/enrichments/list-live-enrichments.md): Live enrichment documents as summaries, sorted by priority then name. `entries` and `conditions` are omitted; read one document with `GET /enrichments/{name}`. Any member.+ - [Get pending enrichment drafts](https://docs.costory.io/api-reference/enrichments/get-pending-enrichment-drafts.md): The live set with every draft applied. The body is `null` when there is nothing to publish. `errors` is empty when the pending set compiles. Org admin only.+ - [Discard pending enrichment drafts](https://docs.costory.io/api-reference/enrichments/discard-pending-enrichment-drafts.md): Deletes every pending enrichment draft. Org admin only.+ - [Publish pending enrichment drafts](https://docs.costory.io/api-reference/enrichments/publish-pending-enrichment-drafts.md): Compiles the live set with every draft applied and, when it compiles, stores that set in one transaction and starts the update workflow.+ - [List columns needed to trace a row](https://docs.costory.io/api-reference/enrichments/list-columns-needed-to-trace-a-row.md): Billing columns to fill in order to trace one row, with the entry keys the mappings list. `draft` is null when there are no drafts. Org admin only.+ - [Trace one row through the enrichments](https://docs.costory.io/api-reference/enrichments/trace-one-row-through-the-enrichments.md): Runs one billed row through the live set with the drafts applied. `published` is the same trace on the live set alone and is present when drafts exist. Org admin only.+ - [Get one live enrichment document](https://docs.costory.io/api-reference/enrichments/get-one-live-enrichment-document.md): One live document in the JSON form of the YAML file. A response saved unmodified is a valid `PUT` body. `conditions` is the stored CEL and is omitted when unset. Any member.+ - [Store an enrichment document as a draft](https://docs.costory.io/api-reference/enrichments/store-an-enrichment-document-as-a-draft.md): Stores the document as a draft. Publish makes it live. A body equal to the live document drops its draft and returns `unchanged`.+ - [Draft the removal of an enrichment](https://docs.costory.io/api-reference/enrichments/draft-the-removal-of-an-enrichment.md): Drafts the removal of a live document, or drops the draft of a document that is not live yet. `404` when there is neither. Org admin only.+ - [List dashboards](https://docs.costory.io/api-reference/dashboards/list-dashboards.md): Returns dashboards visible to the caller, newest updated first. Optional `search` filters by name (case-insensitive contains).+ - [List recently updated dashboards](https://docs.costory.io/api-reference/dashboards/list-recently-updated-dashboards.md)+ - [List popular dashboards by view count](https://docs.costory.io/api-reference/dashboards/list-popular-dashboards-by-view-count.md)+ - [Get a dashboard](https://docs.costory.io/api-reference/dashboards/get-a-dashboard.md): Returns the full dashboard including widgets. Increments the caller's view stats (except for templates) and emits opened analytics.+ - [List saved dashboard versions](https://docs.costory.io/api-reference/dashboards/list-saved-dashboard-versions.md): Newest first. Requires the same read access as GET dashboard (Share Reader or Editor). Each row includes optional `name` (null when untitled). The first row is the current version.+ - [Get a dashboard version hydrate payload](https://docs.costory.io/api-reference/dashboards/get-a-dashboard-version-hydrate-payload.md): Version createdAt + context + widgets only (no shell identity). Requires the same read access as GET dashboard. Unknown or foreign version ids return 404.+ - [Rename a saved dashboard version](https://docs.costory.io/api-reference/dashboards/rename-a-saved-dashboard-version.md): Updates only `name` on that version row (empty string becomes null). Max 80 characters. Does not insert a new version. The current version may be renamed. Unknown or foreign version ids return 404.+ - [Copy an old dashboard version into a new dashboard](https://docs.costory.io/api-reference/dashboards/copy-an-old-dashboard-version-into-a-new-dashboard.md): Creates a private copy owned by the caller from that saved version. Requires the same read access as Duplicate.+ - [Create a dashboard](https://docs.costory.io/api-reference/dashboards/create-a-dashboard.md): Creates a DashboardV2 from a bulk-save payload (metadata + widgets with explicit grid positions). Team/scope assignment is validated against membership.+ - [Publish a dashboard](https://docs.costory.io/api-reference/dashboards/publish-a-dashboard.md): Inserts a new saved version (context + widgets) and updates shell metadata. Prefer metadata-only PATCH when widgets are unchanged.+ - [Delete a dashboard](https://docs.costory.io/api-reference/dashboards/delete-a-dashboard.md)+ - [Update dashboard metadata](https://docs.costory.io/api-reference/dashboards/update-dashboard-metadata.md): Metadata-only patch (name, visibility, team, scope, tags, context). Does not rewrite widgets.+ - [Bulk update dashboard metadata](https://docs.costory.io/api-reference/dashboards/bulk-update-dashboard-metadata.md)+ - [Bulk delete dashboards](https://docs.costory.io/api-reference/dashboards/bulk-delete-dashboards.md)

https://raw.githubusercontent.com/costory-io/costory-finops-mcp-skills/HEAD/AGENTS.md

− - **No top-level `skills/` directory.** Every skill lives under `plugins/costory/skills/`.+ powers/costory/                            ← Kiro power (Agent Plugins format: plugin.json + mcp.json + skills/costory-finops/)+ - **No top-level `skills/` directory.** Every plugin skill lives under `plugins/costory/skills/` (the Kiro power keeps its own under `powers/costory/skills/`).+ - **`powers/costory/`** is the Kiro power. Its single skill (`costory-finops`) is a condensed playbook that points to the MCP `get_skill` ids; it is not served by `get_skill` and is not listed in `skills.json`. When you change tool names, safety rules, or the multi-organization rule in a skill, update `powers/costory/skills/costory-finops/SKILL.md` too, and keep `powers/costory/plugin.json` `version` in step with the other manifests.

description

FinOps MCP: query allocated, correlated cloud and AI cost across AWS, GCP, Azure and Snowflake. → FinOps agent MCP: allocated AWS, GCP, Azure, Kubernetes, SaaS & AI cost for Claude or any agent

icon_url

https://framerusercontent.com/images/VCSgoWz73lYAwZVdz7BaJb5Zxk.png → https://raw.githubusercontent.com/costory-io/costory-finops-mcp-skills/main/plugins/costory/assets/logo.png

version

1.0.0 → 1.0.1