Bring Usage Based Billing
to Cursor
Learn how to connect Orb to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Orb MCP Server?
Connect your Orb account to any AI agent to streamline your revenue operations and usage-based billing workflows through natural language.
What you can do
- Usage Ingestion — Send batches of usage events with idempotency keys to track consumption in real-time.
- Subscription Lifecycle — Create, update, and cancel subscriptions, tying customers to specific billing plans seamlessly.
- Customer Management — Provision new customers and list existing ones with full metadata and external ID mapping.
- Invoicing & Revenue — List historical invoices or fetch upcoming draft invoices to predict end-of-month billing.
- Credit Ledgers — Manage prepaid credits by creating ledger entries for increments, decrements, or expirations.
How it works
- Subscribe to this server
- Enter your Orb API Key
- Start managing your billing and usage data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Finance & RevOps — Instantly check upcoming revenue and manage customer credits without manual dashboard exports.
- Engineering Teams — Debug usage ingestion and verify event delivery directly from the terminal or IDE.
- Product Managers — Monitor feature adoption and subscription statuses across the customer base.
Built-in capabilities (10)
Cancel a subscription
Requires name and email. Create a new customer in Orb
Create a ledger entry for credits
Create a subscription for a customer
Fetch credit ledger for a customer
Fetch upcoming invoice for a subscription
Events require customer_id, event_name, timestamp, idempotency_key, and properties. Ingest usage events into Orb
List customers in Orb
List invoices
Update an existing subscription
Why Cursor?
Cursor's Agent mode turns Orb into an in-editor superpower. Ask Cursor to generate code using live data from Orb and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Orb in Cursor
Orb and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Orb to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Orb in Cursor
The Orb MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Orb for Cursor
Every tool call from Cursor to the Orb MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I report usage events for a specific customer?
Use the ingest_events tool. You'll need to provide an array of event objects containing the customer_id, event_name, timestamp, and an idempotency_key to ensure usage is only counted once.
Can I see how much a customer will be charged before the billing cycle ends?
Yes! The get_upcoming_invoice tool allows you to fetch the draft invoice for any active subscription_id, giving you real-time visibility into accrued costs.
How do I manage prepaid credits or balances?
You can use create_ledger_entry to add or remove credits from a customer's balance. You can also use fetch_ledger to view the current state of a customer's credit ledger.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Langfuse (LLM Tracing & Evals)
10 toolsMonitor LLM apps via Langfuse — track traces, manage prompt templates, and audit evaluation scores.
Paymo
10 toolsControl agency workflows via Paymo — trace tasks, submit time entries, structure project milestones, and securely fetch invoices using AI.
Gobierno Abierto Valencia
5 toolsAccess Valencia's Open Data portal to query datasets, resources, and public records directly from your AI agent.
ClearSale
5 toolsManage e-commerce fraud prevention via ClearSale — submit orders for analysis, monitor fraud scores, and track status updates directly from any AI agent.