MX Technologies
MX Technologies provides a comprehensive API platform for aggregating and enhancing financial data, enabling seamless connections to numerous financial institutions.
Verdict
Common use cases
- Provision client accounts for new fintech users
- Aggregate bank transactions for spending analysis
- Generate embeddable widgets for customer dashboards
- Trigger rewards aggregation after member signup
- List account numbers for compliance audits
Integration
- Vendor
- MX Technologies
- Category
- developer-tools
- Auth
- OAUTH2
- Tools
- 33
- Composio slug
mx_technologies
Tools
- Cancel Partner Account
Tool to cancel (disable) a client account under a partner account. this maps to mx platform api: put /users/{guid} with body {"user": {"is disabled": true, "metadata": "..."}}.
- Create account
Tool to create a manual account for a given user. use when you need to add an external or test account to a user record.
- Create member
Tool to create a member and start aggregating specified financial products. use after confirming user guid and gathering connection credentials or oauth details.
- Create Partner Account
Tool to create a new client account under a partner account. use when provisioning a new constant contact client after obtaining api key and jwt authorization.
- Create Partner Account User SSO
Tool to create a new partner account user with single sign-on enabled. use when adding an sso user under a partner client account with 'sso for all users' enabled.
- Fetch rewards
Tool to initiate rewards aggregation for a specific member. use after connecting the member to trigger an async rewards job.
- Get configurable widget URL
Tool to retrieve a configurable widget url for a user. use after determining the user guid.
- List Account Numbers by Member
Tool to list account numbers for a specific member. use after obtaining user and member guids.
- List account owners
Tool to list account owners associated with a member's account. use after validating user and member guids.
- List account owners by member
Tool to list account owners for a specific member. use when you have the user guid and member guid.
- List accounts
Tool to list all accounts for a user. use after confirming the user guid.
- List budgets
Tool to list budgets for a specific user. use after obtaining a valid user guid to retrieve that user’s budgets.
- List categories
Tool to list all categories for a user. use when you need to fetch both default and custom categories for a given user guid.
- List challenges
Tool to list mfa challenges for a member. use when the member is in challenged state to retrieve prompts to answer.
- List Connect Widget URLs
Tool to list connect widget urls for a user. use when you need to retrieve all connect widget urls associated with a user.
- List favorite institutions
Tool to list partner favorite institutions, sorted by popularity. use when you need to retrieve a paginated set of a partner's favorite institutions.
- List goals
Tool to list goals for a specific user. use after obtaining a valid user guid to view user goals.
- List institution credentials
Tool to list credential fields required by a given institution. use after selecting the institution code; supports optional pagination.
- List institutions
Tool to list financial institutions supported by mx. use when you need to retrieve available institutions with optional filters like name, country code, or products; supports pagination.
- List member accounts
Tool to list accounts for a specific member. use when you need to retrieve all accounts associated with a given user and member guid.
- List members
Tool to list members associated with a specific user. use when you need to retrieve the members for a given user guid.
- List rewards
Tool to list rewards associated with a specific user and member. use after confirming both user guid and member guid; supports pagination.
- List statements by member
Tool to list statements for a member. use after obtaining valid user and member guids.
- List taggings
Tool to list all taggings for a specific user. use when you need to fetch taggings associated with a user after obtaining their user guid.
- List tags
Tool to list all tags for a user. use after obtaining a valid user guid; supports pagination.
- List transactions
Tool to list transactions for a user. use when you need to retrieve a user's transaction history across all accounts. use after obtaining a valid user guid.
- List transactions by member
Tool to list transactions for a member. use when you have valid user and member guids and need their transactions.
- List users
Tool to list users. use when you need to retrieve a paginated list of user accounts with optional filters.
- Read account
Tool to retrieve details for a specific account. use after obtaining valid user and account guids to fetch up-to-date account information.
- Read account balance
Tool to retrieve the available balance for a specific account. use after confirming the user and account guids.
- Read category
Tool to retrieve a default category by guid. use after confirming the default category guid.
- Read FDX account
Tool to return details for the specified fdx account. use when you have an fdx accountid and need full account info.
- Retrieve Audience API Credentials
Tool to retrieve audience api credentials. use when obtaining client id and client secret for audience service authentication before generating an access token. credentials must be created in the partner dashboard (partner administrator → a
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find MX Technologies in the developer tools section and click Connect. 3. You'll be redirected to MX's OAuth consent screen — sign in with your MX Platform credentials. 4. Grant the requested scopes (user management, member aggregation, account read/write, widget generation). 5. After authorization, Switchy redirects you back and confirms the connection is live. 6. Open any Space and type '@MX Technologies list my partner accounts' to verify the integration works. 7. If you see account data returned, you're ready to invoke any of the 33 tools by @mentioning MX Technologies and describing the task.
What teammates see: by default, memories from MX Technologies are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Test Account
@MX Technologies create a manual checking account for user guid usr_12345 with a starting balance of $1000 and label it 'Test Account Q1'.Open in a Space →
Pull Member Transactions
@MX Technologies list all transactions for member mbr_67890 from the last 30 days and summarize spending by category.Open in a Space →
Generate Widget URL
@MX Technologies get the configurable widget URL for user guid usr_54321 and return the full embed code.Open in a Space →
Initiate Rewards Sync
@MX Technologies fetch rewards data for member mbr_11223 and notify me when the job completes.Open in a Space →
Provision Partner Account
@MX Technologies create a partner account for client 'Acme Finance' with metadata including their API key and contact email.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@mx list all account numbers for member mem-abc123 under user usr-xyz789
Here are the account numbers for member mem-abc123: • Checking Account: ****1234 (Chase Bank) • Savings Account: ****5678 (Chase Bank) • Credit Card: ****9012 (Capital One) All three accounts are currently active and last aggregated 2 hours ago. The checking account shows a current balance of $3,247.18, savings shows $12,450.00, and the credit card has a $1,203.45 balance.
This example demonstrates read-only account enumeration. Requires valid user_guid and member_guid from your MX environment. Account numbers are masked by default for PCI compliance. If aggregation hasn't run recently, balances may be stale—trigger a refresh via the 'aggregate member' tool if needed.
@mx create a manual checking account for user usr-xyz789 with account number 9876543210 and current balance $5000
Manual account created successfully: • Account GUID: acc-manual-def456 • Type: Checking • Account Number: ****3210 (masked) • Balance: $5,000.00 • Institution: Manual Entry • Status: Active This account is now visible in the user's account list and will appear in transaction aggregation queries. You can update the balance or add transactions manually using the account GUID.
This write operation creates a persistent account record in MX's system. Useful for testing or tracking external accounts not supported by MX's aggregation network. The account won't auto-update—you must manually post transactions or balance changes. Requires user:write scope in your OAuth2 token.
@mx fetch the configurable widget URL for user usr-xyz789, then summarize what financial data this user has connected
Widget URL generated: https://widgets.mx.com/connect?token=eyJhbG... (expires in 15 minutes) Based on this user's connected accounts, they have: • 2 bank accounts at Chase (checking and savings, totaling $15,697.18) • 1 credit card at Capital One ($1,203.45 balance, $5,000 limit) • Last aggregation: 2 hours ago across all members The user has one active member connection (mem-abc123) covering all three accounts. No rewards programs are currently linked.
This example pairs MX's widget generation (a write operation that creates a time-limited URL) with AI synthesis of the user's financial graph. The widget URL is single-use and expires quickly—don't cache it. Aggregation timing matters: if accounts haven't synced recently, the summary will reflect stale data. Requires both user:read and widget:write scopes.
Use-case deep-dives
When MX wins for white-label account provisioning
A 6-person fintech startup building a budgeting app needs to spin up user accounts and link bank credentials without writing aggregation logic from scratch. MX's Create Partner Account and Create Member tools handle the OAuth dance and account creation in one call, which beats building your own Plaid wrapper if you're already on MX's platform. The 33-tool surface means you're committing to their ecosystem—fine if you need rewards aggregation or widget embeds, overkill if you only want transaction pulls. The OAuth2 scope is partner-level, so one integration covers all your end-users. If your roadmap includes white-labeled financial widgets or multi-institution aggregation, this MCP pays off in week two.
Why support teams skip this MCP for now
A 3-person support team at a personal finance SaaS gets tickets about missing transactions or broken bank links twice a day. MX's List Account Numbers and Fetch Rewards tools could surface the data, but the 33-tool catalog is built for developers provisioning accounts, not support reps diagnosing user issues. Your support flow needs read-only queries and error logs—MX's tooling assumes you're writing records or triggering aggregation jobs. If your support team already lives in Intercom or Zendesk, a simpler read-only API wrapper (or a custom MCP with 4 tools instead of 33) will close tickets faster. Save MX for backend automation, not frontline triage.
When this MCP handles multi-tenant client setup
A 12-person B2B fintech sells white-labeled budgeting tools to credit unions. Each new credit union needs a partner account, SSO users, and member aggregation turned on—manually clicking through MX's dashboard for 40 clients per quarter burns 6 hours. The Create Partner Account and Create Partner Account User SSO tools automate the entire flow in a Slack workflow: sales closes the deal, ops runs /provision-client, and the credit union's users can log in same-day. The OAuth2 setup is one-time; after that, the MCP handles provisioning without touching the MX console. If you're onboarding fewer than 5 partners per month, the manual dashboard is faster. Above that threshold, this MCP turns a half-day task into a 2-minute Slack command.
Frequently asked
What does the MX Technologies MCP do in Switchy?
It connects your team to MX's financial data aggregation platform. You can create and manage user accounts, add manual or aggregated financial accounts, initiate member connections to banks, and retrieve account numbers or rewards data. This is useful if you're building fintech features or need programmatic access to financial institution data MX aggregates.
Do I need partner-level MX credentials to use this MCP?
Yes. The MCP uses OAuth2 and expects partner account access — you'll need an API key and JWT authorization from MX. Several tools (Create Partner Account, Create Partner Account User SSO) explicitly require partner-level permissions. If you only have end-user credentials, this integration won't work; contact MX to upgrade your account type.
Can the MX MCP send money or execute transactions?
No. The 33 tools focus on account creation, member aggregation, and data retrieval (account numbers, rewards). MX's platform supports payments in some contexts, but this MCP doesn't expose transaction or transfer tools. If you need to move money, you'll have to call MX's API directly or use a different integration.
Why use this MCP instead of calling MX's API directly?
The MCP wraps MX's REST endpoints in natural-language tools, so your team can say "create a member for user X" instead of writing PUT /users/{guid} with JSON payloads. It's faster for prototyping and non-engineers. If you already have production API code, stick with that — the MCP adds a conversational layer, not new capabilities.
Who on my team should connect the MX integration?
Whoever holds your MX partner API key and understands your user provisioning flow. This is typically a backend engineer or fintech product lead. The person connecting it will authenticate once via OAuth2; after that, any Switchy team member can invoke the tools in shared chats, subject to your workspace permissions.