MX Technologies for AI agents
MX Technologies aggregates and enriches financial data, connecting apps to bank accounts, transactions, and budgets across thousands of financial institutions. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in MX Technologies.
List a member's accounts
Pull the accounts linked to a member to check current balances, read-only.
Check recent transactions
List a member's recent transactions to categorize spending for a budget view.
Approve before disabling a user account
Require approval before disabling a user account, since it cuts off their linked financial data access.
36 MX Technologies actions, graded by risk.
Every MX Technologies action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
28Look things up. Allowed by default.
- mx_technologies.list_tagsList tags
- mx_technologies.list_goalsList goals
- mx_technologies.list_usersList users
- mx_technologies.list_budgetsList budgets
- mx_technologies.list_membersList members
- mx_technologies.list_rewardsList rewards
- mx_technologies.list_accountsList accounts
- mx_technologies.list_taggingsList taggings
- mx_technologies.list_categoriesList categories
- mx_technologies.list_challengesList challenges
- mx_technologies.list_institutionsList institutions
- mx_technologies.list_transactionsList transactions
- mx_technologies.list_account_ownersList account owners
- mx_technologies.list_member_accountsList member accounts
- mx_technologies.list_statements_by_memberList statements by member
- mx_technologies.list_favorite_institutionsList favorite institutions
write
7Create and change things. Allow, or ask the user first.
- mx_technologies.create_memberCreate member
- mx_technologies.create_accountCreate account
- mx_technologies.update_transactionUpdate transaction
- mx_technologies.update_users_taggingsUpdate user tagging
- mx_technologies.create_partner_accountCreate Partner Account
- mx_technologies.update_transaction_rulesUpdate transaction rules
- mx_technologies.create_audience_api_credentialsRetrieve Audience API Credentials
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- mx_technologies.cancel_partner_accountDisable MX User Account
MX Technologies in three steps.
- 01Your users connect MX TechnologiesThey add their MX Technologies username and password on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create member” can wait for the user, and “disable MX User Account” can be denied outright.
- 03Any agent can actYour agent calls MX Technologies through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('mx_technologies', { read: 'allow', write: 'ask', // create_member destructive: 'deny', // cancel_partner_account }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How MX Technologies connects.
Users add their MX Technologies username and password on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same MX Technologies connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use MX Technologies from any agent.
More finance and accounting apps.
MX Technologies and Arc0, answered.
Can I use MX Technologies with Claude, ChatGPT or Cursor?
Yes. Connect MX Technologies to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the MX Technologies actions you allow.
How do users connect MX Technologies?
Users add their MX Technologies username and password on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which MX Technologies actions can my agent take?
36 in total: 28 read, 7 write and 1 destructive, such as “create member”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in MX Technologies?
Yes. Actions like “disable MX User Account” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call MX Technologies too?
Yes. The same MX Technologies connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug MX Technologies into your agent.
Your users connect MX Technologies once, under your brand. Your agent gets 36 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan