How to integrate Cloudflare browser rendering MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Cloudflare browser rendering logo
OpenCode logo
divider

How to integrate Cloudflare browser rendering MCP with OpenCode

This guide explains how to connect Cloudflare browser rendering MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Cloudflare browser rendering with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Cloudflare browser rendering with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Cloudflare browser rendering

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Cloudflare browser rendering Composio".
  3. Complete the authentication and authorization flow, and your Cloudflare browser rendering integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Cloudflare browser rendering to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Cloudflare browser rendering with OpenCode

Now, in the chat, ask the agent to connect to Cloudflare browser rendering or give it any Cloudflare browser rendering-related task.

For example, ask it to:

  • "Capture a full-page screenshot of example.com"
  • "Extract all product prices from a category page"
  • "Get the HTML and image of a login page"

It will prompt you to authenticate and authorize access to Cloudflare browser rendering.

That is it. Composio tools are now available in OpenCode, and your Cloudflare browser rendering account is ready to use.

Supported Tools & Triggers

Tools
Capture ScreenshotTool to capture a webpage screenshot.
List AccountsTool to list all Cloudflare accounts accessible.
Scrape HTML ElementsTool to scrape HTML elements for text, HTML, attributes, and box metrics.
Take Webpage SnapshotTool to capture rendered HTML and screenshot of a webpage.

Way Forward

Now that Cloudflare browser rendering is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Cloudflare browser rendering MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Cloudflare browser rendering MCP with ChatGPT

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

Claude Code logo

Claude Code

Use Cloudflare browser rendering MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Cloudflare browser rendering MCP with Claude Cowork

Codex logo

Codex

Use Cloudflare browser rendering MCP with Codex

Cursor logo

Cursor

Use Cloudflare browser rendering MCP with Cursor

OpenClaw logo

OpenClaw

Use Cloudflare browser rendering MCP with OpenClaw

Hermes logo

Hermes

Use Cloudflare browser rendering MCP with Hermes

CLI logo

CLI

Use Cloudflare browser rendering MCP with CLI

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

VS Code logo

VS Code

Use Cloudflare browser rendering MCP with VS Code

FAQ

What are the differences in Tool Router MCP and Cloudflare browser rendering MCP?

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.

Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode 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.

Can I manage the permissions and scopes for Cloudflare browser rendering while using Tool Router?

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.

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