# How to integrate Honeyhive MCP with Pydantic AI ```json { "title": "How to integrate Honeyhive MCP with Pydantic AI", "toolkit": "Honeyhive", "toolkit_slug": "honeyhive", "framework": "Pydantic AI", "framework_slug": "pydantic-ai", "url": "https://composio.dev/toolkits/honeyhive/framework/pydantic-ai", "markdown_url": "https://composio.dev/toolkits/honeyhive/framework/pydantic-ai.md", "updated_at": "2026-05-12T10:15:04.084Z" } ``` ## Introduction This guide walks you through connecting Honeyhive to Pydantic AI using the Composio tool router. By the end, you'll have a working Honeyhive agent that can add new datapoints to your evaluation dataset, list all datasets in your honeyhive project, log a batch of model events for analysis through natural language commands. This guide will help you understand how to give your Pydantic AI agent real control over a Honeyhive account through Composio's Honeyhive MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Honeyhive with - [OpenAI Agents SDK](https://composio.dev/toolkits/honeyhive/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/honeyhive/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/honeyhive/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/honeyhive/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/honeyhive/framework/codex) - [OpenClaw](https://composio.dev/toolkits/honeyhive/framework/openclaw) - [Hermes](https://composio.dev/toolkits/honeyhive/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/honeyhive/framework/cli) - [Google ADK](https://composio.dev/toolkits/honeyhive/framework/google-adk) - [LangChain](https://composio.dev/toolkits/honeyhive/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/honeyhive/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/honeyhive/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/honeyhive/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/honeyhive/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up your Composio API key and User ID - How to create a Composio Tool Router session for Honeyhive - How to attach an MCP Server to a Pydantic AI agent - How to stream responses and maintain chat history - How to build a simple REPL-style chat interface to test your Honeyhive workflows ## What is Pydantic AI? Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications. Key features include: - Type Safety: Built on Pydantic for automatic data validation - MCP Support: Native support for Model Context Protocol servers - Streaming: Built-in support for streaming responses - Async First: Designed for async/await patterns ## What is the Honeyhive MCP server, and what's possible with it? The Honeyhive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Honeyhive account. It provides structured and secure access to your AI observability platform, so your agent can perform actions like managing datasets, logging model and tool events, evaluating runs, and configuring project settings on your behalf. - Dataset management and organization: Create, retrieve, and delete datasets for your AI projects, helping you maintain organized and up-to-date evaluation data. - Efficient event logging: Log batches of model or external tool events, enabling comprehensive tracking and analysis of AI system interactions in real-time. - Data curation and cleanup: Add new datapoints to datasets or remove specific datapoints, ensuring your evaluation data remains accurate and relevant. - Streamlined evaluation workflows: Mark evaluation runs as completed and fetch project configuration details, making it easy to track progress and update run statuses automatically. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `HONEYHIVE_ADD_DATAPOINTS_TO_DATASET` | Add datapoints to dataset | Tool to add datapoints to a dataset. Use when you need to append multiple entries with specified input, ground truth, and history mappings. | | `HONEYHIVE_COMPARE_RUNS` | Compare Experiment Runs | Tool to retrieve experiment comparison between two evaluation runs. Use when you need to analyze the differences in metrics, datapoints, and events between two runs. | | `HONEYHIVE_COMPARE_RUNS_EVENTS` | Compare Runs Events | Tool to compare events between two experiment runs side-by-side. Use when analyzing differences in model behavior, performance metrics, or outputs between evaluation runs. Returns matched event pairs with their respective data from both runs for comparison. | | `HONEYHIVE_CREATE_BATCH_DATAPOINTS` | Batch Create Datapoints | Tool to create multiple datapoints in a single batch operation. Use when you need to bulk-import events into a dataset or create many datapoints at once. Supports filtering by date range, event IDs, or custom criteria. Efficient for migrating large numbers of events to evaluation datasets. | | `HONEYHIVE_CREATE_BATCH_MODEL_EVENTS` | Create Batch Model Events | Tool to create multiple model events in a single request. Use when you need to log a batch of event interactions to HoneyHive. | | `HONEYHIVE_CREATE_BATCH_TOOL_EVENTS` | Create Batch Tool Events | Tool to log a batch of external API calls as tool events. Use when you need to record multiple tool events in one request—use after gathering all event data. | | `HONEYHIVE_CREATE_CONFIGURATION` | Create Configuration | Creates a new configuration in HoneyHive for managing LLM or pipeline settings. Use this to define reusable configurations with specific models, prompts, and parameters that can be deployed across different environments (dev, staging, prod). Configurations enable version control and environment-specific management of your AI application settings. | | `HONEYHIVE_CREATE_DATAPOINT` | Create Datapoint | Tool to create a new datapoint with input-output pairs. Use when you need to add a single datapoint with inputs, ground truth, conversation history, and metadata. | | `HONEYHIVE_CREATE_DATASET` | Create Dataset | Tool to create a dataset. Use when you need to initialize a new dataset within a project. | | `HONEYHIVE_CREATE_EVENT` | Create Event | Tool to create a new event in HoneyHive to track execution of different parts of your application. Use when you need to log a model call, tool execution, or chain step. Events can be grouped into sessions and nested hierarchically using parent_id and children_ids. | | `HONEYHIVE_CREATE_METRIC` | Create Metric | Tool to create a new metric in HoneyHive. Use when you need to define how to evaluate model outputs, whether through code (PYTHON), AI evaluation (LLM), human review (HUMAN), or combining multiple metrics (COMPOSITE). Important: LLM metrics require both model_provider and model_name to be specified. | | `HONEYHIVE_CREATE_MODEL_EVENT` | Create Model Event | Tool to create a new model event to log LLM call data. Use when you need to track a single model interaction including messages, responses, usage, and metadata. | | `HONEYHIVE_CREATE_TOOL` | Create Tool | Creates a new tool definition in a HoneyHive project. Use this to register functions or plugins that can be invoked and tracked within HoneyHive. Tools are defined with a JSON Schema for their parameters, allowing HoneyHive to validate inputs and track tool usage in your AI workflows. Tool names must be unique within a project. | | `HONEYHIVE_DELETE_DATAPOINT` | Delete Datapoint | Tool to delete a specific datapoint by its ID. Use when you need to remove a datapoint from HoneyHive after confirming its identifier. | | `HONEYHIVE_DELETE_DATASET` | Delete Dataset | Tool to delete a dataset by ID. Use when you need to remove a dataset after confirming its ID. | | `HONEYHIVE_END_EVALUATION_RUN` | End Evaluation Run | Tool to update an evaluation run's status and metadata. Use to mark a run as completed after finishing evaluations, or update run properties like name, metadata, configuration, and associated event/datapoint IDs. | | `HONEYHIVE_GET_CONFIGURATIONS` | Get Configurations | Tool to retrieve a list of configurations. Use when you need to fetch all configurations for a specific project before making changes. | | `HONEYHIVE_GET_DATASETS` | Get Datasets | Retrieve datasets from HoneyHive for a specified project. Use this tool when you need to: - List all datasets within a project - Find datasets by type (evaluation or fine-tuning) - Retrieve a specific dataset by its ID Returns dataset details including name, description, datapoints count, type, and timestamps. | | `HONEYHIVE_GET_EVENTS` | Get Events | Tool to query events with filters and projections from HoneyHive. Use this action when you need to retrieve events with lightweight filtering (limit 1000 results). For bulk exports or more complex queries, use the Retrieve Events action instead. Supports filtering by date range, event properties, and field projections. | | `HONEYHIVE_GET_EVENTS_BY_SESSION_ID` | Get Events By Session ID | Tool to retrieve the complete tree of nested events for a specific session. Use when you need to analyze all events (model calls, tool calls, chains) that occurred within a session, including their hierarchical relationships, inputs, outputs, metrics, and costs. Returns a tree structure with recursive children. | | `HONEYHIVE_GET_EVENTS_CHART` | Get Events Chart | Tool to retrieve charting and analytics data for events over time. Use when you need aggregated metrics (duration, cost, token usage) grouped by time buckets or fields. Supports percentile analysis (p50, p95, p99) for latency monitoring and custom filters for targeted analytics. | | `HONEYHIVE_GET_METRICS` | Get Metrics | Retrieves all metrics associated with a HoneyHive project. Returns a list of metrics including their configuration (name, type, description, thresholds, evaluator details) and metadata (creation/update timestamps, sampling settings). Use this tool when you need to: - List all metrics configured for a project - Get metric IDs for updating metrics via HONEYHIVE_UPDATE_METRIC - Understand what evaluations are set up for a project Prerequisites: Obtain a valid project_name using HONEYHIVE_GET_PROJECTS first. | | `HONEYHIVE_GET_PROJECTS` | Get Projects | Tool to retrieve all projects in the HoneyHive account. Use when you need to list available projects, get project IDs for use in other API calls, or search for a specific project by name. | | `HONEYHIVE_GET_RUN` | Get Evaluation Run Details | Tool to get details of an evaluation run by its UUID. Use when you need to check the status, configuration, results, or metadata of a specific evaluation run. | | `HONEYHIVE_GET_RUN_METRICS` | Get Run Metrics | Tool to get event metrics for an experiment run. Use when you need to retrieve metrics computed on events within a specific experiment run. Returns an array of event objects with their associated metrics, which can be filtered by date range or custom filters. | | `HONEYHIVE_GET_RUNS` | Get Evaluation Runs | Tool to retrieve a list of evaluation runs from HoneyHive. Use when you need to: - List all evaluation runs for analysis - Find runs by status, name, or dataset - Get specific runs by their IDs - Paginate through large sets of evaluation runs Returns evaluation details including status, results, configuration, and timestamps. | | `HONEYHIVE_GET_RUNS_SCHEMA` | Get Runs Schema | Tool to retrieve the schema for experiment runs in HoneyHive. Use when you need to understand available fields, datasets, and mappings for experiment runs. | | `HONEYHIVE_GET_SESSION` | Get Session | Retrieve a complete session tree by session ID from HoneyHive. Use this tool to fetch the full session hierarchy including all nested events (model calls, tool calls, chains) with their inputs, outputs, durations, and metadata. Returns a recursive tree structure with aggregated metrics. Prerequisites: You need a valid session ID from HONEYHIVE_START_SESSION or HONEYHIVE_RETRIEVE_EVENTS. | | `HONEYHIVE_LIST_TOOLS` | List Tools | Tool to list all available Honeyhive tools. Use when you need to discover which functions or plugins are registered for use. | | `HONEYHIVE_RETRIEVE_DATAPOINT` | Retrieve Datapoint | Retrieve a specific datapoint by its ID from HoneyHive. Use this tool when you need the full details of a single datapoint, including its inputs, ground truth, conversation history, linked datasets, and metadata. Prerequisites: You need a valid datapoint ID. Get datapoint IDs from: - HONEYHIVE_RETRIEVE_DATAPOINTS (list datapoints by project/dataset) - HONEYHIVE_ADD_DATAPOINTS_TO_DATASET (returns IDs of newly created datapoints) | | `HONEYHIVE_RETRIEVE_DATAPOINTS` | Retrieve Datapoints | Retrieve datapoints from a HoneyHive project. Use this tool to fetch evaluation datapoints containing inputs, ground truth, and metadata. Supports filtering by specific datapoint IDs or dataset name. Commonly used to: - Review existing test cases before running evaluations - Export datapoints for analysis - Verify datapoint contents after adding them to a dataset | | `HONEYHIVE_RETRIEVE_EVENTS` | Retrieve Events | Retrieve and export events from a HoneyHive project. Use this tool to query traced events (model calls, tool calls, sessions, chains) with optional filters by event_type, metadata, feedback scores, or date range. Returns events with their inputs, outputs, duration, and metrics. Supports pagination for large result sets (max 7500 per page). | | `HONEYHIVE_RETRIEVE_EXPERIMENT_RESULT` | Retrieve Experiment Result | Tool to retrieve the result of a specific experiment run. Use when you need the status, metrics, and datapoint-level details of a completed experiment. | | `HONEYHIVE_START_EVALUATION_RUN` | Start Evaluation Run | Creates a new evaluation run to group and track multiple session events for analysis. Use this action when you want to: - Compare model performance across multiple sessions - Create evaluation batches for quality assurance - Link existing events to datasets for structured evaluation Prerequisites: - Get project ID using Get Projects action - Get event IDs from Start Session or Retrieve Events actions - (Optional) Get dataset ID from Get Datasets action | | `HONEYHIVE_START_SESSION` | Start Session | Start a new HoneyHive session for tracing and observability. Use this tool to initiate a tracking session that groups together related model, tool, and chain events. Returns a session_id that should be used to link subsequent events to this session. Common use cases: - Start tracing a user conversation - Begin logging an LLM pipeline execution - Initialize observability for a batch processing job | | `HONEYHIVE_UPDATE_CONFIGURATION` | Update Configuration | Tool to update an existing HoneyHive configuration. Use when you need to modify a configuration's name, provider, model parameters, environments, or other settings. You must provide the configuration ID (obtainable via Get Configurations action) and the name field. All other fields are optional and will only update if provided. | | `HONEYHIVE_UPDATE_DATAPOINT` | Update Datapoint | Update an existing datapoint by ID. Use this to modify any combination of inputs, ground_truth, history, metadata, linked_datasets, or linked_evals for a datapoint. Requires a valid datapoint ID obtained from retrieve_datapoints or add_datapoints_to_dataset. | | `HONEYHIVE_UPDATE_DATASET` | Update Dataset | Tool to update an existing dataset. Use when you need to modify a dataset's details (name, description, datapoints, linked evaluations, or metadata) after confirming its ID. | | `HONEYHIVE_UPDATE_EVENT` | Update Event | Update an existing HoneyHive event by ID. Use to attach feedback, metrics, metadata, outputs, config, user properties, or update duration on events created via start_session or batch event creation. At least one optional field must be provided alongside the event_id. | | `HONEYHIVE_UPDATE_METRIC` | Update Metric | Tool to update an existing metric. Use when you need to modify a metric’s properties after creation. Ensure you retrieve the metric first to verify its current state. | | `HONEYHIVE_UPDATE_PROJECT` | Update Project | Updates an existing HoneyHive project's name or description. Use this action to modify project metadata after creation. You must provide the project_id and at least one field to update (name or description). To find project IDs, use the Get Projects action first. | | `HONEYHIVE_UPDATE_TOOL` | Update Tool | Tool to update an existing tool in HoneyHive. Use when you need to modify a tool's name, description, parameters, or type after confirming its ID. At least one optional field must be provided alongside the required tool ID. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Honeyhive MCP server is an implementation of the Model Context Protocol that connects your AI agent to Honeyhive. It provides structured and secure access so your agent can perform Honeyhive 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: - Python 3.9 or higher - A Composio account with an active API key - Basic familiarity with Python and async programming ### 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). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install the required libraries. What's happening: - composio connects your agent to external SaaS tools like Honeyhive - pydantic-ai lets you create structured AI agents with tool support - python-dotenv loads your environment variables securely from a .env file ```bash pip install composio pydantic-ai python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your agent to Composio's API - USER_ID associates your session with your account for secure tool access - OPENAI_API_KEY to access OpenAI LLMs ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key ``` ### 4. Import dependencies What's happening: - We load environment variables and import required modules - Composio manages connections to Honeyhive - MCPServerStreamableHTTP connects to the Honeyhive MCP server endpoint - Agent from Pydantic AI lets you define and run the AI assistant ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from pydantic_ai import Agent from pydantic_ai.mcp import MCPServerStreamableHTTP load_dotenv() ``` ### 5. Create a Tool Router Session What's happening: - We're creating a Tool Router session that gives your agent access to Honeyhive tools - The create method takes the user ID and specifies which toolkits should be available - The returned session.mcp.url is the MCP server URL that your agent will use ```python async def main(): api_key = os.getenv("COMPOSIO_API_KEY") user_id = os.getenv("USER_ID") if not api_key or not user_id: raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment") # Create a Composio Tool Router session for Honeyhive composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["honeyhive"], ) url = session.mcp.url if not url: raise ValueError("Composio session did not return an MCP URL") ``` ### 6. Initialize the Pydantic AI Agent What's happening: - The MCP client connects to the Honeyhive endpoint - The agent uses GPT-5 to interpret user commands and perform Honeyhive operations - The instructions field defines the agent's role and behavior ```python # Attach the MCP server to a Pydantic AI Agent honeyhive_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[honeyhive_mcp], instructions=( "You are a Honeyhive assistant. Use Honeyhive tools to help users " "with their requests. Ask clarifying questions when needed." ), ) ``` ### 7. Build the chat interface What's happening: - The agent reads input from the terminal and streams its response - Honeyhive API calls happen automatically under the hood - The model keeps conversation history to maintain context across turns ```python # Simple REPL with message history history = [] print("Chat started! Type 'exit' or 'quit' to end.\n") print("Try asking the agent to help you with Honeyhive.\n") while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit", "bye"}: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n", flush=True) async with agent.run_stream(user_input, message_history=history) as stream_result: collected_text = "" async for chunk in stream_result.stream_output(): text_piece = None if isinstance(chunk, str): text_piece = chunk elif hasattr(chunk, "delta") and isinstance(chunk.delta, str): text_piece = chunk.delta elif hasattr(chunk, "text"): text_piece = chunk.text if text_piece: collected_text += text_piece result = stream_result print(f"Agent: {collected_text}\n") history = result.all_messages() ``` ### 8. Run the application What's happening: - The asyncio loop launches the agent and keeps it running until you exit ```python if __name__ == "__main__": asyncio.run(main()) ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from pydantic_ai import Agent from pydantic_ai.mcp import MCPServerStreamableHTTP load_dotenv() async def main(): api_key = os.getenv("COMPOSIO_API_KEY") user_id = os.getenv("USER_ID") if not api_key or not user_id: raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment") # Create a Composio Tool Router session for Honeyhive composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["honeyhive"], ) url = session.mcp.url if not url: raise ValueError("Composio session did not return an MCP URL") # Attach the MCP server to a Pydantic AI Agent honeyhive_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[honeyhive_mcp], instructions=( "You are a Honeyhive assistant. Use Honeyhive tools to help users " "with their requests. Ask clarifying questions when needed." ), ) # Simple REPL with message history history = [] print("Chat started! Type 'exit' or 'quit' to end.\n") print("Try asking the agent to help you with Honeyhive.\n") while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit", "bye"}: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n", flush=True) async with agent.run_stream(user_input, message_history=history) as stream_result: collected_text = "" async for chunk in stream_result.stream_output(): text_piece = None if isinstance(chunk, str): text_piece = chunk elif hasattr(chunk, "delta") and isinstance(chunk.delta, str): text_piece = chunk.delta elif hasattr(chunk, "text"): text_piece = chunk.text if text_piece: collected_text += text_piece result = stream_result print(f"Agent: {collected_text}\n") history = result.all_messages() if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You've built a Pydantic AI agent that can interact with Honeyhive through Composio's Tool Router. With this setup, your agent can perform real Honeyhive actions through natural language. You can extend this further by: - Adding other toolkits like Gmail, HubSpot, or Salesforce - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Honeyhive for workflow automation) This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations. ## How to build Honeyhive MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/honeyhive/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/honeyhive/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/honeyhive/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/honeyhive/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/honeyhive/framework/codex) - [OpenClaw](https://composio.dev/toolkits/honeyhive/framework/openclaw) - [Hermes](https://composio.dev/toolkits/honeyhive/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/honeyhive/framework/cli) - [Google ADK](https://composio.dev/toolkits/honeyhive/framework/google-adk) - [LangChain](https://composio.dev/toolkits/honeyhive/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/honeyhive/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/honeyhive/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/honeyhive/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/honeyhive/framework/crew-ai) ## Related Toolkits - [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed. - [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service. - [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows. - [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow. - [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows. - [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application. - [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities. - [Anthropic administrator](https://composio.dev/toolkits/anthropic_administrator) - Anthropic administrator is an API for managing Anthropic organizational resources like members, workspaces, and API keys. It helps you automate admin tasks and streamline resource management across your Anthropic organization. - [Api labz](https://composio.dev/toolkits/api_labz) - Api labz is a platform offering a suite of AI-driven APIs and workflow tools. It helps developers automate tasks and build smarter, more efficient applications. - [Apipie ai](https://composio.dev/toolkits/apipie_ai) - Apipie ai is an AI model aggregator offering a single API for accessing top AI models from multiple providers. It helps developers build cost-efficient, latency-optimized AI solutions without juggling multiple integrations. - [Astica ai](https://composio.dev/toolkits/astica_ai) - Astica ai provides APIs for computer vision, NLP, and voice synthesis. Integrate advanced AI features into your app with a single API key. - [Bigml](https://composio.dev/toolkits/bigml) - BigML is a machine learning platform that lets you build, train, and deploy predictive models from your data. Its intuitive interface and robust API make machine learning accessible and efficient. - [Botbaba](https://composio.dev/toolkits/botbaba) - Botbaba is a platform for building, managing, and deploying conversational AI chatbots across messaging channels. It streamlines chatbot automation, making it easier to integrate AI into customer interactions. - [Botpress](https://composio.dev/toolkits/botpress) - Botpress is an open-source platform for building, deploying, and managing chatbots. It helps teams automate conversations and deliver rich, interactive messaging experiences. - [Chatbotkit](https://composio.dev/toolkits/chatbotkit) - Chatbotkit is a platform for building and managing AI-powered chatbots using robust APIs and SDKs. It lets you easily add conversational AI to your apps for better user engagement. - [Cody](https://composio.dev/toolkits/cody) - Cody is an AI assistant built for businesses, trained on your company's knowledge and data. It delivers instant answers and insights, tailored for your team. - [Context7 MCP](https://composio.dev/toolkits/context7_mcp) - Context7 MCP delivers live, version-specific code docs and examples right from the source. It helps developers and AI agents instantly retrieve authoritative programming info—no more out-of-date docs. - [Customgpt](https://composio.dev/toolkits/customgpt) - CustomGPT.ai lets you build and deploy chatbots tailored to your own data and business needs. Get precise and context-aware AI conversations without writing code. - [Datarobot](https://composio.dev/toolkits/datarobot) - Datarobot is a machine learning platform that automates model development, deployment, and monitoring. It empowers organizations to quickly gain predictive insights from large datasets. - [Deepgram](https://composio.dev/toolkits/deepgram) - Deepgram is an AI-powered speech recognition platform for accurate audio transcription and understanding. It enables fast, scalable speech-to-text with advanced audio intelligence features. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Honeyhive MCP? With a standalone Honeyhive MCP server, the agents and LLMs can only access a fixed set of Honeyhive tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Honeyhive and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Pydantic AI? Yes, you can. Pydantic 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 Honeyhive tools. ### Can I manage the permissions and scopes for Honeyhive while using Tool Router? Yes, absolutely. You can configure which Honeyhive 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 Honeyhive data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)