# How to integrate Mx technologies MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Mx technologies MCP with Vercel AI SDK v6", "toolkit": "Mx technologies", "toolkit_slug": "mx_technologies", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/mx_technologies/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/mx_technologies/framework/ai-sdk.md", "updated_at": "2026-05-06T08:20:57.749Z" } ``` ## Introduction This guide walks you through connecting Mx technologies to Vercel AI SDK v6 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 Vercel AI SDK 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 - [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) - [Claude Code](https://composio.dev/toolkits/mx_technologies/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/mx_technologies/framework/claude-cowork) - [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) - [CLI](https://composio.dev/toolkits/mx_technologies/framework/cli) - [Google ADK](https://composio.dev/toolkits/mx_technologies/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mx_technologies/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/mx_technologies/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/mx_technologies/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mx_technologies/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Mx technologies integration - Using Composio's Tool Router to dynamically load and access Mx technologies tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## 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` | 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": "..."}}. | | `MX_TECHNOLOGIES_CREATE_ACCOUNT` | 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. | | `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 | Tool to create a member and start aggregating specified financial products. use after confirming user guid and gathering connection credentials or oauth details. | | `MX_TECHNOLOGIES_CREATE_PARTNER_ACCOUNT` | 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. | | `MX_TECHNOLOGIES_CREATE_PARTNER_ACCOUNT_USER_SSO` | 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. | | `MX_TECHNOLOGIES_FETCH_REWARDS` | Fetch rewards | Tool to initiate rewards aggregation for a specific member. use after connecting the member to trigger an async rewards job. | | `MX_TECHNOLOGIES_GET_CONFIGURABLE_WIDGET_URL` | Get configurable widget URL | Tool to retrieve a configurable widget url for a user. use after determining the user guid. | | `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 associated with a member's account. use after validating user and member guids. | | `MX_TECHNOLOGIES_LIST_ACCOUNT_OWNERS_BY_MEMBER` | List account owners by member | Tool to list account owners for a specific member. use when you have the user guid and member guid. | | `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 | Tool to list budgets for a specific user. use after obtaining a valid user guid to retrieve that user’s budgets. | | `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_CONNECT_WIDGET_URLS` | 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. | | `MX_TECHNOLOGIES_LIST_FAVORITE_INSTITUTIONS` | 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. | | `MX_TECHNOLOGIES_LIST_GOALS` | List goals | Tool to list goals for a specific user. use after obtaining a valid user guid to view user goals. | | `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 | Tool to list members associated with a specific user. use when you need to retrieve the members for a given user guid. | | `MX_TECHNOLOGIES_LIST_REWARDS` | List rewards | Tool to list rewards associated with a specific user and member. use after confirming both user guid and member guid; supports pagination. | | `MX_TECHNOLOGIES_LIST_STATEMENTS_BY_MEMBER` | List statements by member | Tool to list statements for a member. use after obtaining valid user and member guids. | | `MX_TECHNOLOGIES_LIST_TAGGINGS` | 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. | | `MX_TECHNOLOGIES_LIST_TAGS` | List tags | Tool to list all tags for a user. use after obtaining a valid user guid; supports pagination. | | `MX_TECHNOLOGIES_LIST_TRANSACTIONS` | 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. | | `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 | Tool to list users. use when you need to retrieve a paginated list of user accounts with optional filters. | | `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_ACCOUNT_BALANCE` | Read account balance | Tool to retrieve the available balance for a specific account. use after confirming the user and account guids. | | `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 | Tool to return details for the specified fdx account. use when you have an fdx accountid and need full account info. | ## 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 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'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Mx technologies tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Mx technologies-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["mx_technologies"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Mx technologies tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to mx_technologies, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Mx technologies tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript 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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); 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 { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["mx_technologies"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to mx_technologies, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Mx technologies agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Mx technologies MCP Agent with another framework - [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) - [Claude Code](https://composio.dev/toolkits/mx_technologies/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/mx_technologies/framework/claude-cowork) - [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) - [CLI](https://composio.dev/toolkits/mx_technologies/framework/cli) - [Google ADK](https://composio.dev/toolkits/mx_technologies/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mx_technologies/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/mx_technologies/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/mx_technologies/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mx_technologies/framework/crew-ai) ## 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. - [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. - [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. - [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. - [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. - [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. - [CurrencyScoop](https://composio.dev/toolkits/currencyscoop) - CurrencyScoop is a developer-friendly API for real-time and historical currency exchange rates. Easily access fiat and crypto data for smart, up-to-date financial applications. - [Daffy](https://composio.dev/toolkits/daffy) - Daffy is a modern charitable giving platform with a donor-advised fund. Easily set aside funds, grow them tax-free, and donate to over 1.7 million U.S. charities. - [Eagle doc](https://composio.dev/toolkits/eagle_doc) - Eagle doc is an AI-powered OCR API for invoices and receipts. It delivers fast, reliable, and accurate document data extraction for seamless automation. - [Elorus](https://composio.dev/toolkits/elorus) - Elorus is an online invoicing and time-tracking software for freelancers and small businesses. Easily manage finances, bill clients, and track work in one place. - [Eodhd apis](https://composio.dev/toolkits/eodhd_apis) - Eodhd apis delivers comprehensive financial data, including live and historical stock prices, via robust APIs. Easily access reliable, up-to-date market insights to power your apps, dashboards, and analytics. - [Fidel api](https://composio.dev/toolkits/fidel_api) - Fidel api is a secure platform for linking payment cards to web and mobile apps. It enables real-time card transaction monitoring and event-based automation for businesses. - [Finage](https://composio.dev/toolkits/finage) - Finage is a secure API platform delivering real-time and historical financial data for stocks, forex, crypto, indices, and commodities. It empowers developers and businesses to access, analyze, and act on market data instantly. - [Finmei](https://composio.dev/toolkits/finmei) - Finmei is an invoicing tool that simplifies billing, invoice management, and expense tracking. Ideal for automating and organizing your business finances in one place. - [Fixer](https://composio.dev/toolkits/fixer) - Fixer is a currency data API offering real-time and historical exchange rates for 170 currencies. Instantly access accurate, up-to-date forex data for your applications and workflows. - [Fixer io](https://composio.dev/toolkits/fixer_io) - Fixer.io is a lightweight API for real-time and historical foreign exchange rates. It makes global currency conversion fast, accurate, and hassle-free. ## 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 Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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)