Overview
Connect Claude or another agent to Walletguide over MCP at api.walletguide.com/mcp, read-only by default.
MCP is how an agent gets tools. Connect Walletguide and Claude can read your assets, search your transactions and ask for a real net-worth figure, using the same routes the app uses.
There is one server, and it is hosted:
https://api.walletguide.com/mcpConnect a client
One URL, browser sign-in, no local process and no key to store.
The tools
What an agent can call, how tools are named, and which are destructive.
Nothing to install and nothing to keep up to date: the tool catalogue is generated from the same OpenAPI document as the API, so a route added to the app reaches your agent on the next deploy. Sign in through your browser and the grant is revocable from your user settings. If your client cannot open a browser, it can send a wg_ API key as a bearer token to the same URL.
Read-only by default
Sign in through your browser and the consent screen offers write as an unticked box. Leave it unticked and the connection has 46 read tools and no way to change anything.
That is not only caution. The read-only catalogue is less than half the size, roughly 17k tokens against 40k, and that is context the model spends before it has read a single number.
A grant that carries only walletguide:read is never shown a mutating tool. It is not offered one and refused on use; it does not appear.
An API key carries its own permissions instead of scopes. A read-only key, which is what a new key is by default, gets the read-only catalogue; a key that may write anything gets the whole catalogue, and a tool it holds no permission for is refused with 403 when called.
Tools
One per route, named after it. GET /wallets/{walletId}/assets is assets_list, POST /wallets/{walletId}/transactions/search is transactions_search, and the seventeen metric slices are data_netWorthTimeSeries and friends. The endpoint reference describes all of them; a tool takes the same parameters as its route.
Deletes, bulk deletes and merges carry a destructive annotation, so a client that asks before running one will ask.
Getting good answers
Ask a data_* tool for a metric. It computes over the full history on the server and applies the rules raw rows do not carry: splits, transfers between your own accounts, offset categories. An agent that lists transactions and adds them up gets one page of them and no warning. See metrics.
Amounts are decimal strings, and negative means money out. Ids are uuids, so find one with transactions_search or a list tool rather than guessing.