## Wallet by BudgetBakers integration

Wallet by BudgetBakers is a personal finance app for tracking accounts, transactions, and budgets.

Agen.co connects to Wallet through Wallet's own hosted MCP server as an **Official** connector. Each user authorizes with their own Wallet account, and agents can read, and optionally change, that user's own financial data.

Prerequisites
- A Wallet by BudgetBakers account. No app needs to be registered with Wallet — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy.


### Connect Wallet in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the **Select connector** drawer, search for `Wallet` and select **Wallet by BudgetBakers**. The **Add Wallet by BudgetBakers** panel opens.
3. Fill in the field:
| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `budgetbakers`. Use lowercase kebab-case. You can change it later from the connector's settings. |
4. Click **Connect**. Wallet opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…**
5. On the **Wallet MCP** sign-in screen, enter the Wallet account's email address, choose how long to grant access for (**7 days**, **30 days**, **90 days**, **180 days**, or **1 year**), and click **Continue**. Complete the sign-in Wallet sends to that address.
6. Back in Agen.co, the panel switches to **Select the tools to import from Wallet by BudgetBakers.** Every tool is toggled on; turn off any you don't want to import, then click **Add**.


The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Wallet tab reported success.

### Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Wallet tool, the call returns an authorization link instead of a result. The user opens the link and signs in the same way, choosing an access duration again. After that, the user's tool calls run with their own Wallet account. Granted access expires after the duration chosen at authorization, and the user has to reauthorize after that; it can also be revoked at any time from **Settings** → **MCP** in Wallet.

Once connected, Wallet appears under **My connectors** with these tools:

| Tool | What it does |
|  --- | --- |
| `get_records` | Reads transactions, for example to export them |
| `create_records` | Adds transactions, accounts, budgets, categories, or labels |
| `patch_records` | Edits records, including bulk recategorization |
| `delete_documents` | Removes records, such as duplicates |
| `create_budget` | Creates a budget |
| `get_budgets` | Reads budget status against spending |
| `create_label` | Creates and applies labels |
| `get_records_aggregation` | Aggregates spending across categories and periods |


Access is read-only by default. Create, update, and delete are opt-in per data type, set at **web.budgetbakers.com/settings/mcp-server** — a tool call for a data type that isn't allowed there fails even if the connector's own policy allows the tool. Wallet limits requests to 300 per hour per account, shared with its REST API.

Enabling the Wallet connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Wallet MCP integration](https://budgetbakers.com/en/products/wallet/integrations/mcp/)