Personal MCP Server

Self-hosted, read-only MCP server that connects your banks and investments via Plaid. Exposed over MCP by the personal mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A self-hosted, read-only MCP server that connects your banks, credit cards, loans, and brokerage accounts (via Plaid) to an MCP client like Claude Code. Ask questions about your own finances in plain English — no third-party aggregator (Monarch, Mint, etc.) involved.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• list_accounts — Every account across every linked bank, with balances
• get_balances — Live current + available balances (optionally filtered by account)
• get_transactions — Transactions in a date range (up to 2 years back)
• search_transactions — Keyword search across merchant / name / counterparty
• get_recurring_transactions — Detected recurring inflow + outflow streams
• get_liabilities — Credit cards, student loans, mortgages with APRs and payment details
• get_investment_holdings — Current holdings with symbol + security metadata
• get_investment_transactions — Buy / sell / dividend history in a date range
• get_institutions_status — Health of each linked bank (surfaces re-auth needs)

Configuration

You will need 2 environment variables: PLAID_CLIENT_ID, PLAID_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Personal.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the personal mcp server does with a few real requests.

When to reach for it

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Personal's toolset — list_accounts, get_balances, get_transactions and 6 more — is a fair guide to whether it matches your workflow. It is maintained by JosueM1109; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.