Read-only by design Official Registry · v1.0.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, summarize bounded date ranges, and help you plan—without changing a transaction or moving a cent.

Set up EnvelopeBudget MCP See how it works

Requires an EnvelopeBudget account, a dedicated developer API key, and a client that supports Streamable HTTP with a static Authorization header.

An EnvelopeBudget envelope connected to an AI conversation through a read-only shield

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 v1 keeps every tool on the read side of the line.

1

Create a dedicated key

Generate a developer API key in EnvelopeBudget, give it an expiration date, and keep it separate from your other integrations.

2

Connect your client

Configure https://envelopebudget.com/mcp as a Streamable HTTP server with Authorization: Bearer YOUR_API_KEY.

3

Review, then act yourself

Ask for a spending summary or funding plan. If you want to change the budget, make that change in EnvelopeBudget.

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

What it cannot do

Read-only means read-only

  • Create, edit, merge, archive, or delete transactions
  • Move funds, change envelope targets, or modify accounts
  • Start AI jobs, record consent, or approve or reject suggestions

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 ↗
Open the complete setup guide Manage developer API keys Public docs and issues (opens in a new tab)

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.
  • 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.”