Connect Banks MCP

Give compatible agents secure, read-only access to the financial products you choose. Banks MCP uses the standard Streamable HTTP transport.

Server URL

Use this exact URL, including /mcp, in any client that supports remote MCP servers.

Streamable HTTP endpoint

http://127.0.0.1:8765/mcp

Choose your client

Add Banks MCP once, then continue in your agent to finish the connection.

Terminal command

codex mcp add banks --url http://127.0.0.1:8765/mcp

Start a new Codex session after adding the server.

What happens next

The local server uses the products enabled in this dashboard.

Add the server

Your client discovers the tools available at the URL above.

Connect on this computer

Local connections do not require a separate OAuth sign-in. Keep Banks MCP running while your agent uses it.

Control MCP visibility

Only products enabled for MCP access in this dashboard are exposed.

Try it

Copy an example after your client shows Banks MCP as connected.

“Summarize my assets and liabilities by currency.”
“Show my recent transactions across all shared accounts.”
“How much did I spend in the last 30 days, grouped by account?”

Available tools

Every current tool is read-only, non-destructive, and idempotent.

List bank connections

See which banks this device can access.

List bank products

Inspect accounts, cards, and masked identifiers.

Get balance summary

Summarize assets and liabilities by currency.

List transactions

Read bounded history for a connected account.

Get recent activity

Review recent activity across bank products.

Access and privacy

The MCP boundary is deliberately read-only and product-scoped.

Loopback only

The server binds to 127.0.0.1 and validates browser origins and host headers.

Credentials stay private

Bank credentials are encrypted at rest and are never returned by an MCP tool or shared with your agent.

Read-only tools

Agents can read balances and activity, but cannot move money, change bank settings, or reveal saved credentials.

Troubleshooting

Most connection issues come from an incorrect endpoint or an incomplete authorization.

The client cannot connect

Confirm the configured URL exactly matches the endpoint above and includes /mcp, then confirm Banks MCP is still running.

A product is missing

Enable that product for MCP access on its bank connection.