Context is the MCP server for your memory and money. Connect it to Claude, ChatGPT, Cursor, or any compatible client, then ask your assistant to understand spending, clean up transactions, keep rules current, and remember what you approve.
Server name
Era Context
Transport
Streamable HTTP
Server base URL
https://context.era.app
Explicit MCP path
https://context.era.app/mcp
Authentication
OAuth-protected remote MCP server
Server card
https://era.app/.well-known/mcp/server-card.json
Most finance apps make AI live inside their app. Context does the opposite: it gives the assistant you already use a permissioned, structured way to work with your Era data and the actions you approve.
Add https://context.era.app as a Streamable HTTP MCP server in a compatible client. OAuth handles permission. Start with a read-only question so your assistant can see what your account, plan, and scopes allow.
Use the Era account that has the accounts, memory, and rules you want your assistant to use.
Choose Claude, ChatGPT, Cursor, or another client that supports remote Streamable HTTP servers.
Add https://context.era.app as the MCP server URL.
Review the requested scopes, finish OAuth, and return to your AI client.
Try an overview, account list, or weekly summary before approving write or billing actions.
Era Context uses standard MCP over Streamable HTTP, so it can travel with you across clients that support remote MCP servers. OAuth is the normal path; API keys are there for developer-first tools.
OAuth
https://context.era.app
API key
.mcp.json
OAuth
https://context.era.app
OAuth
~/.cursor/mcp.json
API key
.vscode/mcp.json
OAuth
~/.codeium/windsurf/mcp_config.json
API key
~/.augment/settings.json
OAuth
https://context.era.app
API key
.vscode/mcp.json
Streamable HTTP endpoint
https://context.era.app
Context currently includes 41 tools for memory, accounts, bank connections, transactions, insights, billing, and referrals. Your assistant only sees the tools allowed by your plan, scopes, and client.
Tool list last updated: April 30, 2026
Carry the conversation forward with financial overviews, pending questions, and facts you approve.
knowledge__confirm_or_reject_inference
knowledge__defer_question
knowledge__forget
knowledge__get_financial_context_and_overview
knowledge__get_pending_questions
knowledge__recall_history
knowledge__remember
knowledge__show_question_ui
See balances, account groups, and which accounts count in analysis.
accounts__check_account_balance
accounts__list_financial_accounts
accounts__manage_account_groups
Requires the Organize plan or higher.
accounts__set_account_visibility
Open bank-connection flows and maintain institutions without handing bank credentials to the agent.
connections__connect_bank_account
connections__disconnect_institution
Find messy data, tag it, categorize it, link transfers, and turn repeat fixes into rules.
transactions__list_recurring_charges
transactions__list_spending_categories
transactions__list_transactions
transactions__manage_automation_rules
transactions__manage_categories
transactions__manage_transaction_tags
transactions__manage_transfer_links
transactions__search_transactions
transactions__update_transactions
Answer the questions people actually ask: what changed, where money went, what is recurring, and what might happen next.
insights__analyze_spending
insights__compare_spending_periods
insights__forecast_spending
insights__get_cash_flow
insights__get_daily_financial_summary
Compare plans, preview costs, and make billing changes only after extra consent.
billing__cancel_subscription
billing__confirm_subscription_change
Requires the Organize plan or higher.
billing__get_current_plan
billing__list_plans
billing__manage
Requires the Organize plan or higher.
billing__preview_subscription_change
Requires the Organize plan or higher.
billing__upgrade
Share and track referral links when you ask.
referral__get_dashboard_sso
referral__get_referral_link
referral__get_referral_stats
referral__join_referral_program
Context is strongest when an assistant chains tools: read the picture, make a small approved change, then check its work. It does not move money or run itself on a schedule; connected clients and other servers can extend what happens next.
Load the overview, ask only the missing questions, and save the facts you explicitly want remembered.
Memory should come from explicit approval, not inference.
Find noisy merchants or categories, update the selected transactions, then rerun the analysis to prove the answer changed.
Transaction edits require write scope and selected transaction IDs.
Convert one-time cleanup into tags and automation rules, preview the effect, then verify it with period comparisons.
Rules keep changing future data, so agents should preview and ask before applying them.
Link money moved between your own accounts before forecasting, so cash flow is not inflated by duplicates.
Uncertain transfer matches should be confirmed with you.
Open the bank-connection flow, list the accounts that came back, and hide anything that should not affect analysis.
Disconnecting an institution is destructive and should require clear confirmation.
Review the current plan, compare options, preview exact cost changes, and only then confirm or open checkout.
Billing changes require the separate mcp:billing-write scope.
If your AI client supports routines or scheduled tasks, Context can supply the financial data for Friday briefs, subscription audits, and anomaly reviews.
Context supplies the data; your AI client controls when the routine runs.
Pair Context with email, calendar, Slack, docs, or spreadsheet servers to draft summaries, reminders, and reimbursement packets.
Sending financial summaries to another service requires separate authorization and review.
Only what you authorize. Context sends structured Era data and approved actions; it never gives the assistant your bank login.
Connected accounts, balances, groups, and visibility state.
Transactions, categories, tags, transfer links, recurring charges, and automation rules.
Spending, cash flow, forecasts, comparisons, and daily summaries built from Era data.
Financial memory you approved: goals, preferences, facts, and open questions.
Plan state, prices, previews, checkout, billing portal, and cancellation flows when scopes allow.
Referral links, enrollment, stats, and dashboard access.
Agents do not receive bank credentials.
Available tools can change by plan, approved OAuth scopes, connected accounts, and MCP client.
Context does not move money, pay bills, place trades, file taxes, or act outside the tools listed here.
Context makes agent access explicit: OAuth scopes limit what your assistant can do, safety labels mark sensitive tools, and higher-impact actions need the right permission.
OAuth protects the remote server and shows the scopes being requested.
Your assistant only sees and calls tools allowed by your account, plan, OAuth scopes, and safety rules.
Billing changes are outside the default scopes and require mcp:billing-write.
Destructive tools should be surfaced clearly by the client and confirmed by you.
Plan limits help prevent runaway agent loops.
You can revoke access by disconnecting the MCP client or the underlying account connection.
When a call fails, Context returns structured errors the client can explain.
Good prompts sound like jobs, not API calls. These examples work best when your accounts are connected and your client can combine MCP servers or run routines.
I'm thinking about booking this trip. Check my balances, recurring bills, and month-end forecast. What can I spend without touching my emergency fund?
Find every recurring charge across my accounts, show the monthly total, and make a rule that flags new subscriptions or price increases for my approval.
My coffee transactions are a mess. Clean up this year's purchases, tag them as daily habits, and make a rule so future coffee buys are tagged automatically.
Build me a work-travel reimbursement packet for last quarter. Find matching transactions, tag anything missing, summarize totals by merchant, and draft an email using my email connector.
Every Friday, send me a money brief with cash flow, unusual transactions, upcoming bills, and anything I should review. Use Context for the data and my email or Slack connector for delivery.
No. In a supported client, add the server URL and sign in with OAuth. Developer tools may also support API keys.
No. Context does not expose tools for transfer execution, bill pay, trading, or moving money.
Yes, with permission. Context can update selected transactions, tags, categories, rules, visibility, memory, connections, billing, and referrals within the scopes you approve.
Because Context is permissioned. Your plan, OAuth scopes, client support, and tool safety rules all affect what the assistant can see.
Billing changes require mcp:billing-write, which is not included in the default scopes. Destructive actions should also be confirmed by the client before they run.
Disconnect the MCP client or revoke the underlying account connection, depending on what you want to stop. You can also deny new OAuth authorization requests.
Yes, if your AI client supports routines or scheduled tasks. Context supplies the financial tools; the client controls when the routine runs.
Yes, if your AI client connects those servers too. Context supplies the financial data and actions; email, calendar, document, or spreadsheet servers handle where the result goes.
Usually the assistant is missing a scope, your plan does not include the tool, the request hit a rate limit, or an external service was unavailable.
The tool list comes from Era's live MCP server metadata, so it stays aligned with the tools your assistant can actually discover and call.
Create an Era account, add the MCP server, and ask one read-only question. When you're ready, approve bigger actions one at a time.