One MCP server for your entire financial picture
Stop stitching together exports and one-off integrations. era Context is a remote MCP server that gives any compatible agent — Claude, ChatGPT, Cursor, or the one you're building — clean, structured, permissioned access to real financial data. Add the server URL, approve the OAuth scopes, and start asking.
An open protocol, not a walled garden
era speaks the Model Context Protocol — the same open standard powering agent tools across the industry. One connection, scoped permissions, and tools your agent can read with and act on.
Open protocol, not a proprietary lock-in
Built on the Model Context Protocol (MCP), the open standard for agent connectivity — any compliant client plugs in without custom integration work.
Connected in minutes
Add the server URL as a Streamable HTTP MCP server in your client, approve the OAuth scopes, and ask a read-only question first — that's the whole setup.
Clean, structured data
Accounts, transactions, and balances arrive cleaned and categorised through regulated data aggregators — your agent works with structured data, not statement exports.
Permissioned by design
Every tool call is scoped to what the user has explicitly allowed, protected by bank-level encryption — and access can be revoked at any time.
Memory that travels between agents
Preferences, facts, and context live with the account, not with any single client — every connected agent reads and writes to the same store.
Works with the tools you already use
Claude, ChatGPT, Cursor, VS Code, or a generic Streamable HTTP client — if it speaks MCP, it can connect to era.
Common questions
The Model Context Protocol — an open standard that gives AI agents a structured, permissioned way to use tools and data. era Context implements it as a remote server, so any compliant client can work with your financial data.
Claude, ChatGPT, Cursor, and any client that supports remote MCP servers over Streamable HTTP — including CLI tools and IDEs. If it speaks MCP, it works.
era Context is an OAuth-protected remote MCP server. You sign in with your era account, review the requested scopes, and approve the connection — API keys are available for developer-first tools.
Every tool call is limited to the scopes granted during OAuth, sensitive actions require extra consent, and you can revoke a client's access at any time.
Never. Your data isn't sold, isn't used for ads, and is never used to train models. Every agent action needs your permission first.
Get connected in minutes
One server URL, one OAuth approval, and your agent can see the whole financial picture. The setup guide walks you through it.