Integration

MX integration

MX Financial Data Platform API for modern money experiences. Connect to 16,000+ financial institutions for account aggregation, transaction enrichment, and financial insights. Provides real-time account data, AI-powered transaction categorization, cash flow analysis, and actionable financial recommendations. Built for fintech apps, digital banking, lending platforms, and personal finance management with industry-leading data quality and uptime.

Connect MX How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in MX.Built from the 11 MX tools below, on the connection you add once.

Common MX use cases

user onboarding
KYC verification
ACH transfer setup
displaying transactions
embedded account linking
real-time balance updates
user management dashboards
building category selectors
displaying account dashboard
building institution selectors

What you can do with MX

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Member, 4 operations

aggregate_memberAggregate memberPOSTTriggers a data refresh for an institution connection. Fetches the latest account balances, transactions, and account details from the financial institution.
identify_memberIdentify memberPOSTPerforms account owner identification for an institution connection. Returns account holder PII including name, address, phone, and email when available.
list_membersList membersGETRetrieves all institution connections (members) for an MX user. Members represent linked financial institutions with their connection status.
verify_memberVerify memberPOSTPerforms instant account verification for ACH transfers. Returns verified account numbers and routing numbers directly from the financial institution.

User, 2 operations

create_userCreate userPOSTCreates a new user in MX for financial data aggregation. Users are the foundation for connecting accounts and accessing financial insights.
list_usersList usersGETRetrieves a paginated list of all users in your MX organization. Returns user GUIDs, IDs, and metadata.

Account, 1 operation

list_accountsList accountsGETRetrieves all linked accounts for an MX user. Returns comprehensive account details including balances, account types, and institution information.

Category, 1 operation

list_categoriesList categoriesGETRetrieves MX's transaction category taxonomy. Returns 200+ categories with parent relationships for building category hierarchies.

Connect widget, 1 operation

request_connect_widget_urlRequest connect widget urlPOSTGenerates a URL for MX Connect widget. The widget provides a complete, secure account linking experience without exposing credentials to your app.

Institution, 1 operation

list_institutionsList institutionsGETSearches MX's 16,000+ supported financial institutions. Returns institutions with codes, names, URLs, and supported capabilities.

Transaction, 1 operation

list_transactionsList transactionsGETRetrieves transactions for an MX user with AI-enriched data. Returns transactions with cleaned merchant names, smart categorization, and location details.

MX API rate limits

150 requests per second

GET: 2000 req/sec, POST: 750 req/sec, PUT: 750 req/sec, DELETE: 150 req/sec. Aggregation jobs are throttled per member. IP whitelisting required for production.

These are the limits MX documents, not ones LiveContext measured. They can change and often depend on your plan, so check the MX documentation for current values.

Use MX from Claude Code, Cursor or Codex

Connect MX in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its MX operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect MX

Create your workspace
Sign up free. Nothing to install.
Connect MX once
Add your MX connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

MX integration FAQ

What can you do with the MX integration?

LiveContext exposes 11 operations on MX, covering member, user, account and category. Common uses include user onboarding, KYC verification and ACH transfer setup.

What are the MX API rate limits?

MX documents 150 requests per second. GET: 2000 req/sec, POST: 750 req/sec, PUT: 750 req/sec, DELETE: 150 req/sec. Aggregation jobs are throttled per member. IP whitelisting required for production. Limits are set by MX and can depend on your plan.