AI Tools
The GASP Standard ships as an MCP server — so your AI tools speak the same metrics language your team does. Whether you're a data engineer building pipelines, an analyst setting up dashboards, or a team lead standardizing your metrics layer, the MCP gives you definitions, formulas, data schemas, and SQL on demand.
Quick Start
Install the MCP server with a single command:
Claude Code
claude mcp add gasp-standard -- npx -y gasp-standard-mcp Claude Desktop / Cursor
Add to your MCP config file:
{
"mcpServers": {
"gasp-standard": {
"command": "npx",
"args": ["-y", "gasp-standard-mcp"]
}
}
} Restart your MCP client after adding the config.
Claude Code Slash Command
The /gasp command turns Claude into a GASP Standard expert. Ask any question about SaaS metrics and get precise answers sourced directly from the canonical standard files.
What it does
- Look up any of the nearly 300 metric definitions across 13 departments
- Return exact formulas, benchmark ranges, and measurement periods
- Explain metric relationships (what drives what)
- Clarify terminology from the canonical definitions glossary
- Cross-reference metrics across departments
Example usage
> /gasp How do I calculate CAC Payback?
> /gasp What drives ARR?
> /gasp Compare logo churn vs revenue churn
> /gasp What data do I need to implement pipeline tracking?
> /gasp Show me the SQL for calculating NRR
MCP Server
A Model Context Protocol server exposing the entire standard as structured tools. Any MCP-compatible client (Claude Code, Claude Desktop, or custom integrations) can query metrics, formulas, relationships, and definitions programmatically.
Tools
lookup_metric name: string Full metric details: definition, formula, benchmarks, common mistakes, sources, and department.
list_metrics department?: string List all metrics grouped by category, optionally filtered by department.
get_formula metric: string Returns the formula(s) for a metric, including all variants when multiple exist.
get_relationships metric: string Upstream (what drives it) and downstream (what it drives) connections from the GASP relationship graph.
get_data_requirements metric?: string, department?: string Data requirements for implementing a metric or department dashboard: required fields with types, reporting grain, source system, and example SQL query.
search query: string Full-text search across all metric names, definitions, formulas, data requirements, and glossary terms.
Use Cases
Use get_data_requirements to get the exact field schema, types, grain, and starter SQL for any metric or department.
Use get_formula and lookup_metric to get the canonical formula, benchmark ranges, and common calculation mistakes to avoid.
Use list_metrics to see every metric for a department, then get_data_requirements to plan the implementation.
Example Output
Here's what get_data_requirements returns for NRR:
| Field | Type |
|---|---|
| account_id | string |
| mrr_start | decimal |
| mrr_end | decimal |
| expansion | decimal |
| contraction | decimal |
| churn | decimal |
SELECT
cohort_month,
SUM(mrr_end) / SUM(mrr_start) AS nrr
FROM account_cohorts
GROUP BY 1 Data at a glance
GASP Standard v1 · Last updated