# How to integrate Serphouse MCP with OpenAI Agents SDK

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

## Introduction

This guide walks you through connecting Serphouse to the OpenAI Agents SDK 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 OpenAI Agents SDK 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

- [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)
- [Mastra AI](https://composio.dev/toolkits/serphouse/framework/mastra-ai)
- [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:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Serphouse
- Configure an AI agent that can use Serphouse as a tool
- Run a live chat session where you can ask the agent to perform Serphouse operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

## 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:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Serphouse project
- Some knowledge of Python or 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'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Serphouse.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only serphouse.
- The router checks the user's Serphouse connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Serphouse.
- This approach keeps things lightweight and lets the agent request Serphouse tools only when needed during the conversation.
```python
# Create a Serphouse Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["serphouse"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Serphouse
const session = await composio.create(userId as string, {
  toolkits: ['serphouse'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Serphouse. "
        "Help users perform Serphouse operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Serphouse. Help users perform Serphouse operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["serphouse"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Serphouse. "
        "Help users perform Serphouse operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['serphouse'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Serphouse. Help users perform Serphouse operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Serphouse MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Serphouse.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Serphouse MCP Agent with another framework

- [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)
- [Mastra AI](https://composio.dev/toolkits/serphouse/framework/mastra-ai)
- [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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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)
