# How to integrate Cloudflare api key MCP with Pydantic AI

```json
{
  "title": "How to integrate Cloudflare api key MCP with Pydantic AI",
  "toolkit": "Cloudflare api key",
  "toolkit_slug": "cloudflare_api_key",
  "framework": "Pydantic AI",
  "framework_slug": "pydantic-ai",
  "url": "https://composio.dev/toolkits/cloudflare_api_key/framework/pydantic-ai",
  "markdown_url": "https://composio.dev/toolkits/cloudflare_api_key/framework/pydantic-ai.md",
  "updated_at": "2026-05-12T10:06:43.088Z"
}
```

## Introduction

This guide walks you through connecting Cloudflare api key to Pydantic AI using the Composio tool router. By the end, you'll have a working Cloudflare api key agent that can add new a record to your dns zone, delete outdated cname record from domain, create lockdown rule for admin urls through natural language commands.
This guide will help you understand how to give your Pydantic AI agent real control over a Cloudflare api key account through Composio's Cloudflare api key MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Cloudflare api key with

- [ChatGPT](https://composio.dev/toolkits/cloudflare_api_key/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/cloudflare_api_key/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/cloudflare_api_key/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/cloudflare_api_key/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/cloudflare_api_key/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/cloudflare_api_key/framework/codex)
- [Cursor](https://composio.dev/toolkits/cloudflare_api_key/framework/cursor)
- [VS Code](https://composio.dev/toolkits/cloudflare_api_key/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/cloudflare_api_key/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/cloudflare_api_key/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/cloudflare_api_key/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/cloudflare_api_key/framework/cli)
- [Google ADK](https://composio.dev/toolkits/cloudflare_api_key/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/cloudflare_api_key/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/cloudflare_api_key/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/cloudflare_api_key/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/cloudflare_api_key/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/cloudflare_api_key/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 Cloudflare api key
- 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 Cloudflare api key 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 Cloudflare api key MCP server, and what's possible with it?

The Cloudflare api key MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Cloudflare account. It provides structured and secure access to your Cloudflare services, so your agent can create DNS records, manage security rules, delete zones, and automate zone configurations on your behalf.
- Automated DNS record management: Instantly create, update, or delete DNS records—including A, CNAME, TXT, and MX types—across your Cloudflare zones to keep your domains running smoothly.
- Zone lockdown and security automation: Add or remove Zone Lockdown rules to restrict access to specific URLs and IP ranges, helping you enforce security policies without manual intervention.
- Ruleset creation and maintenance: Direct your agent to create new rulesets or modify existing ones, ensuring your web applications remain secure and compliant with evolving access requirements.
- Comprehensive zone administration: Effortlessly delete entire zones or DNSSEC configurations for streamlined domain management and cleanup when needed.
- Versioned ruleset management: Retrieve specific versions of entry point rulesets, giving you granular control and auditability over your security configurations.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CLOUDFLARE_API_KEY_CREATE_DNS_RECORD` | Create DNS Record | Tool to create a new DNS record in a Cloudflare zone. Use when you need to add a record (A, CNAME, TXT, MX, etc.) to a specified zone. |
| `CLOUDFLARE_API_KEY_CREATE_LOCKDOWN_RULE` | Create Zone Lockdown Rule | Tool to create a Zone Lockdown rule. Use when you need to restrict access to specific URL patterns to defined IPs/CIDR ranges. Use after confirming zone_id. |
| `CLOUDFLARE_API_KEY_CREATE_RULE_IN_RULESET` | Create Rule in Ruleset | Tool to add a rule to an existing ruleset. Use when you need to append or insert a new rule in a Cloudflare ruleset. |
| `CLOUDFLARE_API_KEY_CREATE_RULESET` | Create Ruleset | Creates a new Cloudflare ruleset at account or zone scope. Rulesets contain rules that control traffic behavior (firewall, rate limiting, redirects, etc.). First use List Zones to get a zone_id, then specify the phase (e.g., 'http_request_firewall_custom' for WAF rules). |
| `CLOUDFLARE_API_KEY_DELETE_DNS_RECORD` | Delete DNS Record | Tool to delete a DNS record. Use when you need to remove a specific DNS record from a zone after confirming both zone and record IDs. |
| `CLOUDFLARE_API_KEY_DELETE_DNSSEC` | Delete DNSSEC | Tool to delete DNSSEC records for a zone. Use after disabling DNSSEC at the registrar to remove DNSSEC configuration. |
| `CLOUDFLARE_API_KEY_DELETE_RULE_FROM_RULESET` | Delete Rule from Ruleset | Tool to delete a specific rule from a ruleset. Use when you need to remove an outdated or incorrect rule from an account or zone ruleset after confirming IDs. |
| `CLOUDFLARE_API_KEY_DELETE_RULESET` | Delete Ruleset | Tool to delete all versions of a ruleset. Use when you need to remove a ruleset from an account or zone after confirming no references exist. |
| `CLOUDFLARE_API_KEY_DELETE_ZONE` | Delete a zone | Tool to delete an existing zone. Use after confirming the zone_id to permanently remove the zone. |
| `CLOUDFLARE_API_KEY_GET_CLOUDFLARE_IP_ADDRESSES` | Get Cloudflare IP Addresses | Tool to retrieve IP addresses used on the Cloudflare or JD Cloud network. Use when you need to obtain the list of IPv4 and IPv6 CIDR blocks used by Cloudflare's infrastructure or JD Cloud data centers. |
| `CLOUDFLARE_API_KEY_GET_ENTRYPOINT_RULESET_VERSION` | Get Entrypoint Ruleset Version | Retrieves a specific historical version of an entry point ruleset from Cloudflare. Entry point rulesets are phase-specific and define the rules that execute during a particular phase of request/response processing. This tool fetches a specific version, allowing you to view rules as they existed at a particular point in time. Use cases: - Audit historical rule configurations - Compare rule changes between versions - Rollback analysis (view what rules looked like before a change) - Debug issues by examining past ruleset states Prerequisites: - Requires a valid account_id or zone_id (use List Zones to get zone IDs) - Requires knowing the ruleset phase (e.g., 'http_request_firewall_custom') - Requires knowing the version number to fetch |
| `CLOUDFLARE_API_KEY_GET_LOCKDOWN_RULE` | Get Lockdown Rule | Tool to get a Zone Lockdown rule. Use when you need to fetch details of a specific lockdown rule by its ID within a Cloudflare zone. |
| `CLOUDFLARE_API_KEY_GET_REGIONAL_TIERED_CACHE` | Get Regional Tiered Cache | Tool to get the regional tiered cache setting for a zone. Use when you need to verify if regional tiered cache is enabled for performance optimization after zone activation. |
| `CLOUDFLARE_API_KEY_GET_RULESET` | Get Ruleset | Tool to fetch the latest version of a ruleset by ID. Use after you have the ruleset scope and ID. |
| `CLOUDFLARE_API_KEY_GET_ZONE_DETAILS` | Get Zone Details | Tool to get details for a specific zone. Use when you need detailed zone metadata by ID. |
| `CLOUDFLARE_API_KEY_LIST_DNS_RECORDS` | List DNS Records | List, search, sort, and filter DNS records for a Cloudflare zone. Use this tool to retrieve DNS records (A, AAAA, CNAME, TXT, MX, etc.) for a zone. Supports filtering by record type, name, content, and proxy status. Results are paginated; use page and per_page parameters for large record sets. Requires a valid zone_id which can be obtained from the List Zones action. |
| `CLOUDFLARE_API_KEY_LIST_ZONES` | List Cloudflare Zones | Tool to list, search, sort, and filter Cloudflare zones. Use when you need to retrieve a paginated list of zones available to the authenticated user. |
| `CLOUDFLARE_API_KEY_OVERWRITE_DNS_RECORD` | Overwrite DNS Record | Tool to completely overwrite a DNS record. Use when you need to replace all record details after confirming record type and name. |
| `CLOUDFLARE_API_KEY_RERUN_ZONE_ACTIVATION_CHECK` | Rerun Zone Activation Check | Triggers a new activation check for a zone with 'pending' status. Use this after creating a zone or updating nameservers to verify that DNS propagation is complete and the zone can be activated. Rate limits apply: once every 5 minutes for paid plans (paygo/Enterprise) or once per hour for Free plans. |
| `CLOUDFLARE_API_KEY_UPDATE_DNSSEC_STATUS` | Update DNSSEC Status | Tool to update DNSSEC configuration for a zone. Use when you need to enable or disable DNSSEC or adjust DNSSEC options after confirming the zone ID. |
| `CLOUDFLARE_API_KEY_UPDATE_LOCKDOWN_RULE` | Update Lockdown Rule | Tool to update a zone lockdown rule. Use when you need to modify the IP or URL settings of an existing Zone Lockdown rule after confirming the rule exists. |
| `CLOUDFLARE_API_KEY_UPDATE_RULE_IN_RULESET` | Update Rule in Ruleset | Tool to update a specific rule in a ruleset. Use when you need to modify a rule's configuration or reorder it after reviewing its current settings. |
| `CLOUDFLARE_API_KEY_UPDATE_RULESET` | Update Ruleset | Update a Cloudflare ruleset, creating a new version. Use this to modify ruleset description, name, or rules. IMPORTANT: When updating rules, you must include ALL rules you want to keep - any rules not included will be removed. Cannot modify managed rulesets directly - use overrides instead. |
| `CLOUDFLARE_API_KEY_UPDATE_ZONE` | Update Cloudflare Zone | Tool to edit a Cloudflare zone. Use when you need to update a single zone property at a time. Ensure only one of paused, type, or vanity_name_servers is provided per call. |
| `CLOUDFLARE_API_KEY_UPLOAD_FILE_TO_S3` | Upload File to S3 | Tool to upload arbitrary file content to temporary storage. Use when you need to stage files for actions requiring FileUploadable. |

## Supported Triggers

None listed.

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

The Cloudflare api key MCP server is an implementation of the Model Context Protocol that connects your AI agent to Cloudflare api key. It provides structured and secure access so your agent can perform Cloudflare api key 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 Cloudflare api key
- 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 Cloudflare api key
- MCPServerStreamableHTTP connects to the Cloudflare api key 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 Cloudflare api key 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 Cloudflare api key
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["cloudflare_api_key"],
    )
    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 Cloudflare api key endpoint
- The agent uses GPT-5 to interpret user commands and perform Cloudflare api key operations
- The instructions field defines the agent's role and behavior
```python
# Attach the MCP server to a Pydantic AI Agent
cloudflare_api_key_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[cloudflare_api_key_mcp],
    instructions=(
        "You are a Cloudflare api key assistant. Use Cloudflare api key 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
- Cloudflare api key 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 Cloudflare api key.\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 Cloudflare api key
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["cloudflare_api_key"],
    )
    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
    cloudflare_api_key_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[cloudflare_api_key_mcp],
        instructions=(
            "You are a Cloudflare api key assistant. Use Cloudflare api key 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 Cloudflare api key.\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 Cloudflare api key through Composio's Tool Router. With this setup, your agent can perform real Cloudflare api key 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 + Cloudflare api key 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 Cloudflare api key MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/cloudflare_api_key/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/cloudflare_api_key/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/cloudflare_api_key/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/cloudflare_api_key/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/cloudflare_api_key/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/cloudflare_api_key/framework/codex)
- [Cursor](https://composio.dev/toolkits/cloudflare_api_key/framework/cursor)
- [VS Code](https://composio.dev/toolkits/cloudflare_api_key/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/cloudflare_api_key/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/cloudflare_api_key/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/cloudflare_api_key/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/cloudflare_api_key/framework/cli)
- [Google ADK](https://composio.dev/toolkits/cloudflare_api_key/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/cloudflare_api_key/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/cloudflare_api_key/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/cloudflare_api_key/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/cloudflare_api_key/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/cloudflare_api_key/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 Cloudflare api key MCP?

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

### Can I manage the permissions and scopes for Cloudflare api key while using Tool Router?

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

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