1
Create a dedicated key
Generate an expiring developer API key. Leave both categorization permissions off for read-only access; enable only the workflow a trusted client needs.
Read-only by default
Official Registry · v1.2.0 (opens in a new tab)
Ask better questions about your budget. Keep the controls.
EnvelopeBudget's remote Model Context Protocol server lets compatible AI assistants review the budgets you authorize and summarize bounded date ranges. Every key starts read-only; separate permissions can allow a trusted agent to resolve suggestions or categorize recently reviewed inbox transactions.
Requires an EnvelopeBudget account, a dedicated developer API key, and a client that supports Streamable HTTP with a static Authorization header.
A safer starting point for financial AI
Useful context, deliberately limited access
MCP gives your assistant structured tools instead of making you export a spreadsheet and explain every column. EnvelopeBudget keeps ordinary keys on the read side of the line and makes categorization permission an explicit choice.
2
Connect your client
Configure https://envelopebudget.com/mcp as a Streamable HTTP server with Authorization: Bearer YOUR_API_KEY.
3
Review—or resolve suggestions
Ask for a spending summary or funding plan. A separately scoped key may resolve selected suggestions or assign recently observed inbox transactions with stale-state protection.
What your assistant can review
The budget context behind the question
- Authorized budgets, accounts, envelopes, balances, and targets
- Bounded transaction searches, including inbox and uncategorized items
- Spending and cashflow summaries for bounded date ranges
- Existing AI categorization disclosure, jobs, and suggestions
- Agent-native inbox categorization without a second AI-provider call
The write boundary
Categorization, not general control
- Create, edit, merge, archive, or delete transactions
- Move funds, change envelope targets, or modify accounts
- Record AI disclosure consent or rewrite transaction amounts, dates, payees, memos, or accounts
Version 1 does not support OAuth. Access uses a static EnvelopeBudget developer API key supplied by you.
Client setup
Use a client that can send a static secret header
Configuration formats change, so start with our setup guide and confirm details against your client's current documentation.
Cursor
Remote server headers with environment interpolation.
Client docs ↗VS Code
HTTP servers with password-style input prompts.
Client docs ↗Claude Desktop
A local bridge for versions that cannot attach a static remote credential.
Bridge docs ↗Hermes Agent
Remote HTTP MCP configuration in config.yaml.
Client docs ↗Privacy and key safety
MCP gives your chosen client and AI provider access to sensitive financial data returned by the tools it calls. Review that provider's data policies before connecting.
- Use a dedicated key with an expiration date and the least permission needed.
- Never paste a key into a prompt, issue, screenshot, or source-controlled file.
- Memo text is omitted unless explicitly requested.
- Membership and role still limit which budgets can be read.
- Rotate or delete the key to disconnect the client.
A few useful first prompts
“List my budgets, then summarize this month's available funds, spending, and cashflow for Household.”
“Show uncategorized transactions in Household from the last 14 days. Do not include memo text.”
“Review the last 90 days of cashflow and suggest a monthly funding plan. Do not change anything.”
“Review my pending categorization suggestions. Approve only the grocery and utility suggestions I name, and leave everything else unchanged.”
“Review these uncategorized inbox transactions, assign the five I confirm to the envelopes we discussed, and leave the rest unchanged.”