Skip to main content
Glama
aaronmsoto

finops-framework-mcp

by aaronmsoto

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FINOPS_MCP_DATANoOverride the artifact directory. Defaults to the one packaged with the npm release (`data/framework`); can also be passed as the first CLI argument.data/framework

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_framework_infoA

Start here. Returns the framework's structure (entity counts), the data version/crawl date/license, and how to navigate this server's tools. No parameters.

search_frameworkA

Ranked keyword search over every entity (capabilities, KPIs, personas, principles, phases, domains, technology categories, maturity levels, scopes). Returns slug + uri per hit. Feed the slug to get_kpis(slug: …), or pass it as capability: <slug> to get_capability/get_maturity_assessment/assess_maturity_path/map_personas and as persona: <slug> where a persona filter is accepted. Other entity types (principles, phases, domains, technology categories, scopes) are read via get_entity(entity_type: …) or the hit's finops:// resource uri. Use this whenever you don't already know a slug.

list_capabilitiesA

All 22 capabilities (slug, title, domain, one-line summary), optionally filtered by domain and/or persona (both take a slug, e.g. domain="understand-usage-and-cost", persona="finance"). The framework does not assign capabilities to phases, so there is deliberately no phase filter. Default limit returns the full list in one call.

get_capabilityA

One capability's content, section-selectable via include to control size. Default include is [summary, definition] (~1-2k tokens). Approximate extra cost per section: maturity ~2.5k tokens, activities ~3k (filter with persona), kpis ~1k, headline_groups/inputs_outputs <1k; requesting ALL sections is roughly 7k tokens — prefer the finops://framework/capabilities/{slug} resource for the full document.

get_maturity_assessmentA

The official FinOps Framework maturity assessment prose for a capability, verbatim, at one level (crawl|walk|run) or all three. This is the Foundation's published assessment text, not a parsed breakdown.

get_kpisA

Full KPI records: description, formula + candidate data sources (present for the 44 KPIs the site details in capability-page popups), official related capabilities, and where each is featured. Look up one KPI with slug, or filter by capability and/or featured_only — filters combine (AND), so a slug that doesn't match the capability filter returns zero records. Without filters, pages through the whole 88-entry library.

assess_maturity_pathA

For one capability, the official maturity assessment text at each level between current and target — evidence to look for when maturing. To get one level's assessment text on its own (or all three at once), use get_maturity_assessment instead.

map_personasA

With persona: every capability that persona works in, WITH that persona's activity bullets inline (one call answers 'what does X do across the framework'). With capability: every persona active in it, with activities. With neither: the full persona index (slugs, categories) — use it to discover persona slugs. Passing both is an error — pick one direction per call. Allied personas are mapped at group level by the framework; responses say so explicitly.

get_entityA

Full rendered markdown for entity types that have no dedicated tool. Required param: entity_type (principles | phases | domains | technology-categories | scopes | persona). Collections return whole (they are small); entity_type 'persona' also needs slug. For capabilities use get_capability; for KPIs get_kpis; for maturity levels get_maturity_model.

get_maturity_modelA

The official FinOps maturity model: Crawl/Walk/Run with each level's characteristics and the community's sample goals/KPIs (e.g. allocation coverage targets per level). Capability-agnostic — for one capability's per-level assessment use get_maturity_assessment.

get_changelogA

What changed between data versions of this server's crawled artifact (rolling window of the 20 most recent refreshes — the crawler caps the log at 20, so this tool covers the full retained history; the same data is at finops://framework/meta/changelog). Reflects crawl-to-crawl differences in finops.org content, not a Foundation-published changelog.

Prompts

Interactive templates invoked by user choice

NameDescription
explain-frameworkGuided onboarding tour of the framework, tailored to an audience (e.g. 'engineering leadership', 'new FinOps hire').
assess-capability-maturityStructured interview to place an organization's maturity (crawl/walk/run) for one capability, citing the official assessment text as evidence.
plan-maturity-roadmapOrdered plan to move one capability from a current to a target maturity level, citing the official assessment text as evidence.
map-personas-to-capabilitiesEngagement guide: what a persona (or every persona) does across the framework's capabilities.

Resources

Contextual data attached and managed by the client

