# How to integrate Exa MCP with Google ADK ```json { "title": "How to integrate Exa MCP with Google ADK", "toolkit": "Exa", "toolkit_slug": "exa", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/exa/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/exa/framework/google-adk.md", "updated_at": "2026-05-06T08:11:01.203Z" } ``` ## Introduction This guide walks you through connecting Exa to Google ADK using the Composio tool router. By the end, you'll have a working Exa agent that can summarize recent news articles on ai safety, find similar research papers to this url, create a webset for quarterly sales data through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Exa account through Composio's Exa MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Exa with - [OpenAI Agents SDK](https://composio.dev/toolkits/exa/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/exa/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/exa/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/exa/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/exa/framework/codex) - [OpenClaw](https://composio.dev/toolkits/exa/framework/openclaw) - [Hermes](https://composio.dev/toolkits/exa/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/exa/framework/cli) - [LangChain](https://composio.dev/toolkits/exa/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/exa/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/exa/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/exa/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/exa/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Exa account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Exa - Build an agent that connects to Exa through MCP - Interact with Exa using natural language ## What is Google ADK? Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol. Key features include: - Gemini Integration: Native support for Google's Gemini models - MCP Toolset: Built-in support for Model Context Protocol tools - Streamable HTTP: Connect to external services through streamable HTTP - CLI and Web UI: Run agents via command line or web interface ## What is the Exa MCP server, and what's possible with it? The Exa MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Exa account. It provides structured and secure access to your Exa data platform, so your agent can perform actions like extracting answers from web data, running semantic searches, managing imports, and automating monitoring across your datasets. - Citation-backed question answering: Have your agent generate direct, source-cited answers or detailed summaries for your research questions using Exa’s advanced search. - Semantic similarity search: Quickly find web pages or documents that are semantically related to a given URL, complete with highlights or summaries for context. - Data import and webset management: Let your agent create, configure, or delete imports and websets to streamline data gathering and enrichment workflows. - Automated data monitoring: Schedule and manage monitors for websets to keep your data fresh and up-to-date with minimal manual intervention. - Event tracking and retrieval: Access a full history of system events or fetch details for specific events to stay on top of activity within your Exa environment. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `EXA_ANSWER` | Generate an answer | Generates a direct, citation-backed answer to a clear natural language question or topic using exa's search, adept at both specific answers and detailed summaries for open-ended queries. | | `EXA_CREATE_IMPORT` | Create Import | Tool to create a new import to upload data into a webset. use when you need to initialize an import before uploading the data file. | | `EXA_CREATE_MONITOR` | Create a Monitor | Tool to create a new monitor. use when you need to schedule automated updates for a webset without manual runs. | | `EXA_CREATE_WEBSET` | Create Webset | Tool to create a new webset with search, import, and enrichment setup. use when you need to configure and seed a webset in one call. | | `EXA_DELETE_IMPORT` | Delete import | Tool to delete an existing import. use when you need to permanently remove an import by its id. | | `EXA_DELETE_WEBSET` | Delete webset | Tool to delete a webset. use after confirming the webset id to permanently remove the webset and all its items. | | `EXA_FIND_SIMILAR` | Find similar | Finds web pages semantically similar to a given url using embeddings-based search, optionally retrieving full text, highlights, or summaries for results. | | `EXA_GET_CONTENTS_ACTION` | Get contents from URLs or document IDs | Retrieves configurable text and highlights from a list of exa document ids or publicly accessible urls. | | `EXA_GET_EVENT` | Get Event | Tool to get details of a specific event by its id. use when you have an event id and need its full details. | | `EXA_LIST_EVENTS` | List events | Tool to list all events that have occurred in the system. use when you need to paginate through the event history. | | `EXA_LIST_IMPORTS` | List imports | Tool to list all imports for the webset. use when you need to paginate through and monitor import jobs. | | `EXA_LIST_WEBHOOKS` | List webhooks | Tool to list all webhooks for websets. use when you need to view existing webhooks and paginate through results. | | `EXA_SEARCH` | Search | Performs a web search using the exa engine, useful for queries requiring advanced filtering, specific content categories, or ai-optimized prompting. | | `EXA_UPDATE_IMPORT` | Update import | Tool to update an import configuration by id. use when you need to modify an import's title or metadata. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Exa MCP server is an implementation of the Model Context Protocol that connects your AI agent to Exa. It provides structured and secure access so your agent can perform Exa 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: - A Google API key for Gemini models - A Composio account and API key - Python 3.9 or later installed - Basic familiarity with Python ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key. - Copy the key and keep it safe. You will put this in GOOGLE_API_KEY. Composio API Key and User ID - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY. - Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Exa via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables Save all your credentials in the .env file. What's happening: - GOOGLE_API_KEY authenticates with Google's Gemini models - COMPOSIO_API_KEY authenticates with Composio - COMPOSIO_USER_ID identifies the user for session management ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate environment What's happening: - os reads environment variables - Composio is the main Composio SDK client - GoogleProvider declares that you are using Google ADK as the agent runtime - Agent is the Google ADK LLM agent class - McpToolset lets the ADK agent call MCP tools over HTTP ```python import os import warnings from composio import Composio from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") ``` ### 6. Create Composio client and Tool Router session What's happening: - Authenticates to Composio with your API key - Declares Google ADK as the provider - Spins up a short-lived MCP endpoint for your user and selected toolkit - Stores the MCP HTTP URL for the ADK MCP integration ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["exa"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent What's happening: - Connects the ADK agent to the Composio MCP endpoint through McpToolset - Uses Gemini as the model powering the agent - Lists exact tool names in instruction to reduce misnamed tool calls ```python composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Exa operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening: - adk run runs the agent in CLI mode - adk web . opens a web UI for interactive testing ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```python import os import warnings from composio import Composio from composio_google import GoogleProvider from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider()) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["exa"], ) COMPOSIO_MCP_URL = composio_session.mcp.url composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Exa operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Exa with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Exa using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Exa tools - Environment variables keep your credentials secure and separate from code - Clear agent instructions reduce tool calling errors - The ADK web UI provides an interactive interface for testing and development You can extend this setup by adding more toolkits to the toolkits array in your session configuration. ## How to build Exa MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/exa/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/exa/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/exa/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/exa/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/exa/framework/codex) - [OpenClaw](https://composio.dev/toolkits/exa/framework/openclaw) - [Hermes](https://composio.dev/toolkits/exa/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/exa/framework/cli) - [LangChain](https://composio.dev/toolkits/exa/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/exa/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/exa/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/exa/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/exa/framework/crew-ai) ## Related Toolkits - [Firecrawl](https://composio.dev/toolkits/firecrawl) - Firecrawl automates large-scale web crawling and data extraction. It helps organizations efficiently gather, index, and analyze content from online sources. - [Tavily](https://composio.dev/toolkits/tavily) - Tavily offers powerful search and data retrieval from documents, databases, and the web. It helps teams locate and filter information instantly, saving hours on research. - [Serpapi](https://composio.dev/toolkits/serpapi) - SerpApi is a real-time API for structured search engine results. It lets you automate SERP data collection, parsing, and analysis for SEO and research. - [Peopledatalabs](https://composio.dev/toolkits/peopledatalabs) - Peopledatalabs delivers B2B data enrichment and identity resolution APIs. Supercharge your apps with accurate, up-to-date business and contact data. - [Snowflake](https://composio.dev/toolkits/snowflake) - Snowflake is a cloud data warehouse built for elastic scaling, secure data sharing, and fast SQL analytics across major clouds. - [Posthog](https://composio.dev/toolkits/posthog) - PostHog is an open-source analytics platform for tracking user interactions and product metrics. It helps teams refine features, analyze funnels, and reduce churn with actionable insights. - [Amplitude](https://composio.dev/toolkits/amplitude) - Amplitude is a digital analytics platform for product and behavioral data insights. It helps teams analyze user journeys and make data-driven decisions quickly. - [Bright Data MCP](https://composio.dev/toolkits/brightdata_mcp) - Bright Data MCP is an AI-powered web scraping and data collection platform. Instantly access public web data in real time with advanced scraping tools. - [Browseai](https://composio.dev/toolkits/browseai) - Browseai is a web automation and data extraction platform that turns any website into an API. It's perfect for monitoring websites and retrieving structured data without manual scraping. - [ClickHouse](https://composio.dev/toolkits/clickhouse) - ClickHouse is an open-source, column-oriented database for real-time analytics and big data processing using SQL. Its lightning-fast query performance makes it ideal for handling large datasets and delivering instant insights. - [Coinmarketcal](https://composio.dev/toolkits/coinmarketcal) - CoinMarketCal is a community-powered crypto calendar for upcoming events, announcements, and releases. It helps traders track market-moving developments and stay ahead in the crypto space. - [Control d](https://composio.dev/toolkits/control_d) - Control d is a customizable DNS filtering and traffic redirection platform. It helps you manage internet access, enforce policies, and monitor usage across devices and networks. - [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights. - [Databricks](https://composio.dev/toolkits/databricks) - Databricks is a unified analytics platform for big data and AI on the lakehouse architecture. It empowers data teams to collaborate, analyze, and build scalable solutions efficiently. - [Datagma](https://composio.dev/toolkits/datagma) - Datagma delivers data intelligence and analytics for business growth and market discovery. Get actionable market insights and track competitors to inform your strategy. - [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment. - [Dovetail](https://composio.dev/toolkits/dovetail) - Dovetail is a research analysis platform for transcript review and insight generation. It helps teams code interviews, analyze feedback, and create actionable research summaries. - [Dub](https://composio.dev/toolkits/dub) - Dub is a short link management platform with analytics and API access. Use it to easily create, manage, and track branded short links for your business. - [Elasticsearch](https://composio.dev/toolkits/elasticsearch) - Elasticsearch is a distributed, RESTful search and analytics engine for all types of data. It delivers fast, scalable search and powerful analytics across massive datasets. - [Fireflies](https://composio.dev/toolkits/fireflies) - Fireflies.ai is an AI-powered meeting assistant that records, transcribes, and analyzes voice conversations. It helps teams capture call notes automatically and search or summarize meetings effortlessly. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Exa MCP? With a standalone Exa MCP server, the agents and LLMs can only access a fixed set of Exa tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Exa and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Google ADK? Yes, you can. Google ADK 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 Exa tools. ### Can I manage the permissions and scopes for Exa while using Tool Router? Yes, absolutely. You can configure which Exa 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 Exa data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)