Read your Stripe revenue in Cursor
Once your Stripe account is connected in the dashboard, read-only, the agent in your editor can answer money questions without you opening Stripe: what MRR is, who started paying this week, who cancelled, and how collected revenue is trending.
Cursor reads MCP servers from a JSON file, either per user or per project. Remote servers take a url and optional headers.
Setup
You need a secret key (nv_live_…) from Dashboard → API keys.
01Add the server to mcp.json
~/.cursor/mcp.json (or .cursor/mcp.json in a project)
{
"mcpServers": {
"nordva": {
"url": "https://mcp.nordva.dev",
"headers": {
"Authorization": "Bearer nv_live_..."
}
}
}
}Use the file in your home directory if the key should not live in the repository. A project-level .cursor/mcp.json containing a key belongs in .gitignore.
02Check the connection
Open Cursor Settings and find the MCP section. nordva should be listed with its tools and a green status. In Agent mode, ask it to run setup_check.
Then ask Cursor
- What's my MRR, and did it go up this month?
- Who paid in the last week, and did anyone cancel?
- Show revenue for the last 90 days. Which week was best?
- Is my Stripe connection healthy? When did it last sync?
For “How did revenue do over the last 30 days?” Cursor calls get_revenue_summary with:
{
"period_days": 30
} Returned: Per currency: MRR, active and trialing subscriptions, paying customers, new and churned subscriptions with their MRR, net MRR change, collected revenue and payment count, plus the sync status and the time of the last sync.
Revenue tools and arguments
get_stripe_connection_status
Read-onlyCheck whether Stripe is connected and syncing
No arguments.
get_revenue_summary
Read-onlyIndie and BuilderGet MRR, subscriptions, growth and churn from Stripe
| period_days | optional | number, 1–730 | Window in days. Default 30. |
get_revenue_series
Read-onlyIndie and BuilderGet revenue over time from Stripe
| range | optional | "30d" | "90d" | "12m" | "all" | Default "30d". |
list_recent_payments
Read-onlyIndie and BuilderList recent payments and cancellations from Stripe
| type | optional | "payment" | "cancellation" | |
| limit | optional | number, 1–100 |
Behaviour worth knowing
- There is no tool that connects Stripe, and no tool accepts a key. The status tool tells the agent to send you to the dashboard and never to ask for a key in the conversation.
- Launch only reads your Stripe account. The key is a restricted key with read permissions, encrypted at rest, and never appears in a tool result.
- Amounts are in the smallest currency unit, per currency, and are never converted or summed across currencies. The tool descriptions tell the agent the same.
- MRR is operational: yearly divided by twelve, running coupons applied, metered and tiered prices counted as zero, refunds not subtracted.
- Every result carries the sync status. If the first import is still running, or the key was revoked, the agent is told the numbers are incomplete or stale.
- History reaches 90 days on Indie and 24 months on Builder. A longer range is shortened and the result says so.
- Cursor's agent decides when to call a tool from the tool descriptions; naming the tool in the prompt ("use publish_changelog_entry") removes the guesswork.
- Tools that send email or remove content are flagged destructive by the server, and their descriptions tell the agent to confirm with you first.