Page 2 of 7 · Server reference
finops-framework-mcp
An agentic interface to the official FinOps Framework (finops.org/framework): 6 Principles, 3 Phases, 4 Domains containing 22 Capabilities, 11 Personas, 5 Technology Categories, Scopes, and an 88-entry KPI library — each Capability carrying a definition, Crawl/Walk/Run maturity assessments, per-persona activities, and featured KPIs.
framework · get_framework_info {}
Data model
The server's own orientation call lays out the hierarchy an agent walks — domains group capabilities, and each capability is the unit that carries KPIs, personas, and maturity guidance:
(Crawl/Walk/Run)
The four domains, per get_framework_info:
Understand Usage & Cost (4 capabilities),
Quantify Business Value (5), Optimize Usage & Cost (5),
Manage the FinOps Practice (8). Phases (Inform/Optimize/Operate) are an
iterative lifecycle, not a partition of capabilities — the server does not offer a phase
filter for that reason.
framework · get_framework_info {} → structuredContent.counts, overview_md
Tool tour
11 tools, grouped by what they're for. Names and parameters below are verified against
the live tools/list response (source: docs/mcp-surface.md,
re-checked against a live probe for this page).
| Tool | Purpose | Key params |
|---|---|---|
| get_framework_info | Orientation: entity counts, data version/crawl date/license, how to navigate. No params. | — |
| list_capabilities | All 22 capabilities (slug, title, domain, summary), optionally filtered. | domain, persona, limit (≤50, default 50), cursor |
| map_personas | Persona↔capability matrix. With persona: capabilities that persona works in, with activity bullets. With capability: personas active in it. With neither: full persona index. | capability, persona |
| Tool | Purpose | Key params |
|---|---|---|
| get_capability | One capability's content, section-selectable to control size (default [summary, definition] ≈1–2k tokens; all sections ≈7k). | capability (required); include: summary|definition|maturity|activities|kpis|headline_groups|inputs_outputs; persona (filters activities) |
| get_kpis | Full KPI records: description, formula + data sources, related capabilities, featured-on list. Single lookup or filtered/paged library browse. | slug, capability, featured_only (default false), limit (≤100, default 25), cursor |
| get_maturity_assessment | Official maturity assessment prose for a capability, verbatim, at one level or all three. | capability (required); level: crawl|walk|run (omit for all three) |
| get_maturity_model | The official Crawl/Walk/Run maturity model itself — capability-agnostic characteristics and sample goals/KPIs per level. No params. | — |
| get_entity | Full markdown for entity types with no dedicated tool. | entity_type (required): principles|phases|domains|technology-categories|scopes|persona; slug (required only for persona) |
| get_changelog | Rolling per-crawl diff summaries of this server's data artifact (crawl-to-crawl, capped at 20 entries). | limit (≤20, default 5) |
| Tool | Purpose | Key params |
|---|---|---|
| search_framework | Ranked keyword search over every entity type. Returns slug + uri per hit — feed slugs into get_capability/get_kpis/etc. | query (required, len ≥2); entity_types (filter); limit (≤50, default 10); cursor |
| Tool | Purpose | Key params |
|---|---|---|
| assess_maturity_path | Official maturity assessment text at each level between a current and target level — evidence to look for when maturing. | capability (required); current_level (required, exclusive); target_level (required, must be above current) |
Prompts & resources
Prompts (4)
| Prompt | Purpose | Arguments |
|---|---|---|
| explain-framework | Guided onboarding tour of the framework, tailored to an audience. | audience (optional) |
| assess-capability-maturity | Structured interview to place an org's maturity for one capability, citing official assessment text as evidence. | capability (required) |
| plan-maturity-roadmap | Ordered plan from a current to a target maturity level, citing official assessment text as evidence. | capability, current, target (all required) |
| map-personas-to-capabilities | Engagement guide: what a persona (or every persona) does across the framework's capabilities. | persona (optional) |
framework · list-prompts (live probe, verbatim descriptions/arguments above)
Resources — finops://framework/…
11 fixed resources plus 4 URI templates (44 concrete resources listed when templates are expanded). Fixed resources are whole small documents; templates are per-entity documents completed via slug (and, for maturity, level).
| URI | What it is | Type |
|---|---|---|
| finops://framework/overview | Start here: what the framework contains, how to navigate | fixed |
| finops://framework/principles | The 6 FinOps Principles | fixed |
| finops://framework/phases | The 3 FinOps Phases (iterative lifecycle) | fixed |
| finops://framework/domains | The 4 Domains with their capabilities | fixed |
| finops://framework/technology-categories | The 5 Technology Categories | fixed |
| finops://framework/maturity-model | Official Crawl/Walk/Run maturity levels | fixed |
| finops://framework/scopes | FinOps Scopes — conceptual guidance | fixed |
| finops://framework/personas | All 11 personas (6 core + 5 allied) | fixed |
| finops://framework/capabilities | All 22 capabilities grouped by domain | fixed |
| finops://framework/meta/manifest | Data manifest (JSON): versions, crawl date, counts, source URLs, attribution | fixed, JSON |
| finops://framework/meta/changelog | Crawl changelog (JSON) | fixed, JSON |
| finops://framework/capabilities/{slug} | Full capability document: definition, maturity, activities, KPIs, inputs/outputs | template, completable |
| finops://framework/personas/{slug} | One persona's goals, objectives, capability involvement | template, completable |
| finops://framework/capabilities/{slug}/maturity/{level} | One capability's official assessment at one level | template, completable |
| finops://framework/kpis/{slug} | Full KPI record | template, completable |
framework · list-resources (11 fixed confirmed live, incl. finops://framework/capabilities/anomaly-management) · docs/mcp-surface.md (template/completion detail)
Pagination & cursors
List/search tools (list_capabilities, get_kpis,
search_framework) return an opaque cursor string alongside
results once more remain; pass it back as the cursor argument to continue.
A live 3-per-page walk of the 22 capabilities:
The three capabilities returned were allocation, anomaly-management, architecting-workload-placement — pagination is stable ordering over the 22-entry list, cursor opaque and version-scoped (embeds the data version, so a re-crawl invalidates stale cursors rather than silently reordering results underneath them).
Official vs. UNOFFICIAL, and provenance
Out of the box, everything this server returns is official restructured FinOps Foundation content — the Framework, KPI library, personas, maturity model, all as published at finops.org/framework. Every tool response carries a provenance footer citing the source URL, CC BY 4.0 license, and the data version/crawl date, e.g.:
What a fresh npx finops-framework-mcp serves — every tool, prompt
and resource on this page — is content from the official framework pages,
restructured and adapted under CC BY 4.0. Nothing this server invented is mixed
in, and the content records that make up an answer carry their own
source_url in structuredContent alongside the footer
above, so any claim can be taken back to the page it came from.
Worked demo: Anomaly Management end to end
The chain an agent walks for one capability: get_capability for what it
is, get_kpis for what to measure, get_maturity_assessment for
how to grow it.
get_capability official
The full definition (trimmed here) situates it: “Anomaly Management gives a FinOps team the ability to detect, identify, clarify, alert on, and manage unexpected cost events in a timely manner […] Effective Allocation metadata are critical to effective anomaly detection […] Use of automated, machine learning–based anomaly detection is typical.” Domain: understand-usage-and-cost.
framework · get_capability {capability: "anomaly-management", include: ["summary","definition"]}
get_kpis, featured only official
Three KPIs are featured on the capability's own page:
Anomaly-Detected Cost Avoidance featured
Anomaly Detection Rate featured
Total Unpredicted Variance of Spend featured
framework · get_kpis {capability: "anomaly-management", featured_only: true} → total: 3
get_maturity_assessment, all three levels official
Crawl: “Manually checking for anomalous spending using reporting […] Reacting to anomaly activity more than a week after it occurs (post receipt of billing data) […] Anomaly alerts sent to a central team, or require manual action to look.”
Walk: “Some form of automated detection or reporting or tooling […] Context-relevant thresholds are detected (percentage of spend change, single item spend amount ceilings, forecast breach alerts, etc.) […] Unexpected spending automatically routed to responsible teams […] KPIs associated with Anomaly Management set and in use by key teams in the organization.”
Run: “Mature Anomaly detection tooling in use and embedded in tooling across the organization […] Automation created to detect, suggest resolution, or resolve anomalous spending alerts […] Analysis results in full root cause analysis post-mortem where appropriate […] Analysis of resolution of past anomalies improves alerting on future anomalies.”
framework · get_maturity_assessment {capability: "anomaly-management", level: "crawl"} · {level: "walk"} · {level: "run"}
What this demo shows
Three tool calls, zero invented data, one
complete practitioner briefing: what Anomaly Management covers, which three KPIs the
Foundation features on its page (with exact formulas), and the verbatim Crawl→Walk→Run
evidence to look for when maturing the practice — the same chain
assess-capability-maturity and plan-maturity-roadmap automate
as prompts.
Next: pair this with FOCUS spec data on finops-focus-mcp, or see both servers combined in the Rate Optimization (ESR) worked example.