Gvnr
Cap per-agent LLM spend and enforce rate limits on every agent call before bills spiral in production.
Overview
Gvnr is a MCP server for the Operate phase that enforces per-agent spend caps and rate limits before each AI API call.
What is this MCP server?
- Per-agent spend caps evaluated before each AI API call
- Rate limiting and idempotency hooks for agent workflows
- Approval workflows and x402-style payment paths in the Gvnr stack
- Remote streamable-http MCP at gvnr.dev with Bearer API key auth
- Published agent-skills index and MCP manifest on gvnr.dev (MIT)
- Registry server version 1.8.1
- Remote endpoint https://gvnr.dev/mcp (streamable-http)
- MIT license; pricing page at gvnr.dev#pricing
What problem does it solve?
Autonomous agents can burn through LLM credits in minutes when there is no per-agent budget or throttle before each request.
Who is it for?
Solo builders shipping agent workflows that call paid models and need caps, throttles, or approvals before money leaves the account.
Skip if: Teams that only use a local model with no metered API, or anyone who wants codegen skills instead of spend governance.
What do I get? / Deliverables
After connecting Gvnr, agents hit enforced spend and rate policies at call time so you can run them in production without surprise invoices.
- Per-agent spend and rate policy enforced on MCP-mediated calls
- Centralized agent infrastructure manifest linked from gvnr.dev
- Optional approval and payment workflow hooks per Gvnr categories
Recommended MCP Servers
Journey fit
How it compares
MCP spend-governance layer, not an agent coding skill or a raw LLM proxy.
Common Questions / FAQ
Who is dev.gvnr/gvnr for?
It is for indie builders and small teams running MCP-connected agents against billed LLM APIs who need per-agent budgets and rate limits.
When should I use dev.gvnr/gvnr?
Use it when agents are live or semi-autonomous and you want spend checks and throttles applied before every provider call, not after the monthly bill.
How do I add dev.gvnr/gvnr to my agent?
Create an account via POST https://gvnr.dev/v1/account, then add the remote MCP URL https://gvnr.dev/mcp with Authorization Bearer your API key in Claude Code, Cursor, or another streamable-http MCP client.