connect

A guided setup command for connecting a cloud account to nable, a local-first tool for tracking infrastructure costs, and checking that the connection works.

In plain words
What is it for?
Use it to connect a provider, check its health, view the last 30 days of spending, identify the most expensive services, compare trends, and inspect AI model costs.
Why use it?
It helps you confirm access and quickly see whether cost data is available without guessing which credentials or setup are missing.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/getnable/finopsmcp/connect
Clone the repo
git clone --depth 1 https://github.com/getnable/finopsmcp
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 482 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00482
Opus 5 $0.00008 $0.00241
Sonnet 5 $0.00003 $0.00096
Haiku 4.5 $0.00002 $0.00048

Measured 2d ago against content hash d6317b5e0ecd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

connect scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

1. Check what nable can already see. Call `list_connected_providers` and `check_connector_health`. AWS often works with zero extra setup because nable uses the machine's existing AWS credential chain (environment variabl
plugins/nable/commands/connect.md · 29 lines

What it actually says

You are helping the user connect nable (their local-first FinOps copilot) and confirm it works, right here inside the editor. Be concise and concrete. No em dashes.

Do these steps in order:

  1. Check what nable can already see. Call list_connected_providers and check_connector_health. AWS often works with zero extra setup because nable uses the machine's existing AWS credential chain (environment variables, ~/.aws/credentials, IAM role, SSO).

  2. If at least one provider is connected and healthy:

    • Call get_cost_summary for the last 30 days. Report the total, the top 3 services, and the trend versus the prior period.
    • Call get_llm_costs (or get_llm_cost_by_model). If there is AI/LLM spend, report it and what share of the total bill it is.
    • Suggest three questions they can ask next, for example: "what drove our bill up last week?", "which EC2 instances should we downsize?", "what is our spend by model?"
    • Stop here. Do not tell them to run any setup. They are already connected.
  3. If nothing is connected (no credentials found):

    • Say in one line that nable reads costs locally with their own credentials and nothing leaves their machine.
    • Tell them to run ONE of these in their terminal, matching their provider:
      • AWS: uvx --from finops-mcp finops setup aws
      • Azure: uvx --from finops-mcp finops setup azure
      • GCP: uvx --from finops-mcp finops setup gcp
    • Mention they can preview on sample data first with uvx --from finops-mcp finops welcome --demo.
    • Tell them to re-run this command to verify once they have finished.
  4. If a provider is configured but unhealthy (auth error or a missing permission), read the health output and give the specific fix, for example the exact IAM permission that is missing, then the command to re-authenticate.

Lead with the cost number whenever you have one. Never invent numbers. Only report what the tools return.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 29 lines · 16 tokens per session scan C d6317b5e0ecd

Subscribe to this mod's changes

connect is a command published in the GitHub repository getnable/finopsmcp (17 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 482 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.