# How to integrate Semrush MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Semrush MCP with Vercel AI SDK v6", "toolkit": "Semrush", "toolkit_slug": "semrush", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/semrush/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/semrush/framework/ai-sdk.md", "updated_at": "2026-05-06T08:27:20.223Z" } ``` ## Introduction This guide walks you through connecting Semrush to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Semrush agent that can show top anchor texts for example.com, compare backlink profiles for three domains, get keyword overview for 'organic coffee' through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Semrush account through Composio's Semrush MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Semrush with - [ChatGPT](https://composio.dev/toolkits/semrush/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/semrush/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/semrush/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/semrush/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/semrush/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/semrush/framework/codex) - [Cursor](https://composio.dev/toolkits/semrush/framework/cursor) - [VS Code](https://composio.dev/toolkits/semrush/framework/vscode) - [OpenCode](https://composio.dev/toolkits/semrush/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/semrush/framework/openclaw) - [Hermes](https://composio.dev/toolkits/semrush/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/semrush/framework/cli) - [Google ADK](https://composio.dev/toolkits/semrush/framework/google-adk) - [LangChain](https://composio.dev/toolkits/semrush/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/semrush/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/semrush/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/semrush/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Semrush integration - Using Composio's Tool Router to dynamically load and access Semrush 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 Semrush MCP server, and what's possible with it? The Semrush MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Semrush account. It provides structured and secure access to your SEO, keyword, and advertising analytics, so your agent can perform actions like keyword research, competitor analysis, backlink audits, and ad copy retrieval automatically on your behalf. - Comprehensive keyword research and reporting: Let your agent fetch broad match keywords, generate batch keyword overviews, and analyze key SEO metrics like search volume and difficulty in real time. - Competitor and backlink analysis: Ask your agent to pull backlink profiles, perform batch comparisons of domains, and summarize backlink authority and link types for competitive intelligence. - Ad campaign and copy insights: Have the agent retrieve unique Google Ads copies for any domain, helping you benchmark and optimize your own ad strategies based on real competitor data. - Content and category profiling: Enable your agent to analyze and categorize domains or URLs, surfacing topic strengths and audience focus areas for smarter content planning. - Anchor text and authority monitoring: Direct your agent to report on anchor text distributions and authority score profiles, giving you actionable insights for improving link-building efforts. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SEMRUSH_ADS_COPIES` | Get ad copies | Retrieves unique ad copies semrush has observed for a specified domain from a regional database, detailing ads seen in google's paid search results. | | `SEMRUSH_ANCHORS` | Get anchor texts | Use this action to get a csv report of anchor texts for backlinks pointing to a specified, publicly accessible domain, root domain, or url. | | `SEMRUSH_AUTHORITY_SCORE_PROFILE` | Get authority score profile | Retrieves the authority score (as) profile for a specified target, showing the count of referring domains that link to the target for each as value from 0 to 100. | | `SEMRUSH_BACKLINKS` | Get backlinks | Fetches backlinks for a specified domain or url as a csv-formatted string, allowing customization of columns, sorting, and filtering; ensure `display limit` surpasses `display offset` when an offset is used, and note the `urlanchor` filter may have limitations for targets with extensive backlinks. | | `SEMRUSH_BACKLINKS_OVERVIEW` | Backlinks overview | Provides a csv-formatted summary of backlinks, including authority score and link type breakdowns, for a specified and publicly accessible domain, root domain, or url. | | `SEMRUSH_BATCH_COMPARISON` | Batch comparison | Compares backlink profiles for multiple specified targets (domains, subdomains, or urls) to analyze and compare link-building efforts. | | `SEMRUSH_BATCH_KEYWORD_OVERVIEW` | Batch keyword overview | Fetches a keyword overview report from a semrush regional database for up to 100 keywords, providing metrics like search volume, cpc, and keyword difficulty. | | `SEMRUSH_BROAD_MATCH_KEYWORD` | Broad match keyword | Fetches broad match keywords for a given phrase; `display sort` and `display filter` parameters are defined but currently not utilized by the api call. | | `SEMRUSH_CATEGORIES` | Get categories | Retrieves categories and their 0-1 confidence ratings for a specified domain, subdomain, or url, with results sorted by rating. | | `SEMRUSH_CATEGORIES_PROFILE` | Get categories profile | Retrieves a profile of content categories from referring domains for a specified target, analyzing its first 10,000 referring domains and sorting results by domain count. | | `SEMRUSH_COMPETITORS` | Get competitor data | Retrieves a customizable csv report of competitors for a specified target (root domain, domain, or url) based on shared backlinks or referring domains, ensuring the target is valid and its type is correctly specified. | | `SEMRUSH_COMPETITORS_IN_ORGANIC_SEARCH` | Get competitors in organic search | Use to get a domain's organic search competitors from semrush as a semicolon-separated string; `display date` requires 'yyyymm15' format if used. | | `SEMRUSH_COMPETITORS_IN_PAID_SEARCH` | Get competitors in paid search | Retrieves a list of a domain's competitors in paid search results from a specified regional database. | | `SEMRUSH_DOMAIN_AD_HISTORY` | Get domain ad history | Retrieves a domain's 12-month advertising history from semrush (keywords bid on, ad positions, ad copy) for ppc strategy and competitor analysis; most effective when the domain has ad history in the selected database. | | `SEMRUSH_DOMAIN_ORGANIC_PAGES` | Get domain organic pages | Fetches a report on a domain's unique organic pages ranking in google's top 100 search results, with options for specifying database, date, columns, sorting, and filtering. | | `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS` | Get domain organic search keywords | Retrieves organic search keywords for a domain from a specified semrush regional database; `display positions` must be set if `display daily=1` for daily updates. | | `SEMRUSH_DOMAIN_ORGANIC_SUBDOMAINS` | Get domain organic subdomains | Retrieves a report on subdomains of a given domain that rank in google's top 100 organic search results for a specified regional database. | | `SEMRUSH_DOMAIN_PAID_SEARCH_KEYWORDS` | Get domain paid search keywords | Fetches keywords driving paid search traffic to a specified, existing domain using a supported semrush regional database. | | `SEMRUSH_DOMAIN_PLA_SEARCH_KEYWORDS` | Get PLA search keywords for a domain | Retrieves product listing ad (pla) search keywords for a specified domain from a semrush regional database. | | `SEMRUSH_DOMAIN_VS_DOMAIN` | Compare domains | Analyzes keyword rankings by comparing up to five domains to find common, unique, or gap keywords, using specified organic/paid types and comparison logic in the `domains` string. | | `SEMRUSH_HISTORICAL_DATA` | Get historical data | Retrieves monthly historical backlink and referring domain data for a specified root domain, returned as a time series string with newest records first. | | `SEMRUSH_INDEXED_PAGES` | Get indexed pages | Retrieves a list of indexed pages from semrush for a specified `target` (root domain, domain, or url) and `target type`, ensuring `target` is publicly accessible, semrush-analyzable, and correctly matches `target type`. | | `SEMRUSH_KEYWORD_DIFFICULTY` | Get keyword difficulty | Determines the keyword difficulty (kd) score (0-100, higher means greater difficulty) for a given phrase in a specific semrush regional database to assess its seo competitiveness. | | `SEMRUSH_KEYWORD_OVERVIEW_ALL_DATABASES` | Keyword overview all databases | Fetches a keyword overview from semrush for a specified phrase, including metrics like search volume, cpc, and competition. | | `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE` | Get keyword overview for one database | Fetches a keyword summary for a specified phrase from a chosen regional database. | | `SEMRUSH_KEYWORDS_ADS_HISTORY` | Get keywords ads history | Fetches a historical report (last 12 months) of domains advertising on a specified keyword in google ads, optionally for a specific month ('yyyymm15') or the most recent period, returning raw csv-like data. | | `SEMRUSH_ORGANIC_RESULTS` | Get organic results | Retrieves up to 100,000 domains and urls from google's top 100 organic search results for a keyword and region, returning a raw string; use `display date` in 'yyyymm15' format (day must be '15') for historical data. | | `SEMRUSH_PAID_RESULTS` | Get paid search results | Fetches domains ranking in google's paid search results (adwords) for a specified keyword and regional database. | | `SEMRUSH_PHRASE_QUESTIONS` | Phrase questions | Fetches question-format keywords semantically related to a given query phrase for a specified regional database, aiding in understanding user search intent and discovering content ideas. | | `SEMRUSH_PLA_COMPETITORS` | Get PLA competitors | Retrieves domains competing with a specified domain in google's product listing ads (pla) from a given semrush regional database. | | `SEMRUSH_PLA_COPIES` | Get PLA copies | Fetches product listing ad (pla) copies that semrush observed for a domain in google's paid search results. | | `SEMRUSH_REFERRING_DOMAINS` | Get referring domains | Retrieves a report as a text string (e.g., csv) listing domains that link to a target, with options to filter by type (not value). | | `SEMRUSH_REFERRING_DOMAINS_BY_COUNTRY` | Get referring domains by country | Generates a csv report detailing the geographic distribution of referring domains (by country, determined via ip address) for a specified, publicly accessible target. | | `SEMRUSH_REFERRING_I_PS` | Referring i ps | Fetches ip addresses that are sources of backlinks for a specified target domain, root domain, or url. | | `SEMRUSH_RELATED_KEYWORDS` | Find related keywords | Call this to find related keywords (including synonyms and variations) for a target phrase in a specific regional database; `display date` (if used for historical data) must be 'yyyymm15' for a past month. | | `SEMRUSH_TLD_DISTRIBUTION` | Get TLD distribution | Fetches a report on the top-level domain (tld) distribution of referring domains for a specified target, useful for analyzing geographic or categorical backlink diversity. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Semrush MCP server is an implementation of the Model Context Protocol that connects your AI agent to Semrush. It provides structured and secure access so your agent can perform Semrush 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 Semrush 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 Semrush-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: ["semrush"], }); 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 Semrush 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 semrush, 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 Semrush 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: ["semrush"], }); 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 semrush, 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 Semrush 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 Semrush MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/semrush/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/semrush/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/semrush/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/semrush/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/semrush/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/semrush/framework/codex) - [Cursor](https://composio.dev/toolkits/semrush/framework/cursor) - [VS Code](https://composio.dev/toolkits/semrush/framework/vscode) - [OpenCode](https://composio.dev/toolkits/semrush/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/semrush/framework/openclaw) - [Hermes](https://composio.dev/toolkits/semrush/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/semrush/framework/cli) - [Google ADK](https://composio.dev/toolkits/semrush/framework/google-adk) - [LangChain](https://composio.dev/toolkits/semrush/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/semrush/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/semrush/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/semrush/framework/crew-ai) ## Related Toolkits - [Metaads](https://composio.dev/toolkits/metaads) - Metaads is Meta's official Ads API that lets you manage, analyze, and optimize your Facebook and Instagram ad campaigns. Streamline ad operations and gain deeper insights with robust automation. - [Adrapid](https://composio.dev/toolkits/adrapid) - Adrapid is a platform for rapid creation of digital marketing visuals using templates. It streamlines design workflows for banners, images, and HTML5 content with automation. - [Adyntel](https://composio.dev/toolkits/adyntel) - Adyntel is an API that retrieves LinkedIn ads for any company using a domain or LinkedIn Page ID. Easily access competitive ad intelligence to power your marketing workflows. - [Beaconstac](https://composio.dev/toolkits/beaconstac) - Beaconstac is a platform for creating and managing QR codes and proximity beacons. It helps businesses engage customers and track marketing performance with powerful analytics. - [Campaign cleaner](https://composio.dev/toolkits/campaign_cleaner) - Campaign cleaner is an email campaign optimization tool that boosts compatibility and deliverability across email clients. It helps marketers get better results by cleaning, enhancing, and ensuring high performance for every campaign. - [Deadline funnel](https://composio.dev/toolkits/deadline_funnel) - Deadline Funnel lets you create personalized deadlines and timers for your marketing campaigns. It helps marketers boost conversions by adding authentic urgency to offers. - [Google Ads](https://composio.dev/toolkits/googleads) - Google Ads is Google's online advertising platform for creating, managing, and optimizing digital campaigns. It helps businesses reach targeted customers and maximize return on ad spend. - [Instantly](https://composio.dev/toolkits/instantly) - Instantly is a platform for automating cold email outreach, managing leads, and optimizing deliverability. Get better results from email campaigns with minimal manual effort. - [Proofly](https://composio.dev/toolkits/proofly) - Proofly is a social proof platform that displays real-time notifications of customer activity on your site. It helps you increase website conversions by building trust and urgency for visitors. - [Segmetrics](https://composio.dev/toolkits/segmetrics) - Segmetrics is a marketing analytics platform that reveals detailed insights into your customer journeys. It helps businesses optimize marketing strategies with accurate, actionable reporting. - [Sendloop](https://composio.dev/toolkits/sendloop) - Sendloop is an all-in-one email marketing platform built for SaaS, e-commerce, and small businesses. It makes it easy to send campaigns, manage lists, and track results—all in one place. - [Sidetracker](https://composio.dev/toolkits/sidetracker) - Sidetracker is a marketing analytics platform that tracks expenses, sales funnels, and customer journeys. It helps optimize marketing spend and visualize campaign performance from start to finish. - [Stannp](https://composio.dev/toolkits/stannp) - Stannp is an API-driven direct mail platform for sending postcards and letters programmatically. It lets you automate physical mail delivery—no manual printing or mailing required. - [Tapfiliate](https://composio.dev/toolkits/tapfiliate) - Tapfiliate is an affiliate and referral tracking platform for businesses. It helps companies efficiently manage, track, and grow their affiliate programs. - [Tpscheck](https://composio.dev/toolkits/tpscheck) - Tpscheck is a real-time service for verifying UK phone numbers against TPS and CTPS registers. It helps prevent unwanted marketing calls and ensures compliance with UK telemarketing laws. - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. - [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options. - [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices. - [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management. - [Twitter](https://composio.dev/toolkits/twitter) - Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Semrush MCP? With a standalone Semrush MCP server, the agents and LLMs can only access a fixed set of Semrush tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Semrush 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 Semrush tools. ### Can I manage the permissions and scopes for Semrush while using Tool Router? Yes, absolutely. You can configure which Semrush 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 Semrush data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)