Nable (finops Mcp)

Created By
chaandannn11 hours ago
Local-first FinOps copilot: ask about your AWS, Azure, GCP, and SaaS costs in plain English. Anomaly detection, rightsizing, idle-resource cleanup, and Jira/Linear ticketing, all in your own Claude. Credentials never leave your machine.
Overview

nable (finops-mcp)

Local-first FinOps copilot. Ask about your AWS, Azure, GCP, and SaaS costs in plain English, right inside Claude. Anomaly detection, rightsizing, idle-resource cleanup, and Jira/Linear ticketing, all running on your own machine. Credentials and cost data never leave your machine.

Install

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

Or pip install finops-mcp.

Ask it things like

  • "What drove our AWS costs up 40% this month?"
  • "Which team is spending the most on Datadog?"
  • "Show me EC2 rightsizing opportunities."
  • "Find idle resources wasting money in AWS."
  • "Create a Jira ticket for any anomaly over $500."

What it covers

  • Cost queries across AWS, Azure, GCP, and 13+ SaaS providers
  • Anomaly detection with alerting
  • Rightsizing and idle-resource cleanup
  • Cost attribution by team and service
  • Commitment (Savings Plans and Reserved) recommendations
  • Jira, Linear, and GitHub ticketing

Server Config

{
  "mcpServers": {
    "nable": {
      "command": "uvx",
      "args": [
        "finops-mcp"
      ]
    }
  }
}
Project Info
Created At
11 hours ago
Updated At
11 hours ago
Author Name
chaandannn
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago