# How to integrate Ambee MCP with Mastra AI ```json { "title": "How to integrate Ambee MCP with Mastra AI", "toolkit": "Ambee", "toolkit_slug": "ambee", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/ambee/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/ambee/framework/mastra-ai.md", "updated_at": "2026-05-12T10:01:03.541Z" } ``` ## Introduction This guide walks you through connecting Ambee to Mastra AI using the Composio tool router. By the end, you'll have a working Ambee agent that can show today's air quality for paris, get wildfire risk forecast for california, retrieve pollen count by your zip code through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Ambee account through Composio's Ambee MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Ambee with - [OpenAI Agents SDK](https://composio.dev/toolkits/ambee/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ambee/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ambee/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ambee/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ambee/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ambee/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ambee/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ambee/framework/cli) - [Google ADK](https://composio.dev/toolkits/ambee/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ambee/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ambee/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/ambee/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ambee/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 Ambee tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Ambee 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 Ambee 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 Ambee MCP server, and what's possible with it? The Ambee MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ambee account. It provides structured and secure access to hyperlocal environmental data, so your agent can perform actions like retrieving real-time air quality, fetching pollen and weather updates, forecasting wildfire risk, and monitoring natural disasters on your behalf. - Hyperlocal air quality monitoring: Instantly get real-time air quality data for any city, postal code, or precise geographic coordinates to stay informed about pollution and AQI levels in your area. - Air quality forecasting: Ask your agent to predict air quality trends up to 48 hours in advance for specific locations, helping you plan outdoor activities with health in mind. - Wildfire risk assessment: Access weekly wildfire risk forecasts for targeted places, so you can stay aware of environmental hazards before they happen. - Disaster and incident tracking: Retrieve the latest natural disaster data by continent, keeping you updated about major environmental events worldwide. - Geocoding and location resolution: Effortlessly transform city names or addresses into latitude and longitude coordinates, making location-based queries accurate and seamless for your agent. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `AMBEE_GEOCODE_BY_PLACE` | Geocode by Place | Tool to transform a place name or address into geographic coordinates. Use after confirming the location name to get precise latitude and longitude. | | `AMBEE_AMBEE_GET_AIR_QUALITY_BY_CITY` | Get Air Quality by City | Tool to retrieve real-time air quality data for a specific city. Use after obtaining a valid city name when current AQI and pollutant levels are needed. | | `AMBEE_GET_AIR_QUALITY_BY_COUNTRY_CODE` | Get Air Quality by Country Code | Tool to retrieve real-time air quality data for a specific country using a 3-letter ISO code. Use after acquiring the country code and when you want a national overview of air quality. | | `AMBEE_AMBEE_GET_AIR_QUALITY_BY_LAT_LNG` | Get Air Quality by Latitude and Longitude | Tool to retrieve real-time air quality data for a specific latitude and longitude. Use when you need hyper-local air quality readings for given coordinates. | | `AMBEE_GET_AIR_QUALITY_BY_POSTAL_CODE` | Get Air Quality by Postal Code | Retrieve real-time air quality data for a specific postal code and country. Returns comprehensive air quality metrics including pollutant concentrations (PM2.5, PM10, CO, NO2, O3, SO2), Air Quality Index (AQI) with category (Good/Moderate/Unhealthy), and location details. Data is updated hourly with 500-meter spatial resolution following US EPA standards. Use this when you need hyper-local air quality insights for a specific postal code. | | `AMBEE_AMBEE_GET_AIR_QUALITY_FORECAST_BY_LAT_LNG` | Get Air Quality Forecast by Latitude and Longitude | Tool to retrieve air quality forecast for a specific latitude and longitude. Use when you need predicted air quality data up to 48 hours in advance based on geographic coordinates. | | `AMBEE_GET_AIR_QUALITY_HISTORY_BY_LAT_LNG` | Get Air Quality History by Latitude and Longitude | Tool to retrieve historical air quality data for a specific latitude and longitude. Use when you need past air quality readings for given coordinates within the last 2 days. | | `AMBEE_GET_DISASTERS_BY_CONTINENT_LATEST` | Retrieve latest natural disasters by continent | Tool to retrieve latest natural disaster data for a specific continent. Use when you need up-to-date disaster information by continent code. | | `AMBEE_GET_DISASTERS_HISTORY` | Get historical natural disasters by date range | Tool to retrieve global historical natural disaster data with date range filtering. Use when you need to search disaster events from a specific starting date onwards. | | `AMBEE_GET_DISASTERS_HISTORY_BY_COUNTRY_CODE` | Get historical natural disasters by country code | Tool to retrieve historical natural disaster data for a country by ISO country code. Use when you need past disaster information for a specific country within a given date range. | | `AMBEE_GET_DISASTERS_HISTORY_BY_LAT_LNG` | Get historical natural disasters by coordinates | Tool to retrieve historical natural disaster data for a specific location by coordinates with date range. Use when you need historical disaster information for a geographic point within the past month. | | `AMBEE_GET_DISASTERS_LATEST_BY_COUNTRY_CODE` | Get latest disasters by country code | Tool to retrieve latest natural disaster data for a specific country using ISO country code. Use when you need up-to-date disaster information for a particular country. | | `AMBEE_GET_DISASTERS_LATEST_BY_LAT_LNG` | Get latest natural disasters by coordinates | Tool to retrieve latest natural disaster data (earthquakes, floods, droughts, volcanic eruptions) for a specific location using geographic coordinates. Use when you need up-to-date disaster information for a particular latitude and longitude. | | `AMBEE_GET_ELEVATION_BY_LAT_LNG` | Get Elevation by Latitude and Longitude | Tool to retrieve elevation statistics (min, max, mean) for a specific latitude and longitude. Use when you need geospatial elevation data for a location within North America. | | `AMBEE_GET_ELEVATION_BY_PLACE` | Get Elevation by Place | Retrieve elevation statistics (minimum, maximum, and mean) for a location by place name. Returns elevation data in meters above sea level. This endpoint has global coverage and is updated every 6 months. Use this when you have a place name (like "San Francisco, USA" or "Tokyo") and need detailed elevation information. | | `AMBEE_GET_FIRE_RISK_BY_LAT_LNG` | Get Fire Risk by Latitude and Longitude | Tool to retrieve fire risk forecast and Fire Weather Index (FWI) data for specific geographic coordinates. Use when you need weekly fire risk predictions for a location over the next four weeks based on latitude and longitude. | | `AMBEE_GET_ILI_FORECAST_BY_LAT_LNG` | Get ILI Forecast by Latitude and Longitude | Tool to retrieve up to 28-day forecast of Influenza-like Illness (ILI) risk using latitude and longitude. Use when you need daily ILI risk levels for a specific location, optionally including pollen and weather details. | | `AMBEE_GET_POLLEN_FORECAST_BY_PLACE` | Get Pollen Forecast by Place | Tool to retrieve 48-hour pollen forecast for a specific location by place name. Use when you need hourly pollen count predictions including grass, tree, and weed pollen levels with risk assessments. | | `AMBEE_GET_POLLEN_HISTORY_BY_PLACE` | Get Pollen History by Place | Tool to retrieve historical pollen data for a specific place name. Use after obtaining a valid place name and time range when historical pollen counts and risk levels are needed. | | `AMBEE_GET_POLLEN_LATEST_BY_LAT_LNG` | Get Latest Pollen Data by Latitude and Longitude | Tool to retrieve latest pollen data for a specific geographic location using latitude and longitude coordinates. Use when you need current pollen concentration levels and risk assessments for grass, tree, and weed pollen at a location. | | `AMBEE_GET_POLLEN_LATEST_BY_PLACE` | Get Latest Pollen by Place | Tool to retrieve latest pollen data for a specific place by name. Use when current pollen count and risk levels are needed for allergy awareness. | | `AMBEE_GET_WEATHER_FORECAST_BY_LAT_LNG` | Get Weather Forecast by Latitude and Longitude | Tool to retrieve weather forecast for a specific latitude and longitude (up to 72 hours). Use when you need predicted weather data based on geographic coordinates with customizable time intervals. | | `AMBEE_GET_WEATHER_LATEST_BY_LAT_LNG` | Get Current Weather by Latitude and Longitude | Tool to retrieve current weather data for a specific latitude and longitude, including temperature, pressure, humidity, and wind conditions. Use when you need real-time weather information for given coordinates. | | `AMBEE_GET_WILDFIRE_BY_LAT_LNG` | Get Wildfire Data by Latitude and Longitude | Retrieves real-time wildfire data for a specific geographic location using latitude and longitude coordinates. Returns nearby wildfire incidents including both detected fires (from satellite imagery) and reported fires (from official sources). Each record includes location, detection time, fire category, Fire Radiative Power (FRP), Fire Weather Index (FWI), and confidence level when available. Use this tool when you need to: - Monitor wildfire activity in a specific area - Get real-time fire detection data for coordinates - Check for fire hazards at a particular location - Filter fires by type (detected vs reported) The API returns fires within a radius of the specified coordinates. | | `AMBEE_GET_WILDFIRE_BY_PLACE` | Get Wildfire Data by Place | Retrieves real-time wildfire data for a specific location by place name. Returns wildfire incidents from the last 7 days including both satellite-detected fires and officially reported fires. Each record includes precise location coordinates, detection time, fire intensity metrics (FRP, FWI), fire category, and confidence level. Use this tool when you need to: - Check for active wildfires in a city, state, or country - Monitor fire activity in a specific geographic area - Get recent wildfire detection data without knowing exact coordinates - Filter fires by type (satellite-detected vs officially reported) The API searches within a geographic area around the place name provided. More specific locations (e.g., "San Francisco, CA") return more localized results than broad queries (e.g., "California"). | | `AMBEE_AMBEE_GET_WILDFIRE_RISK_FORECAST_BY_PLACE` | Get Wildfire Risk Forecast by Place | Tool to retrieve wildfire risk forecast for a specific place. Use when you need weekly wildfire risk predictions for a location over the next four weeks. | | `AMBEE_REVERSE_GEOCODE_BY_LAT_LNG` | Reverse Geocode by Latitude and Longitude | Tool to convert geographic coordinates into human-readable location data (address, place name, postal code). Use when you have latitude and longitude and need to get the corresponding address or location details. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Ambee MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ambee. It provides structured and secure access so your agent can perform Ambee 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 Ambee 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 Ambee What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "ambee" for Ambee 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: ["ambee"], }, ); const composioMCPUrl = session.mcp.url; console.log("Ambee 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 Ambee 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: "ambee-mastra-agent", instructions: "You are an AI agent with Ambee 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 Ambee 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: { ambee: 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: ["ambee"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { ambee: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "ambee-mastra-agent", instructions: "You are an AI agent with Ambee 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: { ambee: 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 Ambee 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 Ambee MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/ambee/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ambee/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ambee/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ambee/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ambee/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ambee/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ambee/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ambee/framework/cli) - [Google ADK](https://composio.dev/toolkits/ambee/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ambee/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ambee/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/ambee/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ambee/framework/crew-ai) ## Related Toolkits - [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management. - [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters. - [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations. - [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions. - [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations. - [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements. - [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints. - [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots. - [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches. - [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand. - [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance. - [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows. - [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses. - [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research. - [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction. - [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation. - [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation. - [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Ambee MCP? With a standalone Ambee MCP server, the agents and LLMs can only access a fixed set of Ambee tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ambee 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 Ambee tools. ### Can I manage the permissions and scopes for Ambee while using Tool Router? Yes, absolutely. You can configure which Ambee 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 Ambee data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)