# How to integrate Mx toolbox MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Mx toolbox MCP with OpenAI Agents SDK",
  "toolkit": "Mx toolbox",
  "toolkit_slug": "mx_toolbox",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/mx_toolbox/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/mx_toolbox/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:19:42.473Z"
}
```

## Introduction

This guide walks you through connecting Mx toolbox to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Mx toolbox agent that can check if your domain is blacklisted, get current mx records for example.com, run a ping test on our mail server through natural language commands.
This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Mx toolbox account through Composio's Mx toolbox MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Mx toolbox with

- [Claude Agent SDK](https://composio.dev/toolkits/mx_toolbox/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/mx_toolbox/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/mx_toolbox/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/mx_toolbox/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/mx_toolbox/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/mx_toolbox/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/mx_toolbox/framework/cli)
- [Google ADK](https://composio.dev/toolkits/mx_toolbox/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/mx_toolbox/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/mx_toolbox/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/mx_toolbox/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/mx_toolbox/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/mx_toolbox/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 Mx toolbox
- Configure an AI agent that can use Mx toolbox as a tool
- Run a live chat session where you can ask the agent to perform Mx toolbox 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 Mx toolbox MCP server, and what's possible with it?

The Mx toolbox MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mx toolbox account. It provides structured and secure access to network diagnostic and email health tools, so your agent can perform actions like DNS lookups, blacklist checks, email authentication analysis, and connectivity testing on your behalf.
- Automated DNS and MX record lookups: Instantly retrieve DNS, MX, DKIM, DMARC, and MTA-STS records for any domain to verify configuration and troubleshoot email delivery issues.
- Blacklist monitoring and alerting: Check if your domain or IP is listed on common blacklists, helping you stay ahead of email deliverability problems and security risks.
- Email authentication validation: Validate BIMI, DKIM, and DMARC records to ensure your domain's outgoing emails are properly authenticated and protected against spoofing.
- Network and SMTP diagnostics: Run ping, HTTP, and SMTP lookups to diagnose connectivity issues, measure latency, or assess mail server responsiveness—no manual testing required.
- Brand and security checks: Use BIMI and MTA-STS lookups to confirm your brand indicators and mail transport security policies are correctly published and compliant.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `MX_TOOLBOX_LOOKUP_BIMI_RECORD` | Lookup BIMI Record | Retrieves BIMI (Brand Indicators for Message Identification) record and diagnostic information for a domain. BIMI allows organizations to display verified logos in email clients. This tool checks: - Whether a BIMI record exists at default._bimi.{domain} - DMARC policy requirements (quarantine or reject needed for BIMI) - DNS resolution details and nameserver information - Related diagnostic checks and recommendations Returns comprehensive lookup data including passed/failed checks, DMARC records, DNS transcript, and related lookups. Use when verifying email branding configuration or troubleshooting BIMI implementation. |
| `MX_TOOLBOX_LOOKUP_BLACKLIST` | Lookup Blacklist | Tool to perform a blacklist check on a domain or IP. Use when you need to verify whether a domain or IP is listed in common blacklists. |
| `MX_TOOLBOX_LOOKUP_DKIM` | Lookup DKIM Record | Tool to retrieve DKIM (DomainKeys Identified Mail) records for a domain. DKIM is an email authentication method that helps prevent email spoofing by allowing the receiver to verify that an email was actually sent and authorized by the owner of that domain. Use this tool to verify DKIM configuration and troubleshoot email authentication issues. |
| `MX_TOOLBOX_LOOKUP_DMARC` | Lookup DMARC Record | Retrieves DMARC (Domain-based Message Authentication, Reporting & Conformance) records for a domain and performs validation checks. Returns detailed information about the DMARC record including policy settings (reject/quarantine/none), reporting addresses, alignment modes, and diagnostic check results. Useful for verifying email authentication configuration and troubleshooting email delivery issues. |
| `MX_TOOLBOX_LOOKUP_DNS` | Lookup DNS Records | Performs comprehensive DNS health check and retrieves name server records for a domain. Returns detailed diagnostics including: - Name server (NS) records with IP addresses, TTL, and status - DNS configuration health checks (warnings, errors, passed tests) - Query transcripts showing DNS resolution path - Related lookup suggestions (A, MX, SPF records) Use this to diagnose DNS issues, verify name server configurations, or check DNS propagation status. |
| `MX_TOOLBOX_LOOKUP_HTTP` | HTTP Lookup | Tool to perform an HTTP test on a domain. Use when you need to assess HTTP connectivity and status for a given domain. |
| `MX_TOOLBOX_LOOKUP_MTA_STS_RECORD` | Lookup MTA-STS Record | Tool to lookup MTA-STS record for a domain. Use when validating mail transport security policy. |
| `MX_TOOLBOX_LOOKUP_MX` | Lookup MX Records | Retrieves MX (Mail Exchange) records for a domain. Returns the mail servers responsible for receiving email for the domain, including their priority, hostname, IP address, and TTL. Use this to discover and verify email infrastructure for any domain. |
| `MX_TOOLBOX_LOOKUP_PING` | Ping Lookup | Performs a ping test to check network connectivity and measure round-trip time to a domain or IP address. Returns detailed ping statistics including response time, TTL (Time-To-Live), packet size, and ASN (Autonomous System Number) information. Useful for diagnosing network connectivity issues, measuring latency, and verifying host availability. |
| `MX_TOOLBOX_LOOKUP_SMTP` | SMTP Lookup | Tool to perform an SMTP connectivity test on a domain. Returns diagnostic results including connection status, DNS checks, TLS support, and other email deliverability indicators. Use when verifying SMTP server configuration or troubleshooting email delivery issues for a domain. |
| `MX_TOOLBOX_LOOKUP_SPF` | Lookup SPF Record | Tool to retrieve SPF records for a specified domain. Use when confirming email sender authorization policies. |
| `MX_TOOLBOX_MONITOR_STATUS` | Monitor Status | Retrieves the current status of all monitors configured in the MX Toolbox account. This action returns a list of all monitors with their health status, last check time, reputation scores, and any failing checks or warnings. Use this when you need to: - Check the overall health of all configured monitors - Get a comprehensive view of monitoring status across all services - Identify which monitors are failing or have warnings - Review when monitors were last checked No parameters are required - this action retrieves all monitors for the authenticated account. Returns an empty list if no monitors are configured. |
| `MX_TOOLBOX_USAGE_CHECK` | Check Usage | Retrieve API usage statistics for DNS and network lookups. Returns current request counts, maximum allowed requests, and any overage errors for both DNS lookups and network operations (HTTP, SMTP, Ping). |

## Supported Triggers

None listed.

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

The Mx toolbox MCP server is an implementation of the Model Context Protocol that connects your AI agent to Mx toolbox. It provides structured and secure access so your agent can perform Mx toolbox 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 Mx toolbox 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 Mx toolbox.
```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 mx_toolbox.
- The router checks the user's Mx toolbox connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Mx toolbox.
- This approach keeps things lightweight and lets the agent request Mx toolbox tools only when needed during the conversation.
```python
# Create a Mx toolbox Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["mx_toolbox"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Mx toolbox
const session = await composio.create(userId as string, {
  toolkits: ['mx_toolbox'],
});
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 Mx toolbox. "
        "Help users perform Mx toolbox 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 Mx toolbox. Help users perform Mx toolbox 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=["mx_toolbox"]
)
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 Mx toolbox. "
        "Help users perform Mx toolbox 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: ['mx_toolbox'],
  });
  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 Mx toolbox. Help users perform Mx toolbox 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 Mx toolbox MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Mx toolbox.
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 Mx toolbox MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/mx_toolbox/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/mx_toolbox/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/mx_toolbox/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/mx_toolbox/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/mx_toolbox/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/mx_toolbox/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/mx_toolbox/framework/cli)
- [Google ADK](https://composio.dev/toolkits/mx_toolbox/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/mx_toolbox/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/mx_toolbox/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/mx_toolbox/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/mx_toolbox/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/mx_toolbox/framework/crew-ai)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Mx toolbox MCP?

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

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

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

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