Cloud FinOps Skill & MCP
v1.46.0Cloud cost + FinOps knowledge for AI agents: AWS/Azure/GCP optimisation, AI spend, waste playbooks.
Endpoint health
online- Last checked
- 11/20/2026, 4:17:34 AM
- Latency
- 171 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.OptimNow%2Fcloud-finops
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.OptimNow/cloud-finops": {
"url": "https://mcp.optimnow.io/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
7 shown · authentication unknown
Find a waste runbook
find_playbooks
Finds runbooks for a suspected cloud-waste pattern, filterable by provider, service, waste category or detection confidence. Useful when the user asks how to detect or fix a specific waste pattern; each runbook includes a detection query the user can run in their own account. This connector has no access to the user's accounts. Use this with ``query`` for a symptom or a "which of my X" question in the user's own words: "our AWS bill has NAT gateway charges but nothing uses them", "which of my RIs are about to expire", "my NAT gateway processes 10TB to S3", "should I delete these old snapshots", "our Log Analytics ingestion doubled", "which VMs are running for nothing", "passerelle NAT qui ne sert à rien". Every runbook declares the questions it answers (English and French); the result is ranked by those, then by title and service, and carries ``matched_question``; the first entry is the one ``get_playbook(name=)`` fetches. Facets narrow the set first; ``query`` ranks what is left. Use this with the facets alone to browse: "what waste can we clean up safely without review" (confidence), "every idle pattern on Azure" (scope and waste category). Patterns covered include NAT gateways and VPC endpoints, expiring Savings Plans / RIs / reservations, snapshot sprawl, S3 lifecycle gaps, idle or stopped VMs, orphaned disks / public IPs / EBS volumes, GPU and SageMaker sizing, Kubernetes idle capacity, and schedule blindness. All filters are optional and combine with AND semantics. String matching is case-insensitive and exact. Examples: - ``find_playbooks(query="which of my RIs are about to expire")`` - ranked runbooks - ``find_playbooks(scope="aws")`` - all AWS-specific playbooks - ``find_playbooks(waste_category="idle")`` - every idle-resource pattern - ``find_playbooks(scope="cross-cloud", confidence="obvious")`` Args: query: the user's symptom or question in their own words, up to 1,000 characters, English or French. Ranks the facet-filtered runbooks by the questions they declare, their title and their service; returns at most five, best first, each with ``match_score`` and ``matched_question`` (a runbook is read whole, so its ``suggested_section`` is null). scope: ``"aws"``, ``"azure"``, ``"gcp"``, or ``"cross-cloud"``. service: Provider service exact-match (e.g. ``"AWS NAT Gateway"``). waste_category: ``"orphaned"``, ``"idle"``, ``"overprovisioned"``, ``"commitment-mismatch"``, ``"schedule-blindness"``, ``"modernization"``, ``"ai-ml-inefficiency"``, or ``"egress"``. confidence: ``"obvious"`` (single signal is enough), ``"likely"`` (two signals required), or ``"possible"`` (needs human review). From the OptimNow three-tier confidence model in `finops-waste-detection-playbooks`. Returns ``{"filters": {...}, "playbooks": [...], "total": N}``. With ``query`` the entries are ranked and capped at five. A facet filter that matches nothing also returns `hint` and `valid_values`, so a typo is distinguishable from a genuine gap in coverage; a ``query`` that matches nothing returns `hint` alone.
Connections
streamable-http
https://mcp.optimnow.io/mcp