# How to integrate Ritekit MCP with Mastra AI ```json { "title": "How to integrate Ritekit MCP with Mastra AI", "toolkit": "Ritekit", "toolkit_slug": "ritekit", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/ritekit/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/ritekit/framework/mastra-ai.md", "updated_at": "2026-05-12T10:24:14.621Z" } ``` ## Introduction This guide walks you through connecting Ritekit to Mastra AI using the Composio tool router. By the end, you'll have a working Ritekit agent that can suggest hashtags for your blog post draft, check if these instagram hashtags are banned, analyze hashtag stats for marketing campaign through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Ritekit account through Composio's Ritekit MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Ritekit with - [OpenAI Agents SDK](https://composio.dev/toolkits/ritekit/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ritekit/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ritekit/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ritekit/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ritekit/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ritekit/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ritekit/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ritekit/framework/cli) - [Google ADK](https://composio.dev/toolkits/ritekit/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ritekit/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ritekit/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/ritekit/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ritekit/framework/crew-ai) ## 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 Ritekit tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Ritekit 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 Ritekit 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 Ritekit MCP server, and what's possible with it? The Ritekit MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ritekit account. It provides structured and secure access to Ritekit’s social media optimization tools, so your agent can generate hashtags, analyze links, validate email addresses, and boost content engagement automatically on your behalf. - Smart hashtag generation and suggestions: Instantly get relevant and trending hashtags for any post or campaign to maximize visibility and reach. - Banned hashtag detection for Instagram: Automatically filter out banned or unsafe hashtags before publishing to keep your posts compliant and effective. - Comprehensive hashtag analytics: Retrieve real-time engagement stats on up to 100 hashtags, including metrics like tweets, retweets, exposure, and popularity grades. - Email address validation: Have your agent detect disposable or free email addresses to improve lead quality and reduce spam signups. - Link ad management: Enable deletion of link ads directly through your agent to keep your promotional content up to date and relevant. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `RITEKIT_AUTO_HASHTAG` | Auto Hashtag | Tool to automatically add relevant hashtags to a given post. Use when you have plain text and need suggested hashtags appended or inserted in context. | | `RITEKIT_BANNED_INSTAGRAM_HASHTAGS` | Check Banned Instagram Hashtags | Tool to identify which hashtags are banned on Instagram. Use when preparing content and need to filter out banned hashtags before posting. | | `RITEKIT_DETECT_DISPOSABLE_EMAIL` | Detect Disposable Email | Tool to detect if an email address is disposable. Use when validating email addresses to filter out temporary or fake email services. | | `RITEKIT_DETECT_EMAIL_TYPO` | Detect Email Typo | Tool to detect common typos in email addresses and suggest corrections. Use when validating email input to help users correct mistakes like gml.com -> gmail.com. | | `RITEKIT_FREEMAIL_DETECTION` | Free Email Detection | Tool to detect whether an email address belongs to a free email provider. Use when validating lead quality before ingestion. | | `RITEKIT_GET_ACCESS_TOKEN` | Get Access Token | Tool to obtain a RiteKit access token. Prefer using a stored token from connection metadata or request. Falls back to OAuth2 client credentials if both client_id and client_secret are provided and no token is otherwise available. | | `RITEKIT_GET_CLIENT_ID` | RiteKit Get Client ID | Tool to retrieve stored RiteKit client_id. Use when child actions require the client_id query parameter. | | `RITEKIT_GET_CLIENT_SECRET` | RiteKit Get Client Secret | Tool to retrieve stored RiteKit client_secret. Use when child actions require the client_secret parameter. | | `RITEKIT_GET_FULL_EMAIL_INSIGHTS` | Get Full Email Insights | Tool to retrieve comprehensive email address insights including full name, free mail detection, business email detection, and typo suggestions. Use when you need detailed analysis of an email address for lead qualification or email validation. | | `RITEKIT_HASHTAG_SUGGESTIONS` | RiteKit Hashtag Suggestions | Tool to get hashtag suggestions for a given text. Use when you need relevant hashtags for social media posts. | | `RITEKIT_LINK_AD_DELETE` | Delete Link Ad | Tool to delete a link ad. Use when you need to permanently remove a link ad by its ID. | | `RITEKIT_LIST_LINK_ADS` | List Link Ads | Tool to retrieve a list of link ads. Use after authenticating to fetch all link ads for the user. | | `RITEKIT_SHORTEN_LINK` | Shorten Link | Tool to shorten a URL with a specified CTA. Use when you need to generate a call-to-action-enabled short link. | | `RITEKIT_TEXT_TO_IMAGE` | Convert Text to Image | Tool to convert a quote into a styled image. Use after preparing quote text and style options. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Ritekit MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ritekit. It provides structured and secure access so your agent can perform Ritekit 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 Ritekit 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 Ritekit What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "ritekit" for Ritekit 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: ["ritekit"], }, ); const composioMCPUrl = session.mcp.url; console.log("Ritekit 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 Ritekit 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: "ritekit-mastra-agent", instructions: "You are an AI agent with Ritekit 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 Ritekit 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: { ritekit: 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: ["ritekit"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { ritekit: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "ritekit-mastra-agent", instructions: "You are an AI agent with Ritekit 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: { ritekit: 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 Ritekit 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 Ritekit MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/ritekit/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ritekit/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ritekit/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ritekit/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ritekit/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ritekit/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ritekit/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ritekit/framework/cli) - [Google ADK](https://composio.dev/toolkits/ritekit/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ritekit/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ritekit/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/ritekit/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ritekit/framework/crew-ai) ## Related Toolkits - [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing. - [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages. - [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections. - [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach. - [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease. - [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic. - [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns. - [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active. - [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place. - [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES. - [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere. - [Brevo](https://composio.dev/toolkits/brevo) - Brevo is an all-in-one email and SMS marketing platform for transactional messaging, automation, and CRM. It helps businesses engage customers and streamline communications through powerful campaign tools. - [Campayn](https://composio.dev/toolkits/campayn) - Campayn is an email marketing platform for creating, sending, and managing campaigns. It helps businesses engage contacts and grow audiences with easy-to-use tools. - [Cardly](https://composio.dev/toolkits/cardly) - Cardly is a platform for creating and sending personalized direct mail to customers. It helps businesses break through the digital clutter by getting real engagement via physical mailboxes. - [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management. - [Crustdata](https://composio.dev/toolkits/crustdata) - CrustData is an AI-powered data intelligence platform for real-time company and people data. It helps B2B sales teams, AI SDRs, and investors react to live business signals. - [Curated](https://composio.dev/toolkits/curated) - Curated is a platform for collecting, curating, and publishing newsletters. It streamlines content aggregation and distribution for creators and teams. - [Customerio](https://composio.dev/toolkits/customerio) - Customer.io is a customer engagement platform for targeted messaging across email, SMS, and push. Easily automate, segment, and track communications with your audience. - [Cutt ly](https://composio.dev/toolkits/cutt_ly) - Cutt.ly is a URL shortening service for managing and analyzing links. Streamline your workflows with quick, trackable, and branded short URLs. - [Demio](https://composio.dev/toolkits/demio) - Demio is webinar software built for marketers, offering both live and automated sessions with interactive features. It helps teams engage audiences and optimize lead generation through detailed analytics. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Ritekit MCP? With a standalone Ritekit MCP server, the agents and LLMs can only access a fixed set of Ritekit tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ritekit 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 Ritekit tools. ### Can I manage the permissions and scopes for Ritekit while using Tool Router? Yes, absolutely. You can configure which Ritekit 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 Ritekit data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)