SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Cloudflare browser rendering MCP with Claude Agent SDK

Connect Claude Agent SDK to Cloudflare browser rendering MCP. Capture a full-page screenshot of example.com, extract all product prices from a category page, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Cloudflare browser rendering logoCloudflare browser rendering
Api Key

Cloudflare Browser Rendering lets you programmatically control headless browsers running on Cloudflare’s global network. It’s perfect for automating web interactions, capturing screenshots, and extracting web data at scale.

4 Tools

Introduction

This guide walks you through connecting Cloudflare browser rendering to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Cloudflare browser rendering agent that can capture webpage screenshots, scrape HTML elements, and take page snapshots through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Cloudflare browser rendering account through Composio's Cloudflare browser rendering MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Cloudflare browser rendering with

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKCodexGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentPiDeepSeek HarnessGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Cloudflare browser rendering
  • Configure an AI agent that can use Cloudflare browser rendering as a tool
  • Run a live chat session where you can ask the agent to perform Cloudflare browser rendering operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Cloudflare browser rendering MCP server, and what's possible with it?

The Cloudflare browser rendering 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 browser rendering account. It provides structured and secure access to headless browser automation and rendering on Cloudflare’s global infrastructure, so your agent can capture screenshots, extract data, generate snapshots, and automate browser tasks on your behalf.

  • Automated webpage screenshot capture: Instantly instruct your agent to capture high-quality screenshots of any web page or HTML content with custom viewport and clipping options.
  • Combined DOM and visual snapshot generation: Direct your agent to create a full webpage snapshot with both the rendered HTML and an image, perfect for archiving or analysis.
  • Precise HTML element scraping: Ask your agent to extract specific text, HTML, attributes, or box metrics from rendered web pages using CSS selectors—ideal for detailed data collection or monitoring changes.
  • Account management automation: Enable your agent to fetch and manage all accessible Cloudflare accounts, making it easy to orchestrate browser rendering tasks across different environments.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Cloudflare browser rendering account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Cloudflare browser rendering functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Cloudflare browser rendering
  const session = await composio.create(USER_ID, {
    toolkits: ['cloudflare_browser_rendering'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Cloudflare browser rendering
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Cloudflare browser rendering tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Cloudflare browser rendering
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Cloudflare browser rendering and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['cloudflare_browser_rendering']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Cloudflare browser rendering tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Cloudflare browser rendering through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Cloudflare browser rendering action and event your agent gets out of the box.

Capture Screenshot

Tool to capture a webpage screenshot.

List Accounts

List Cloudflare accounts accessible to the authenticated API token, with optional name filtering and pagination.

Scrape HTML Elements

Tool to scrape HTML elements for text, HTML, attributes, and box metrics.

Take Webpage Snapshot

Capture both rendered HTML content and a screenshot of a webpage in a single request.

FRAMEWORKS

How to build Cloudflare browser rendering MCP Agent with another framework

Claude Code logo

Claude Code

Use Cloudflare browser rendering MCP with Claude Code

Cursor logo

Cursor

Use Cloudflare browser rendering MCP with Cursor

ChatGPT logo

ChatGPT

Use Cloudflare browser rendering MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Cloudflare browser rendering MCP with Claude Cowork

Antigravity logo

Antigravity

Use Cloudflare browser rendering MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Cloudflare browser rendering MCP with OpenAI Agents SDK

Codex logo

Codex

Use Cloudflare browser rendering MCP with Codex

Grok Build logo

Grok Build

Use Cloudflare browser rendering MCP with Grok Build

VS Code logo

VS Code

Use Cloudflare browser rendering MCP with VS Code

OpenCode logo

OpenCode

Use Cloudflare browser rendering MCP with OpenCode

OpenClaw logo

OpenClaw

Use Cloudflare browser rendering MCP with OpenClaw

Hermes logo

Hermes

Use Cloudflare browser rendering MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Cloudflare browser rendering MCP with Atomic Agent

Pi logo

Pi

Use Cloudflare browser rendering MCP with Pi

DeepSeek Harness logo

DeepSeek Harness

Use Cloudflare browser rendering MCP with DeepSeek Harness

Google ADK logo

Google ADK

Use Cloudflare browser rendering MCP with Google ADK

LangChain logo

LangChain

Use Cloudflare browser rendering MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Cloudflare browser rendering MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Cloudflare browser rendering MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Cloudflare browser rendering MCP with LlamaIndex

CrewAI logo

CrewAI

Use Cloudflare browser rendering MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Cloudflare browser rendering MCP with Pydantic AI

AutoGen logo

AutoGen

Use Cloudflare browser rendering MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Cloudflare browser rendering MCP server, the agents and LLMs can only access a fixed set of Cloudflare browser rendering tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Cloudflare browser rendering and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent 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 Cloudflare browser rendering tools.

Yes, absolutely. You can configure which Cloudflare browser rendering 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.

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 browser rendering data and credentials are handled as safely as possible.

Start with Cloudflare browser rendering.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Cloudflare browser rendering tool your agent needs.Free to start.

Start building