NameDescription
overviewStart here: what the framework contains and how to navigate this server.
principlesThe 6 FinOps Principles
phasesThe 3 FinOps Phases (iterative lifecycle)
domainsThe 4 FinOps Domains with their capabilities
technology-categoriesThe 5 Technology Categories (FinOps for Cloud/SaaS/AI/Data Center/Data Cloud)
maturity-modelOfficial Crawl/Walk/Run maturity levels
scopesFinOps Scopes — conceptual guidance document
personas-indexAll 11 personas (6 core + 5 allied)
capabilities-indexAll 22 capabilities grouped by domain
manifestData/schema versions, crawl date, counts, source URLs, attribution.
changelogRolling per-crawl diff summaries (what changed between data versions).
AllocationDefine strategies to assign and share cost and usage using accounts, tags, labels, and other metadata, creating accountability among teams and projects within an organization.
Anomaly ManagementDetect, identify, alert and manage unexpected or unforecasted technology cost and usage irregularities in a timely manner to lower risk and ensure cost-effective operations.
Architecting & Workload PlacementDesigning and modernizing solutions with cost awareness and efficiency to maximize business value, while meeting performance, scalability, and operational objectives. Evaluating an
Automation, Tools, & ServicesDeveloping criteria and methodologies to effectively evaluate and integrate software tools, automation solutions, and professional services aligned with the FinOps Framework Capabi
BudgetingStrategic and ongoing process for setting limits, monitoring, and managing technology spending, aligned with business objectives, to ensure accountability and predictable financial
Data IngestionCollect, transfer, store, and normalize data from various sources, with a goal of creating a complete, contextual dataset of usage and cost data available for analysis.
Executive Strategy AlignmentExecutive Strategy Alignment connects technology-related spend, usage and adoption to the organization's business strategy and priorities, helping leaders compare options, make tra
FinOps AssessmentConducting repeatable, measurable, thoughtful analysis of the maturity of a FinOps Practice in the context of the FinOps Framework for insights into strengths and areas for improve
FinOps Education & EnablementTraining, skill development, and practical activities that enable teams throughout the organization to adopt and deliver the FinOps practice.
FinOps Practice OperationsDriving a culture of accountability by running an effective FinOps team that empowers the FinOps practice through continuous implementation of FinOps strategy and processes.
ForecastingCreating a model of the anticipated future cost and value of IT systems leveraging statistical methods, historical spend patterns, planned changes, and related metrics.
Governance, Policy & RiskEstablishing and evolving policies, controls, and governance mechanisms to ensure that technology use across every FinOps Scope aligns with business objectives, complies with regul
Intersecting DisciplinesCoordinating FinOps activities with other interconnected disciplines or Allied Personas (such as, ITAM, ITFM, Sustainability, Security) that exist in the organization, and which ma
Invoicing & ChargebackDeveloping specific reporting, service provider invoice reconciliation workflows and chargeback models, in direct collaboration with Finance Personas with input from Product and En
KPIs & BenchmarkingUsing KPIs to evaluate optimization, performance, and business value across diverse technology categories (Cloud, SaaS, Data Cloud Platforms, and on-premises environments), all Fin
Licensing & SaaSUnderstanding and optimizing the impact of software licenses and SaaS investments on an organization’s cost structure and value by understanding vendor-specific licensing terms, us
Planning & EstimatingEstimation and exploration of potential cost and value, alongside opportunities for automation, sustainability and optimization, for workloads if implemented in an organization’s t
Rate OptimizationDriving rate efficiency through a combination of strategic vendor use, negotiated discounts, commitment discounts, and other pricing mechanisms to meet the organization’s strategic
Reporting & AnalyticsAnalyze data and create reporting to gain insights into usage patterns and spend patterns, identify opportunities for improvement, and support informed decision-making about techno
SustainabilityIncorporating sustainability criteria and metrics into FinOps activities to ensure environmental efficiency is balanced with financial value, and optimization decisions are aligned
Unit EconomicsDevelop and track metrics that provide an understanding of how an organization’s technology use and technology management practices impact the value of the organization’s products,
Usage OptimizationAnalyze and optimize technology resources to match specific usage patterns while ensuring that workloads operate efficiently and generate sufficient business value for their cost.
Engineering personacore persona
Finance personacore persona
FinOps Practitioner personacore persona
ITAM personaallied persona
ITFM personaallied persona
ITSM / ITIL personaallied persona
Leadership personacore persona
Procurement personacore persona
Product personacore persona
Security personaallied persona
Sustainability personaallied persona

TDQS

A4.3/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target distinct entity types or actions, and descriptions explicitly steer users (e.g., get_maturity_assessment vs assess_maturity_path vs get_maturity_model). The maturity trio has some conceptual overlap, but the prose clarifies when to use each.

Naming Consistency5/5

All names use consistent snake_case with clear verb_noun structure (get_*, list_*, search_*, assess_*, map_*). The pattern is predictable across the entire tool set.

Tool Count5/5

11 tools is well within the ideal 3-15 range for a multi-entity framework browser. Each tool corresponds to a distinct entity type or workflow, with no excessive fragmentation.

Completeness5/5

The surface covers discovery, capabilities, KPIs, personas, maturity assessment/path/model, generic entities (principles, phases, domains, technology categories, scopes), and changelog. This is comprehensive read-only coverage for the FinOps Framework domain.

Maintenance

ActivityActive
ResponsivenessNo issues