SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Cloudflare browser rendering MCP with LangChain

Connect LangChain 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 LangChain 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 LangChain 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 SDKClaude Agent SDKCodexGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentPiDeepSeek HarnessGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Cloudflare browser rendering project to Composio
  • Create a Tool Router MCP session for Cloudflare browser rendering
  • Initialize an MCP client and retrieve Cloudflare browser rendering tools
  • Build a LangChain agent that can interact with Cloudflare browser rendering
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • 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 @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Cloudflare browser rendering functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Cloudflare browser rendering tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['cloudflare_browser_rendering']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Cloudflare browser rendering 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
  • This approach allows the agent to dynamically load and use Cloudflare browser rendering tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "cloudflare_browser_rendering-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Cloudflare browser rendering MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Cloudflare browser rendering tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Cloudflare browser rendering related question or task to the agent.\n");

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

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['cloudflare_browser_rendering']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "cloudflare_browser_rendering-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Cloudflare browser rendering related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

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

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
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

Claude Agent SDK logo

Claude Agent SDK

Use Cloudflare browser rendering MCP with Claude Agent 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

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. LangChain 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