finops-mcp 0.8.6

Ask Claude about your AWS, Azure, GCP, and SaaS costs. MCP server with anomaly detection, rightsizing, and Jira ticketing.

nable — Ask your AI about cloud costs

Connect Claude (or any MCP client) to your real AWS, Azure, GCP, and SaaS billing data.

nable is an MCP server. Install it once and ask Claude about your cloud spend in plain English — no dashboards, no SQL, no BI tool.

"What drove our AWS costs up 40% this month?"
"Which team is spending the most on Datadog?"
"Show me rightsizing opportunities for EC2."
"Create a Jira ticket for any anomalies over $500."

No dashboards. No SQL. Just ask.

---

Quick start

pip install finops-mcp
finops setup

finops setup connects your providers and auto-configures Claude Desktop. Restart Claude Desktop and ask: "What are my AWS costs this month?"

On Anaconda? Anaconda's pip can't install finops-mcp. Use uvx instead — it's isolated and doesn't touch your Anaconda environment:

brew install uv        # or: curl -LsSf https://astral.sh/uv/install.sh | sh
uvx finops-mcp setup

finops setup detects Claude Desktop and writes claude_desktop_config.json automatically. It picks uvx if available, otherwise uses the absolute binary path. Restart Claude Desktop and ask: "What are my AWS costs this month?"

1-month free trial, all features unlocked. No credit card required.

---

Manual Claude Desktop config

If finops setup doesn't auto-configure, run:

finops setup claude

Or add manually to claude_desktop_config.json:

With uvx (recommended):

{
  "mcpServers": {
    "finops": { "command": "uvx", "args": ["finops-mcp"] }
  }
}

With absolute path:

{
  "mcpServers": {
    "finops": { "command": "/usr/local/bin/finops-mcp" }
  }
}

Use the path from which finops-mcp.

Config file locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Why uvx? Claude Desktop is a GUI app and doesn't inherit your shell's PATH. uvx sidesteps this by running finops-mcp in its own isolated environment. It's the most reliable option on corporate machines with managed Python installs.

---

Troubleshooting

finops-doctor          # checks credentials, DB, network, audit log
finops setup claude    # re-run Claude Desktop configuration only

Symptom	Fix
Tools don't appear in Claude	Switch to uvx config or use absolute path
command not found: finops-mcp	Re-install with pip install finops-mcp or use uvx
Python 3.8/3.9 errors	nable requires Python 3.10+: python3.10 -m pip install finops-mcp
Corporate SSL errors	pip install --trusted-host pypi.org --trusted-host files.pythonhosted.org finops-mcp
Permission denied	Install to user: pip install --user finops-mcp or use uvx
Works at home, not at work	Use uvx — corporate IT often strips custom PATH entries

---

Connectors

Provider	What it pulls
AWS	Cost Explorer: real spend, savings plans, reservations
Azure	Cost Management API
GCP	Cloud Billing API + BigQuery export
Datadog	Usage Metering API v2: real dollar amounts
Snowflake	ACCOUNT_USAGE.METERING_HISTORY
Langfuse	Daily metrics API: model cost, token usage, trace volume
MongoDB Atlas	Invoice API
Twilio	Usage Records API
Cloudflare	Billing API
GitHub	Actions minutes + Copilot seats
Vercel	Invoice API (Enterprise)
PagerDuty	Seat count
New Relic	Data ingest + user counts

---

What nable actually does

nable is not just a connector that pipes billing data into Claude. It runs active analysis on your infrastructure and surfaces findings as tools Claude can reason about and act on.

AWS deep audit goes well beyond Cost Explorer. It pulls CloudWatch metrics for every running resource and flags waste that never shows up on your bill until it's too late: gp2 volumes that should be gp3 (20% cheaper, same performance), unattached EBS volumes, idle NAT Gateways costing $32/mo in base charges, RDS backup retention set way too high, CloudWatch Log Groups with no retention policy growing forever, and Lambda functions allocated 2x the memory they actually use. Think of it as Compute Optimizer plus the layer underneath it.

Anomaly detection uses z-score, CUSUM drift, and day-of-week seasonal normalization. When something spikes, it drills into Cost Explorer by tag and tells you which team, environment, or service drove it.

Rightsizing combines AWS Compute Optimizer with nable's own CloudWatch analysis. It gives you specific recommended instance types with estimated savings, not just a list of underutilized resources.

Commitment analysis (Team plan) models Savings Plans and Reserved Instance coverage against your actual usage. It shows your current effective discount rate, coverage gaps, and what you would save by purchasing additional commitments.

---

Team plan features

• Anomaly alerts via Slack or Teams
• Cost attribution by team, service, or tag
• Auto-ticketing: creates Jira, Linear, or GitHub issues for anomalies and waste findings
• Scheduled email reports
• Commitment purchase recommendations with ROI projections
• Org-wide multi-account cost rollup
• Invoice email parsing via IMAP for vendors without APIs

$39.99/mo, 1-month free trial. Subscribe at nable.sh.

---

Security

Credentials are encrypted with Fernet and stored in your OS keyring (macOS Keychain, Windows Credential Manager, or libsecret on Linux). They never leave your machine. nable never writes to your AWS account unless you explicitly enable cleanup mode.

Run finops setup aws --iam-template to generate a least-privilege IAM policy with exactly the permissions nable needs.

---

Docs

Full setup guide: nable.sh/docs