Walletguide

For AI agents

Walletguide for AI agents

Connect the assistant you already use, choose what it may do, and let it set up your wallet with you. It answers your questions with the numbers the app shows, and you approve everything that matters.

Connect an assistantI'm an agent

Connect your assistant in a minute

The Walletguide MCP server lives at mcp.walletguide.com and signs you in through your browser, so your assistant needs nothing more than the address. No API key. Pick yours:

  1. 1

    Open the connector settings in Claude.

    Open Claude connectors
  2. 2

    Click "Add custom connector", name it Walletguide and paste this address:

    https://mcp.walletguide.com
  3. 3

    Click Connect and sign in. The connector works in Claude on the web, in the desktop and mobile apps, and in Code sessions of the desktop app. On a Team or Enterprise plan, an owner may have to add it for the organization first.

Sign in or create your account

When you connect Walletguide, a Walletguide page opens in your browser. Sign in, or create a free account right there and confirm your email address; the connection continues on its own once you have. Then you see which app is asking and choose what it may do:

Read your wallets, transactions and reports
Always included. Your assistant can answer questions about your net worth, spending, assets and plans, with the same numbers the app shows.
Add and change data in your wallets
Lets it do the setup work: add assets and transactions, create and assign categories, merchants and tags, and clean up. Without it the assistant only reads.
Change wallet settings and manage bank connections
Lets it rename a wallet, change its currency or image, hand you links to connect or reconnect a bank, and refresh bank connections. It can also ask you to approve the changes only you may make.
Create wallets for you
Lets it create a wallet with you as the owner, or a sample wallet with example data that is deleted after 14 days. Your first wallet starts your free trial, as it does in the app.

A new account gets every option your assistant asks for ticked; you can untick what you don't want. An existing account starts with reading only. Your assistant sees only the tools of what you allowed, and never more than your own role allows: in a wallet where you are a viewer it changes nothing. To change your answer later, disconnect the app under User settings, Connected apps, and connect again.

Paste this into a new chat

A new chat or session picks up the Walletguide tools you just connected.

I've connected Walletguide. Set it up for me. Instructions for AI agents: https://walletguide.com/agents.md

  • You connect your banks

    Your assistant sends you a link into the app. You sign in with your bank there, through finAPI in Europe or Plaid in the US and Canada; your assistant never sees your bank login. Importing a bank's CSV export stays with you, in the app.

  • Your assistant does the tedious part

    It adds the assets a bank doesn't know about, categorizes transactions, creates merchants and tags, and shows you each change before applying it.

Approve what only you may change

An assistant allowed to change wallet settings can ask for these, and only ask. Each request holds the exact change and comes to you as a link: you open it in Walletguide, signed in, and approve or decline it within an hour. Nothing changes until you approve.

  • Inviting someone to a wallet
  • Changing a member's role or permissions
  • Removing a member
  • Creating an API key, which is shown once, to you and never to the assistant
  • Deleting a wallet, which only its owner can approve, by typing the wallet's name

If you are an agent, start here

Fetch the setup guide as Markdown and follow it step by step. It covers connecting in each client, the sign-in, and every step below. Ask the person before you install anything or change data.

Setup guide

https://walletguide.com/agents.md

MCP server (remote, OAuth)

https://mcp.walletguide.com

Setting a wallet up, in order

  1. 1

    Check the connection

    get_started

    Says how you are connected, which consent options the person did not tick, and which tools each one would add.

  2. 2

    Find or create the wallet

    wallets_listwallets_create

    Confirm with the person which wallet to use. With no wallet yet, ask for its name and the currency to report in, and create it. A sample wallet with example data is deleted after 14 days.

  3. 3

    Connect the banks

    integrations_connect_linkintegrations_sync

    Hand the person a link into the app's bank dialog; they sign in with their bank there, never in the chat. Then refresh connected banks on demand.

  4. 4

    Fill in the rest

    assets_createtransactions_bulk

    Add the assets and transactions no bank knows about. Importing a bank's CSV export stays with the person, in the app.

  5. 5

    Do the setup work

    transactions_bulkEditcategories_createmerchants_create

    Categorize transactions and create missing categories, merchants and tags, after showing the person what you plan to apply.

  6. 6

    Answer with real numbers

    data_netWorthTimeSeriesdata_profitLossdata_batch

    Take every figure from a data tool. They compute over the whole history on the server; adding up transactions yourself gets transfers and pagination wrong.

What the person allows

On the consent screen read access is always granted. Every other option starts ticked for an account created in the last day and unticked for an older one. A connection lists only the tools its grant allows, and every call stays bounded by the person's role in the wallet. A missing tool means an option was not ticked: the person disconnects and connects again with it. A 403 without insufficient_scope means their role does not allow it.

Read your wallets, transactions and reports walletguide:read
Always granted. Every read tool and every report.
Add and change data in your wallets walletguide:write
Creating, changing and deleting assets, transactions, categories, merchants, tags, plans and scenarios.
Change wallet settings and manage bank connections walletguide:admin
Wallet settings, bank connect links and refreshes, and the access requests below. Offered only when the client asks for it.
Create wallets for you walletguide:create_wallets
Creating wallets, sample wallets included, with the person as owner. Offered only when the client asks for it.

What only the person approves

An agent never changes members or API keys and never deletes a wallet. With wallet settings allowed, it can ask: each tool returns an approvalUrl, where the person, signed in, approves or declines the exact change within an hour. access_requests_get tells you how it went; never report a change as done before it reads succeeded.

  • access_requests_invite Invite someone to a wallet
  • access_requests_change_role Change a member's role or permissions
  • access_requests_remove_member Remove a member
  • access_requests_create_api_key Create an API key, whose secret only the person sees
  • access_requests_delete_wallet Delete a wallet, which only its owner can approve

Links the person opens

  • The sign-in and consent page, when the client connects. They can create a free account there.
  • The bank dialog from integrations_connect_link, to connect a bank or reconnect one in error.
  • The approval page of each access request.

Walletguide never moves money, and an agent never sees a bank login or an API key's secret.

Build your own

How we protect your data