# How to integrate Mx technologies MCP with Mastra AI ```json { "title": "How to integrate Mx technologies MCP with Mastra AI", "toolkit": "Mx technologies", "toolkit_slug": "mx_technologies", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/mx_technologies/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/mx_technologies/framework/mastra-ai.md", "updated_at": "2026-09-24T11:17:04.354Z" } ``` ## Introduction This guide walks you through connecting Mx technologies to Mastra AI using the Composio tool router. By the end, you'll have a working Mx technologies agent that can create a manual account for a user, list account numbers for a specific member, fetch rewards for a connected member through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Mx technologies account through Composio's Mx technologies MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Mx technologies with - [Claude Code](https://composio.dev/toolkits/mx_technologies/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/mx_technologies/framework/claude-cowork) - [OpenAI Agents SDK](https://composio.dev/toolkits/mx_technologies/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/mx_technologies/framework/claude-agents-sdk) - [Codex](https://composio.dev/toolkits/mx_technologies/framework/codex) - [OpenClaw](https://composio.dev/toolkits/mx_technologies/framework/openclaw) - [Hermes](https://composio.dev/toolkits/mx_technologies/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/mx_technologies/framework/atomic-agent) - [Google ADK](https://composio.dev/toolkits/mx_technologies/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mx_technologies/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/mx_technologies/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/mx_technologies/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mx_technologies/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/mx_technologies/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/mx_technologies/framework/autogen) ## TL;DR Here's what you'll learn: - Set up your environment so Mastra, OpenAI, and Composio work together - Create a Tool Router session in Composio that exposes Mx technologies tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Mx technologies tool definitions and attach them as a toolset - Build a Mastra agent that can reason, call tools, and return structured results - Run an interactive CLI where you can chat with your Mx technologies agent ## What is Mastra AI? Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP. Key features include: - MCP Client: Built-in support for Model Context Protocol servers - Toolsets: Organize tools into logical groups - Step Callbacks: Monitor and debug agent execution - OpenAI Integration: Works with OpenAI models via @ai-sdk/openai ## What is the Mx technologies MCP server, and what's possible with it? The Mx technologies MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mx technologies account. It provides structured and secure access to financial data aggregation and account management features, so your agent can perform actions like creating accounts, managing members, fetching financial rewards, and handling account ownership on your behalf. - Automated account creation and management: Let your agent create new manual accounts, partner accounts, and user SSO accounts for seamless onboarding and testing. - Member aggregation and connection: Instruct your agent to create members and initiate aggregation of financial products across institutions, streamlining financial data collection. - Rewards and incentives tracking: Have your agent fetch and aggregate member rewards data after account connections, so you never miss out on incentives. - Secure access to account details: Direct your agent to list account owners, retrieve account numbers by member, and access configurable widget URLs for enhanced user interactions. - Credential and API management: Use your agent to retrieve API credentials for audience services, streamlining authentication flows and integrations. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `MX_TECHNOLOGIES_CANCEL_PARTNER_ACCOUNT` | Disable MX User Account | Disables an MX user account, preventing background updates to accounts and transactions and restricting data access. The user can be re-enabled later via the update user endpoint. Uses MX Platform API: PUT /users/{user_guid} with is_disabled=true. | | `MX_TECHNOLOGIES_CREATE_ACCOUNT` | Create account | Creates a manual account for a specified user in MX Platform. Use this tool when you need to: - Add an external/off-platform account that isn't aggregated through MX - Create a test account for development purposes - Track accounts from institutions not supported by MX aggregation Note: Manual accounts do not aggregate data from financial institutions. They are created under the special 'Manual Institution' member and require manual updates for balance and transaction information. Requires: A valid user_guid (obtained from List Users or Create User). | | `MX_TECHNOLOGIES_CREATE_AUDIENCE_API_CREDENTIALS` | 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 → Authentication → Audience API Key). The tool prefers explicitly provided values, then falls back to environment variables. | | `MX_TECHNOLOGIES_CREATE_MEMBER` | Create member | Create a member to connect a user to a financial institution. A member represents the relationship between an MX user and a financial institution. For non-OAuth institutions, provide credentials obtained from List Institution Credentials. For OAuth institutions, set is_oauth=true and use the returned oauth_window_uri. Prerequisites: - user_guid from List Users or Create User - institution_code from List Institutions - credentials from List Institution Credentials (for non-OAuth) Test credentials for MX Bank (mxbank): username='mxuser', password='password' | | `MX_TECHNOLOGIES_CREATE_PARTNER_ACCOUNT` | Create Partner Account | Create a new user (partner account) in the MX Platform. Users represent end-users in your application and are required before creating members, accounts, or accessing financial data. Use this tool to provision a new user record in MX. | | `MX_TECHNOLOGIES_FETCH_REWARDS` | Fetch rewards | Initiate rewards aggregation for a specific member. This triggers an async job to gather rewards data (points, miles, etc.) from the member's financial institution. Use List Rewards to retrieve the results after aggregation completes. | | `MX_TECHNOLOGIES_GET_CONFIGURABLE_WIDGET_URL` | Get configurable widget URL | Retrieve a configurable widget URL for embedding MX widgets (Connect, Transactions, Pulse, etc.). Use this tool to generate a single-use URL for displaying MX widgets to end users. The URL expires after 10 minutes or immediately upon first use, so always request a fresh URL when loading the widget. Requires a valid user_guid (obtained from list_users or create_user actions). | | `MX_TECHNOLOGIES_LIST_ACCOUNT_NUMBERS_BY_MEMBER` | List Account Numbers by Member | Tool to list account numbers for a specific member. Use after obtaining user and member GUIDs. | | `MX_TECHNOLOGIES_LIST_ACCOUNT_OWNERS` | List account owners | Tool to list account owners for a specific member. Returns identity information (name, address, contact details) for all account owners associated with the member's accounts. Requires user_guid and member_guid. Use this to retrieve account holder identity data for verification or compliance purposes. | | `MX_TECHNOLOGIES_LIST_ACCOUNTS` | List accounts | Tool to list all accounts for a user. Use after confirming the user GUID. | | `MX_TECHNOLOGIES_LIST_BUDGETS` | List budgets | List all budgets for a specific MX user. Budgets track spending limits for categories. Prerequisites: Obtain a valid user_guid from the List Users endpoint first. Note: Budgets are automatically generated based on transaction history or can be manually created. If a user has no budgets, an empty list is returned. | | `MX_TECHNOLOGIES_LIST_CATEGORIES` | 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. | | `MX_TECHNOLOGIES_LIST_CHALLENGES` | List challenges | Tool to list MFA challenges for a member. Use when the member is in CHALLENGED state to retrieve prompts to answer. | | `MX_TECHNOLOGIES_LIST_FAVORITE_INSTITUTIONS` | List favorite institutions | List the partner's favorite financial institutions, sorted by popularity. Use this tool to retrieve institutions that have been pre-configured as favorites for the partner account. Results are paginated and can be filtered by country. Note: Favorite institutions must be configured by MX - contact MX support to set up favorites. | | `MX_TECHNOLOGIES_LIST_GOALS` | List goals | List all financial goals for a specific MX user. Use this to retrieve a paginated list of the user's savings goals, including target amounts, progress, and completion dates. Requires a valid user GUID obtained from the LIST_USERS action. | | `MX_TECHNOLOGIES_LIST_INSTITUTION_CREDENTIALS` | List institution credentials | Tool to list credential fields required by a given institution. Use after selecting the institution code; supports optional pagination. | | `MX_TECHNOLOGIES_LIST_INSTITUTIONS` | 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. | | `MX_TECHNOLOGIES_LIST_MEMBER_ACCOUNTS` | 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. | | `MX_TECHNOLOGIES_LIST_MEMBERS` | List members | List all members (financial institution connections) for a specific user. A member represents a connection between a user and a financial institution. Use this tool to retrieve all members linked to a user, including their connection status, aggregation state, and institution details. Useful for checking which accounts are connected, identifying connection issues, or finding member GUIDs for other operations. Returns paginated results with member details and pagination info. | | `MX_TECHNOLOGIES_LIST_REWARDS` | List rewards | Lists rewards and loyalty program data for a specific member. Returns information about points, miles, and other rewards balances from connected financial institutions. Requires valid user_guid (from List Users) and member_guid (from List Members). Supports pagination for large result sets. | | `MX_TECHNOLOGIES_LIST_STATEMENTS_BY_MEMBER` | List statements by member | Retrieve a paginated list of monthly account statements (PDF) for a specific member. Use this tool after obtaining valid user_guid (via LIST_USERS) and member_guid (via LIST_MEMBERS). Statements include bank/credit statements in PDF format. The uri field in each statement can be used to download the actual PDF. | | `MX_TECHNOLOGIES_LIST_TAGGINGS` | List taggings | List all taggings for a specific MX user. Taggings are links between custom tags and transactions - they show which labels have been applied to which transactions. Use this when you need to: - See all tag-transaction associations for a user - Find which transactions have been labeled with custom tags - Audit or review a user's transaction categorization Prerequisites: Obtain a valid user_guid from LIST_USERS first. | | `MX_TECHNOLOGIES_LIST_TAGS` | List tags | List all custom tags associated with a specific MX user. Tags are labels that can be applied to transactions for organization. Every user has a default 'Business' tag. Returns paginated results. Use this to retrieve tag GUIDs needed for tagging transactions. | | `MX_TECHNOLOGIES_LIST_TRANSACTIONS` | List transactions | Retrieve all financial transactions for an MX user across all their connected accounts and members. Use this tool to get a user's complete transaction history. Supports pagination, date filtering, and optional enhanced data (merchants, geolocations, classifications, repeating transactions). Prerequisites: You need a valid MX user GUID (starts with 'USR-'). Get this from the List Users action. | | `MX_TECHNOLOGIES_LIST_TRANSACTIONS_BY_MEMBER` | List transactions by member | Tool to list transactions for a member. Use when you have valid user and member GUIDs and need their transactions. | | `MX_TECHNOLOGIES_LIST_USERS` | List users | List all users in the MX Platform. Use this to retrieve a paginated list of user accounts with optional filters by ID, email, or disabled status. Each user represents an end user accessing MX Platform through your application. Returns user details including guid (MX identifier), id (partner-defined identifier), email, and account status flags. | | `MX_TECHNOLOGIES_READ_ACCOUNT` | 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. | | `MX_TECHNOLOGIES_READ_CATEGORY` | Read category | Tool to retrieve a default category by GUID. Use after confirming the default category GUID. | | `MX_TECHNOLOGIES_READ_FDX_ACCOUNT` | Read FDX account | Retrieve details for a specific account using the FDX 4.6 standard API. This action fetches comprehensive account information including balances, status, and account attributes. It requires an FDX account identifier. AUTHENTICATION: This endpoint requires OAuth Bearer token authentication obtained from the MX Data Access OAuth flow. Basic Auth credentials for the MX Platform API will not work with FDX endpoints. FALLBACK: If FDX endpoints fail and the account_id looks like an MX Platform GUID (starts with 'ACC-' or 'ACT-'), the action will attempt to use the MX Platform API to retrieve the account instead. | | `MX_TECHNOLOGIES_READ_INSTITUTION` | Read institution | Tool to retrieve details for a specific institution by code. Use when you need to get information about a particular financial institution using its unique code. | | `MX_TECHNOLOGIES_READ_TRANSACTION` | Read transaction | Tool to retrieve details for a specific transaction by its GUID. Use when you need to fetch information about a particular transaction for a user. | | `MX_TECHNOLOGIES_READ_TRANSACTION_BY_ACCOUNT` | Read transaction by account | Tool to retrieve details for a specific transaction by account. Use when you need to fetch information about a particular transaction using user, member, account, and transaction identifiers. Supports optional enhancements like merchant details, geolocations, classifications, and repeating transaction patterns. | | `MX_TECHNOLOGIES_READ_TRANSACTION_RULE` | Read transaction rule | Tool to retrieve details for a specific transaction rule by its GUID. Use when you need to fetch information about a particular transaction rule for a user. | | `MX_TECHNOLOGIES_UPDATE_TRANSACTION` | Update transaction | Tool to update a specific transaction's description. Use when you need to modify the description of an existing transaction. | | `MX_TECHNOLOGIES_UPDATE_TRANSACTION_RULES` | Update transaction rules | Tool to update an existing transaction rule. Use when you need to modify how transactions are categorized or described based on pattern matching. Note: Changes to match_description will only be applied to future transactions. | | `MX_TECHNOLOGIES_UPDATE_USERS_TAGGINGS` | Update user tagging | Tool to update a tagging for an MX user. Use when you need to change which tag is associated with a specific transaction. A tagging represents the link between a custom tag and a transaction. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Mx technologies MCP server is an implementation of the Model Context Protocol that connects your AI agent to Mx technologies. It provides structured and secure access so your agent can perform Mx technologies operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Node.js 18 or higher - A Composio account with an active API key - An OpenAI API key - Basic familiarity with TypeScript ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. - You need credits or a connected billing setup to use the models. - Store the key somewhere safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Mx technologies through MCP. ### 2. Install dependencies Install the required packages. What's happening: - @composio/core is the Composio SDK for creating MCP sessions - @mastra/core provides the Agent class - @mastra/mcp is Mastra's MCP client - @ai-sdk/openai is the model wrapper for OpenAI - dotenv loads environment variables from .env ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your requests to Composio - COMPOSIO_USER_ID tells Composio which user this session belongs to - OPENAI_API_KEY lets the Mastra agent call OpenAI models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment What's happening: - dotenv/config auto loads your .env so process.env.* is available - openai gives you a Mastra compatible model wrapper - Agent is the Mastra agent that will call tools and produce answers - MCPClient connects Mastra to your Composio MCP server - Composio is used to create a Tool Router session ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string, }); ``` ### 5. Create a Tool Router session for Mx technologies What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "mx_technologies" for Mx technologies access - session.mcp.url is the MCP URL that Mastra's MCPClient will connect to ```typescript async function main() { const session = await composio.create( composioUserID as string, { toolkits: ["mx_technologies"], }, ); const composioMCPUrl = session.mcp.url; console.log("Mx technologies MCP URL:", composioMCPUrl); ``` ### 6. Configure Mastra MCP client and fetch tools What's happening: - MCPClient takes an id for this client and a list of MCP servers - The headers property includes the x-api-key for authentication - getTools fetches the tool definitions exposed by the Mx technologies toolkit ```typescript const mcpClient = new MCPClient({ id: composioUserID as string, servers: { nasdaq: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); console.log("Fetching MCP tools from Composio..."); const composioTools = await mcpClient.getTools(); console.log("Number of tools:", Object.keys(composioTools).length); ``` ### 7. Create the Mastra agent What's happening: - Agent is the core Mastra agent - name is just an identifier for logging and debugging - instructions guide the agent to use tools instead of only answering in natural language - model uses openai("gpt-5") to configure the underlying LLM ```typescript const agent = new Agent({ name: "mx_technologies-mastra-agent", instructions: "You are an AI agent with Mx technologies tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface What's happening: - messages keeps the full conversation history in Mastra's expected format - agent.generate runs the agent with conversation history and Mx technologies toolsets - maxSteps limits how many tool calls the agent can take in a single run - onStepFinish is a hook that prints intermediate steps for debugging ```typescript let messages: AiMessageType[] = []; console.log("Chat started! Type 'exit' or 'quit' to end.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmedInput, }); console.log("\nAgent is thinking...\n"); try { const response = await agent.generate(messages, { toolsets: { mx_technologies: composioTools, }, maxSteps: 8, }); const { text } = response; if (text && text.trim().length > 0) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text, }); } } catch (error) { console.error("\nError:", error); } rl.prompt(); }); rl.on("close", async () => { console.log("\nSession ended."); await mcpClient.disconnect(); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string }); async function main() { const session = await composio.create(composioUserID as string, { toolkits: ["mx_technologies"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { mx_technologies: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "mx_technologies-mastra-agent", instructions: "You are an AI agent with Mx technologies tools via Composio.", model: "openai/gpt-5", }); let messages: AiMessageType[] = []; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (input: string) => { const trimmed = input.trim(); if (["exit", "quit"].includes(trimmed.toLowerCase())) { rl.close(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed }); const { text } = await agent.generate(messages, { toolsets: { mx_technologies: composioTools }, maxSteps: 8, }); if (text) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text }); } rl.prompt(); }); rl.on("close", async () => { await mcpClient.disconnect(); process.exit(0); }); } main(); ``` ## Conclusion You've built a Mastra AI agent that can interact with Mx technologies through Composio's Tool Router. You can extend this further by: - Adding other toolkits like Gmail, Slack, or GitHub - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows ## How to build Mx technologies MCP Agent with another framework - [Claude Code](https://composio.dev/toolkits/mx_technologies/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/mx_technologies/framework/claude-cowork) - [OpenAI Agents SDK](https://composio.dev/toolkits/mx_technologies/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/mx_technologies/framework/claude-agents-sdk) - [Codex](https://composio.dev/toolkits/mx_technologies/framework/codex) - [OpenClaw](https://composio.dev/toolkits/mx_technologies/framework/openclaw) - [Hermes](https://composio.dev/toolkits/mx_technologies/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/mx_technologies/framework/atomic-agent) - [Google ADK](https://composio.dev/toolkits/mx_technologies/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mx_technologies/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/mx_technologies/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/mx_technologies/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mx_technologies/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/mx_technologies/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/mx_technologies/framework/autogen) ## Related Toolkits - [Stripe](https://composio.dev/toolkits/stripe) - Stripe is a global online payments platform offering APIs for managing payments, customers, and subscriptions. Trusted by businesses for secure, efficient, and scalable payment processing worldwide. - [44API](https://composio.dev/toolkits/44api) - 44API is an API service for validating VAT and tax identifiers and returning company details. Use it to verify business tax data and manage account IP whitelists quickly. - [Airwallex](https://composio.dev/toolkits/airwallex) - Airwallex is a global financial platform providing business accounts, payments, payouts, FX, and cards. Built to simplify cross-border payments and streamline financial operations for businesses. - [Aiwyn Tax MCP](https://composio.dev/toolkits/aiwyn_tax_mcp) - Aiwyn Tax MCP is a tax estimation service powered by Aiwyn's federal and state tax engine. It helps teams estimate tax outcomes without building tax calculation logic from scratch. - [Alpaca](https://composio.dev/toolkits/alpaca) - Alpaca is a stock and crypto trading platform for commission-free trading, real-time market data, and algorithmic strategies. Use it to build brokerage apps, trading bots, and portfolio workflows with market connectivity. - [Alpha vantage](https://composio.dev/toolkits/alpha_vantage) - Alpha Vantage is a financial data platform offering real-time and historical stock market APIs. Get instant, reliable access to equities, forex, and technical analysis data for smarter trading decisions. - [Altoviz](https://composio.dev/toolkits/altoviz) - Altoviz is a cloud-based billing and invoicing platform for businesses. It streamlines online payments, expense tracking, and customizable invoice management. - [Benzinga](https://composio.dev/toolkits/benzinga) - Benzinga provides real-time financial news and data APIs for market coverage. It helps you track breaking news and actionable market insights instantly. - [Bigdata.com MCP](https://composio.dev/toolkits/bigdata_com_mcp) - Bigdata.com MCP provides grounded access to financial news, transcripts, filings, and entity intelligence. Ideal for building research workflows and generating timely market insights. - [Billsby](https://composio.dev/toolkits/billsby) - Billsby is a subscription billing platform for managing customers, subscriptions, invoices, products, plans, usage counters, add-ons, and allowances. It helps SaaS and subscription teams automate billing operations without building complex billing logic from scratch. - [Brex](https://composio.dev/toolkits/brex) - Brex provides corporate credit cards and spend management tailored for startups and tech businesses. It helps optimize company cash flow, streamline accounting, and accelerate business growth. - [Cashfree Payments MCP](https://composio.dev/toolkits/cashfree_payments_mcp) - Cashfree Payments MCP is a merchant payments platform that handles collection, payouts, subscriptions, settlements, refunds, and identity verification. Simplifies merchant money lifecycle management with unified, API-driven workflows. - [Chaser](https://composio.dev/toolkits/chaser) - Chaser is accounts receivable automation software that sends invoice reminders and helps businesses get paid faster. It streamlines the collections process to save time and improve cash flow. - [Clarity AI MCP](https://composio.dev/toolkits/clarity_ai_mcp) - Clarity AI MCP is an MCP toolkit for simulating SFDR 2.0 fund classifications from a fund name, ISIN, or CUSIP. Use it to tap Clarity AI disclosure data and modeling without building custom sustainability-data workflows. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Coinbase](https://composio.dev/toolkits/coinbase) - Coinbase is a platform for buying, selling, and storing cryptocurrency. It makes exchanging and managing crypto simple and secure for everyone. - [Coinbase Agents MCP](https://composio.dev/toolkits/coinbase_agents_mcp) - Coinbase Agents MCP is Coinbase's managed toolkit exposing accounts, portfolios, orders, fills, and market data. Use it to let authorized agents inspect holdings, execute trades, perform transfers, and handle payments. - [Coinbase Wallet MCP](https://composio.dev/toolkits/coinbase_wallet_mcp) - Coinbase Wallet MCP is Coinbase's wallet service for interacting with onchain accounts. Use it to give agents secure, structured access to inspect wallets and request onchain actions. - [Coinranking](https://composio.dev/toolkits/coinranking) - Coinranking is a comprehensive cryptocurrency market data platform offering access to real-time coin prices, market caps, and historical data. Get accurate, up-to-date stats for thousands of digital assets in one place. - [Coupa](https://composio.dev/toolkits/coupa) - Coupa is a business spend management platform for procurement, invoicing, and expenses. It helps organizations streamline purchasing, control costs, and gain complete visibility over financial operations. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Mx technologies MCP? With a standalone Mx technologies MCP server, the agents and LLMs can only access a fixed set of Mx technologies tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mx technologies and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Mastra AI? Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Mx technologies tools. ### Can I manage the permissions and scopes for Mx technologies while using Tool Router? Yes, absolutely. You can configure which Mx technologies scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Mx technologies data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)