# How to integrate Leverly MCP with Pydantic AI ```json { "title": "How to integrate Leverly MCP with Pydantic AI", "toolkit": "Leverly", "toolkit_slug": "leverly", "framework": "Pydantic AI", "framework_slug": "pydantic-ai", "url": "https://composio.dev/toolkits/leverly/framework/pydantic-ai", "markdown_url": "https://composio.dev/toolkits/leverly/framework/pydantic-ai.md", "updated_at": "2026-05-06T08:18:29.872Z" } ``` ## Introduction This guide walks you through connecting Leverly to Pydantic AI using the Composio tool router. By the end, you'll have a working Leverly agent that can show all current ingestion reattempts, stop reattempts for a specific lead, list reattempts history for lead 1234 through natural language commands. This guide will help you understand how to give your Pydantic AI agent real control over a Leverly account through Composio's Leverly MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Leverly with - [OpenAI Agents SDK](https://composio.dev/toolkits/leverly/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/leverly/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/leverly/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/leverly/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/leverly/framework/codex) - [OpenClaw](https://composio.dev/toolkits/leverly/framework/openclaw) - [Hermes](https://composio.dev/toolkits/leverly/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/leverly/framework/cli) - [Google ADK](https://composio.dev/toolkits/leverly/framework/google-adk) - [LangChain](https://composio.dev/toolkits/leverly/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/leverly/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/leverly/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/leverly/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/leverly/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 Leverly - 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 Leverly 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 Leverly MCP server, and what's possible with it? The Leverly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Leverly account. It provides structured and secure access to your Leverly workflows, so your agent can perform actions like listing reattempt histories, stopping ongoing reattempts, and streamlining automation management on your behalf. - View reattempt history: Quickly ask your agent to retrieve a complete list of all ingestion reattempts for easy review and troubleshooting. - Stop ongoing reattempts: Direct your agent to halt any ongoing reattempts for specific leads by providing the relevant reattempt ID. - Monitor workflow automation: Let your agent inspect and keep tabs on the status of automated processes, ensuring nothing falls through the cracks. - Accelerate process interventions: Empower your agent to step in and manage exceptions or stuck workflows by stopping unnecessary retries as needed. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `LEVERLY_LIST_REATTEMPTS` | List Reattempts | Tool to list all reattempts in leverly. use when you need to inspect the history of ingestion reattempts before taking further action. | | `LEVERLY_STOP_REATTEMPTS` | Stop Leverly Reattempts | Tool to stop ongoing reattempts for a lead in leverly. use when you need to halt retries for a given reattempt id. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Leverly MCP server is an implementation of the Model Context Protocol that connects your AI agent to Leverly. It provides structured and secure access so your agent can perform Leverly 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 Leverly - 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 Leverly - MCPServerStreamableHTTP connects to the Leverly 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 Leverly 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 Leverly composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["leverly"], ) 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 Leverly endpoint - The agent uses GPT-5 to interpret user commands and perform Leverly operations - The instructions field defines the agent's role and behavior ```python # Attach the MCP server to a Pydantic AI Agent leverly_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[leverly_mcp], instructions=( "You are a Leverly assistant. Use Leverly 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 - Leverly 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 Leverly.\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 Leverly composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["leverly"], ) 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 leverly_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[leverly_mcp], instructions=( "You are a Leverly assistant. Use Leverly 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 Leverly.\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 Leverly through Composio's Tool Router. With this setup, your agent can perform real Leverly 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 + Leverly 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 Leverly MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/leverly/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/leverly/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/leverly/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/leverly/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/leverly/framework/codex) - [OpenClaw](https://composio.dev/toolkits/leverly/framework/openclaw) - [Hermes](https://composio.dev/toolkits/leverly/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/leverly/framework/cli) - [Google ADK](https://composio.dev/toolkits/leverly/framework/google-adk) - [LangChain](https://composio.dev/toolkits/leverly/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/leverly/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/leverly/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/leverly/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/leverly/framework/crew-ai) ## Related Toolkits - [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations. - [Basin](https://composio.dev/toolkits/basin) - Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code. - [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications. - [Conveyor](https://composio.dev/toolkits/conveyor) - Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews. - [Crowdin](https://composio.dev/toolkits/crowdin) - Crowdin is a localization management platform that streamlines translation workflows and collaboration. It helps teams centralize multilingual content, boost productivity, and automate translation processes. - [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. - [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way. - [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease. - [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration. - [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease. - [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease. - [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services. - [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows. - [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses. - [Hyperbrowser](https://composio.dev/toolkits/hyperbrowser) - Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale. - [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals. - [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination. - [Make](https://composio.dev/toolkits/make) - Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code. - [Ntfy](https://composio.dev/toolkits/ntfy) - Ntfy is a notification service to send push messages to phones or desktops. Instantly deliver alerts and updates to users, devices, or teams. - [Persona](https://composio.dev/toolkits/persona) - Persona offers identity infrastructure to automate user verification and compliance. It helps organizations securely verify users and reduce fraud risk. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Leverly MCP? With a standalone Leverly MCP server, the agents and LLMs can only access a fixed set of Leverly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Leverly 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 Leverly tools. ### Can I manage the permissions and scopes for Leverly while using Tool Router? Yes, absolutely. You can configure which Leverly 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 Leverly data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)