
Wealthapi
eu.wealthapiPublished by wealthapi.euv0.1.0Updated Oct 24, 2026
Read-only MCP server for wealthAPI: portfolio, cash-flow, and dividend insights for AI assistants.
Overview
Lets an assistant answer read-only questions about a wealthAPI account: accounts, cash flow, portfolio performance, dividends and market data.
- What you can do
- A local stdio server that wraps the wealthAPI REST API in read-only tools. It covers accounts and balances, transactions and recurring payments, cash-flow summaries and savings rate, portfolio valuation, allocation, performance, risk metrics and realized gains, dividend history, calendar and yield, plus symbol search, quotes and fundamentals. It also registers guided prompts such as monthly review, savings-rate check and subscription audit.
- When to use it
- Use it when you want an assistant to answer everyday personal-finance questions about your own wealthAPI account, such as spending, portfolio performance, biggest positions, dividend income or diversification, without exporting data by hand.
- Requirements
- Runs locally as a Node.js process (Node 20+ and pnpm to build from source) and is configured in a desktop MCP client such as Claude Desktop. Requires a personal wealthAPI API token supplied in the BEARER_TOKEN environment variable, with read scopes for accounts, investments, transactions and profile. Network access to the wealthAPI API is needed.
Installation
In SourceWeft
- Open Wealthapi in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
wealthapi-mcp
A small Model Context Protocol (MCP) server that lets Claude (or any MCP-compatible assistant) answer everyday portfolio questions about your wealthAPI account:
"What did I spend the most money on last month?" "How is my portfolio performing this year?" "Show me my five biggest positions." "Which of my investments lost the most value?"
It runs locally on your machine. Your bearer token never leaves your computer.
What is an MCP server?
MCP is an open protocol that lets an AI assistant call tools you control. The assistant
runs in one process (e.g. Claude Desktop); the MCP server runs as a separate process you
launch. They talk to each other over stdio using JSON-RPC: the assistant writes a
tools/call message to the server's stdin, the server runs the tool and writes the
result back to its stdout. That's the whole protocol.
Note the distinction: this is an MCP server, not an MCP plugin. There is no such thing as an MCP plugin — plugins (e.g. Claude Code plugins) extend the assistant itself, while an MCP server is a standalone process the assistant connects to over the protocol. Any MCP-compatible client (Claude Desktop, Claude Code, others) can use this server.
Concretely, this repo is a Node script. When Claude Desktop starts it, the script registers its tools, waits for tool calls, and when one arrives, makes an HTTPS request to the wealthAPI REST API on your behalf and returns a text summary. No state, no database, no server to maintain.
Read more at https://modelcontextprotocol.io.
The tools
Auth is a wealthAPI API token (wapi_key_…) carrying the read scopes (accounts:read,
investments:read, transactions:read, profile:read). All tools are read-only.
Accounts & cash flow
Portfolio & performance
Dividends
Market data & profile
The server also registers prompts (monthly_review, savings_rate_check,
subscription_audit, fixed_costs_summary, financial_health_check) that chain these
tools into guided analyses.
Tool registration is gated by SUPPORTED_TOOLS/SUPPORTED_PROMPTS in src/index.ts —
remove a name there to disable it without deleting code.
Install
You need Node 20+ and pnpm.
Get a personal bearer token from wealthAPI (your account → API settings).
Add the server to Claude Desktop's config
(~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Restart Claude Desktop. The active tools will appear in the tools panel of any chat, and you can ask portfolio questions in plain English.
How to add a new tool
The canonical example lives in src/tools/accounts.ts — list_accounts is ~50 lines
and shows the whole pattern.
- Create or open the relevant file under
src/tools/and write aregister*Tools(server, client)function that callsserver.registerTool(...). Each call takes a name, a{ description, inputSchema }object (Zod for the input schema), and an async handler that returns{ content: [{ type: "text", text }] }. - Import and call your
register*Toolsfromsrc/index.ts. pnpm buildand restart Claude Desktop.
That's it. No code generation, no registration files, no boilerplate.
Layout
Run tests
Source: README.md at commit d3596ef
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts