Connect Banks MCP

Give compatible agents secure access to the accounts you choose. They can read financial data and organize transaction categories, but cannot move money. 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

https://mcp.corton.ai/mcp

Choose your client

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

1. Open MCP settings

In Codex Desktop, open Settings, select MCP servers, then choose Add server.

2. Add Banks MCP

Name the server Banks MCP, choose Streamable HTTP, and enter https://mcp.corton.ai/mcp

3. Authenticate

Save and restart, select Authenticate, then sign in and choose the accounts Codex may read.

What happens next

Authentication and account access stay under your control.

Add the server

Your client discovers the tools available at the URL above.

Sign in securely

Your browser opens the Banks MCP OAuth flow. Bank credentials are never shared with the client.

Choose what to share

Approve only the accounts, cards, and investments this client should be able to read.

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.”
“Find my uncategorized transactions and help me categorize them.”
“How much did I spend in the last 30 days, grouped by account?”

Available tools

Financial reads are read-only. Category updates are non-destructive, transaction-scoped, and idempotent.

List bank connections

See which banks are connected.

List bank accounts

Inspect accounts, cards, and masked identifiers.

Get balance summary

Summarize assets and liabilities by currency.

List transactions

Read all or only uncategorized history for a shared account.

Get recent activity

Review all or only uncategorized activity across shared accounts.

List transaction categories

See every category an agent may assign.

Edit transaction categories and display names

Categorize one transaction without changing its bank record.

Access and privacy

The MCP boundary is account-scoped and cannot move money or change bank records.

OAuth protected

Each client receives its own authorization and can access only the accounts you approve.

Credentials stay private

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

Limited organization access

Agents can read balances and activity and categorize transactions. They 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.

Sign-in did not finish

Disconnect Banks MCP in your client, add it again, and complete the browser authorization without closing the tab.

An account is missing

Share that account with agents on its bank page, then reconnect the client to update its approved accounts.