# How to integrate Serphouse MCP with Mastra AI

```json
{
  "title": "How to integrate Serphouse MCP with Mastra AI",
  "toolkit": "Serphouse",
  "toolkit_slug": "serphouse",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/serphouse/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/serphouse/framework/mastra-ai.md",
  "updated_at": "2026-03-29T06:49:50.974Z"
}
```

## Introduction

This guide walks you through connecting Serphouse to Mastra AI using the Composio tool router. By the end, you'll have a working Serphouse agent that can get serp results for 'ai marketing tools', list top keywords for competitor domain, summarize ranking changes for your site through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Serphouse account through Composio's Serphouse MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Serphouse with

- [OpenAI Agents SDK](https://composio.dev/toolkits/serphouse/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/serphouse/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/serphouse/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/serphouse/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/serphouse/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/serphouse/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/serphouse/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/serphouse/framework/cli)
- [Google ADK](https://composio.dev/toolkits/serphouse/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/serphouse/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/serphouse/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/serphouse/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/serphouse/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 Serphouse tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Serphouse 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 Serphouse 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 Serphouse MCP server, and what's possible with it?

The Serphouse MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Serphouse account. It provides structured and secure access so your agent can perform Serphouse operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `SERPHOUSE_ACCOUNT_INFO` | Get Account Information | Tool to retrieve account information including active plan, credit usage, and account details. Use when you need to check account status, remaining credits, or active subscription plans. |
| `SERPHOUSE_DOMAIN_LIST` | Get Domain List | Tool to retrieve comprehensive list of search engine domains supported by the SERP API including Google, Bing, and Yahoo. Use when you need to know which domains are available for search queries. |
| `SERPHOUSE_GOOGLE_JOBS_SEARCH` | Google Jobs Search | Tool to perform real-time Google Jobs search to retrieve job listings. Use when you need to search for job postings on Google with specific query terms, location, and filters. |
| `SERPHOUSE_GOOGLE_SERP_ADVANCED_SCHEDULED` | Schedule Google SERP Advanced Search | Tool to schedule Google SERP scraping tasks that fetch up to 100 results by iterating through multiple result pages. Use when you need comprehensive search results beyond Google's 10-result limit. Credits are reserved upfront based on max_pages (1 page = 1 credit), with automatic refunds for unused pages. |
| `SERPHOUSE_GET_LANGUAGE_LIST` | Get Language List | Tool to retrieve full list of languages supported by Google, Bing, and Yahoo for SERP requests. Use when you need language codes for making SERP API requests or when configuring language-specific searches. |
| `SERPHOUSE_SEARCH_LOCATIONS` | Search Locations | Tool to search and retrieve available locations for SERP API from Google or Bing geographical targeting data. Use when you need to find valid location targets before making SERP API requests. |
| `SERPHOUSE_CHECK_SERP_TASK_STATUS` | Check SERP Task Status | Tool to check the status of a previously submitted SERP task. Use when monitoring task completion progress or verifying whether a SERP task has finished processing. |
| `SERPHOUSE_SERP_LIVE_SEARCH_GET` | SERP Live Search (GET) | Tool to execute real-time search requests and retrieve search engine results immediately via HTTP GET. Use when you need to perform searches on Google, Bing, or Yahoo and get instant SERP data. |
| `SERPHOUSE_EXECUTE_SERP_LIVE_POST_SEARCH` | Execute SERP Live POST Search | Tool to execute real-time search requests and retrieve search engine results immediately using HTTP POST method. Use when you need to get fresh SERP data from Google, Bing, or Yahoo with specific location and device targeting. Supports web, news, image, and shopping search types with advanced filtering options. |
| `SERPHOUSE_SCHEDULE_SERP_TASKS` | Schedule SERP Tasks | Tool to schedule SERP search tasks for asynchronous processing. Use when you need to queue multiple search tasks (up to 100 at once) for later execution. Results can be retrieved via webhook or polling. |
| `SERPHOUSE_GET_TRENDS_CATEGORIES_LIST` | Get Trends Categories List | Tool to retrieve the full list of categories and subcategories for Google Trends searches. Use when you need category IDs for filtering trends analysis. |
| `SERPHOUSE_CHECK_TREND_SEARCH_STATUS` | Check Trend Search Status | Tool to check the status of a previously submitted trend search task. Use when you need to monitor completion progress of a trend search. |
| `SERPHOUSE_GET_TRENDS_COUNTRY_LIST` | Get Trends Country List | Tool to retrieve the full list of countries and states for Google Trends searches. Use when you need geographic targeting options for trends analysis. |
| `SERPHOUSE_GET_TREND_SEARCH_RESULTS` | Get Trend Search Results | Tool to retrieve the results of a completed trend search query. Use when you need to fetch trend data for a specific task ID that was previously submitted. The task must be completed before results are available. |
| `SERPHOUSE_GET_TRENDS_LANGUAGE_LIST` | Get Trends Language List | Tool to retrieve the full list of supported languages for Google Trends searches. Use when you need to identify valid language codes for trend search requests. |
| `SERPHOUSE_SCHEDULE_GOOGLE_TRENDS_SEARCH` | Schedule Google Trends Search | Tool to schedule Google Trends search tasks with configuration for keywords, time ranges, and geographic locations. Use when you need to collect Google Trends data for specific keywords, time periods, or regions. Supports batch processing of up to 100 tasks. |
| `SERPHOUSE_PERFORM_GOOGLE_TRENDS_SEARCH` | Perform Google Trends Search | Tool to perform real-time Google Trends search to retrieve trend data for specified keywords. Use when you need to analyze keyword popularity across time periods and geographic locations. |
| `SERPHOUSE_GET_TRENDS_TIMEZONE_LIST` | Get Trends Timezone List | Tool to retrieve full list of timezones and offset values for use in Google Trend search requests. Use when you need timezone information for trend analysis or when configuring timezone-specific trend searches. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Serphouse MCP server is an implementation of the Model Context Protocol that connects your AI agent to Serphouse. It provides structured and secure access so your agent can perform Serphouse 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 Serphouse 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 Serphouse

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "serphouse" for Serphouse 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: ["serphouse"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Serphouse 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 Serphouse 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: "serphouse-mastra-agent",
    instructions: "You are an AI agent with Serphouse 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 Serphouse 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: {
        serphouse: 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: ["serphouse"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      serphouse: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "serphouse-mastra-agent",
    instructions: "You are an AI agent with Serphouse 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: { serphouse: 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 Serphouse 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 Serphouse MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/serphouse/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/serphouse/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/serphouse/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/serphouse/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/serphouse/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/serphouse/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/serphouse/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/serphouse/framework/cli)
- [Google ADK](https://composio.dev/toolkits/serphouse/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/serphouse/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/serphouse/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/serphouse/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/serphouse/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.
- [Exa](https://composio.dev/toolkits/exa) - Exa is a data extraction and search platform for gathering and analyzing information from websites, APIs, or databases. It helps teams quickly surface insights and automate data-driven workflows.
- [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.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Serphouse MCP?

With a standalone Serphouse MCP server, the agents and LLMs can only access a fixed set of Serphouse tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Serphouse 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 Serphouse tools.

### Can I manage the permissions and scopes for Serphouse while using Tool Router?

Yes, absolutely. You can configure which Serphouse 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 Serphouse data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)