What you can actually ask once OpenClaw is connected

Your bank knows everything. The day-to-day cash flow, the recurring subscriptions you forgot about, the times you tapped overdraft, the typical balance going into each month. Until now, your bank's data sat in your bank's app and went nowhere else. Even your AI agent — even one running on your own server — had no idea any of it existed.

Once you connect Truthifi to OpenClaw, that changes. From any OpenClaw channel — web, Discord, Telegram, custom — you can ask:

• "What did I spend at restaurants last month, and how does that compare to the trailing six-month average?"

• "How much have I paid in bank fees this year? Break it down by fee type."

• "What recurring charges hit my Chase account that I might want to review?"

• "Across my Chase and BofA accounts, what's my actual liquid cash right now?"

• "Did any of my deposits this week look unusual compared to my typical pattern?"

• "Find my five largest non-recurring purchases over the last 90 days."

• "What's my month-over-month savings rate based on inflows minus outflows from primary checking?"

• "Which subscriptions am I paying for that I haven't used in three months?" (OpenClaw infers usage from absence of related transactions, not perfectly but useful as a starting point.)

Same conversational interface you already use OpenClaw for. The bank data shows up where you ask the question — your laptop, your Discord with your spouse, your Telegram on a flight.

A worked example. A family runs a shared OpenClaw instance with both spouses authenticated. The Discord channel is where they coordinate household finances. One spouse asks the OpenClaw bot: "How much did we spend on travel-related categories combined last quarter, across both our Chase and BofA accounts?" OpenClaw returns the cross-account figure pulled from Truthifi, with category breakdowns. Both spouses see the answer at the same time. The follow-up "is that on track for our 2026 travel budget?" works the same way — both Truthifi for current spending and OpenClaw's reasoning about target vs actual. The kind of conversation that previously meant exporting two CSVs and reconciling in a spreadsheet now happens inline in chat.

The architecture: why this is different from giving your password to an app

The most common objection to "connect AI to my bank" is the obvious one: I don't trust some random AI tool with my banking credentials. Reasonable. The architecture here is designed around exactly that concern.

Your Chase and Bank of America credentials live at Chase and Bank of America. They never go to Truthifi, they never go to OpenClaw, they never end up on any host you control. The connection works through industry-standard aggregation: your bank shows you a screen that says "Truthifi wants to read your account data," you authenticate at the bank's own portal (not at Truthifi), and the bank issues Truthifi a read-only token. Truthifi can read what the token allows; that's it.

OpenClaw, in turn, talks to Truthifi over an MCP connection. Your OpenClaw host doesn't see your banking credentials. It doesn't even see the Truthifi-to-bank token. It sees a separate Truthifi-issued MCP token that lets it call read-only tools on Truthifi's MCP server.

Two layers of indirection. Your credentials at the bank. Truthifi's token to the bank. OpenClaw's token to Truthifi. Each layer can be revoked independently. Each layer is read-only. Compromise at any single layer doesn't compromise the others.

This is also where the design diverges from naive "Plaid-only" consumer apps. Standalone aggregator apps store your raw data on their servers and expose it back through their own UI. Truthifi inherits the same upstream relationship with your bank that aggregators have — it has to, that's how bank data is accessed in 2026 — but it stops there. The MCP layer means you don't have to use Truthifi's UI; you use OpenClaw's. And the read-only enforcement at the API surface means even if Truthifi were compromised, the worst case is data exposure, not money movement.

For self-hosted OpenClaw users, the architecture is particularly favorable: the OpenClaw host you control sits between Truthifi and the various OpenClaw channels (web, Discord, Telegram). All Truthifi data flows through your infrastructure. Nothing transits a third-party SaaS LLM provider. The privacy posture that motivated self-hosting in the first place is preserved end-to-end for banking questions specifically — meaningful because banking data is among the most sensitive personal data.

What you need

• A self-hosted OpenClaw instance.

• A Truthifi account with Chase and/or Bank of America linked. (New to Truthifi Connect?)

• Either Node.js 20+ for the mcporter skill, or text-editor access to ~/.openclaw/openclaw.json for direct config.

Setup: five steps

Full walkthrough: How to Connect Your Portfolio to OpenClaw via Truthifi MCP. Condensed:

1. Link Chase and BofA to Truthifi. Sign in to truthifi.com → Connections → add each bank. Bank-side OAuth handles authentication; happens once per bank.

2. Add Truthifi to OpenClaw. Path A: mcporter install --target openclaw truthifi. Path B: edit ~/.openclaw/openclaw.json to add Truthifi to mcpServers with type: "http" and url: "https://api.truthifi.com/mcp".

3. Restart the OpenClaw gateway (Path B only; mcporter handles this for you).

4. Authenticate via OAuth on first call. The first banking question to OpenClaw triggers a browser-based OAuth flow with Truthifi.

5. Verify with a prompt like "Show me my balances across Chase and BofA."

If you're running OpenClaw behind a reverse proxy, set MCP_ISSUER_URL to your public HTTPS URL. The setup guide covers why.

Your controls

You stay in control of the connection at every layer:

• Revoke Truthifi's bank read access from your Chase or BofA security/connected-apps settings. Cuts off Truthifi's ability to read that specific bank.

• Revoke OpenClaw's Truthifi access from truthifi.com → Settings → Connected Apps → OpenClaw → Revoke. OpenClaw can no longer call Truthifi.

• Remove the connector from OpenClaw by deleting the truthifi entry in your config or running mcporter uninstall truthifi. OpenClaw stops trying to call Truthifi.

• Read the audit log at truthifi.com to see exactly what OpenClaw queried, when, and from which channel.

• Set per-channel rules in OpenClaw. If you only want Telegram queries to be allowed (and not Discord), OpenClaw's role/permission system lets you restrict which channels can call which MCP servers. Useful for shared family hosts where you want to scope what's queryable from where.

What OpenClaw cannot do — ever

A clear list:

• No transfers, no payments, no Zelle, no money movement of any kind.

• No bill pay setup or modification.

• No account-setting changes (linked email, phone, security questions, 2FA).

• No new account opening.

• No ATM card management.

• No statement-paper-mailing toggles, no overdraft settings, no debit-card limit changes.

• No card-block or card-cancel actions.

OpenClaw with Truthifi reads. It does not write. There is no API path through Truthifi to a transactional endpoint at Chase or BofA. Even a fully compromised OpenClaw host cannot move your money.

Supported institutions

Truthifi's MCP supports the full roster of US banks and credit unions through industry-standard aggregation:

• Chase (consumer + business)

• Bank of America (consumer + business)

• Wells Fargo, Citi, US Bank, PNC, Capital One (and most other top-50 US banks)

• Most credit unions with online banking

• Smaller community banks where the underlying aggregator has coverage

• Online-first banks (Ally, Marcus, SoFi, Discover)

Your OpenClaw will see whatever you've linked in Truthifi. Add a third or fourth bank later — OpenClaw picks it up automatically with no config change.

Disconnecting

Three independent revocation paths, listed in increasing scope:

• Per-bank at the bank: revoke Truthifi's read access at Chase or BofA's connected-apps screen. Cuts off the affected bank only.

• OpenClaw-from-Truthifi: truthifi.com → Connected Apps → OpenClaw → Revoke. Stops OpenClaw from being able to call Truthifi at all (Truthifi's connections to your banks are unaffected).

• Truthifi-from-OpenClaw: remove from mcpServers config or run mcporter uninstall truthifi. OpenClaw forgets Truthifi entirely.

Use whichever scope matches what you're trying to accomplish.