How to integrate Cloudflare api key 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 api key logo
OpenCode logo
divider

How to integrate Cloudflare api key MCP with OpenCode

This guide explains how to connect Cloudflare api key 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 api key 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 api key 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 api key

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 api key Composio".
  3. Complete the authentication and authorization flow, and your Cloudflare api key integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Cloudflare api key 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 api key with OpenCode

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

For example, ask it to:

  • "Add new A record to your DNS zone"
  • "Delete outdated CNAME record from domain"
  • "Create lockdown rule for admin URLs"

It will prompt you to authenticate and authorize access to Cloudflare api key.

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

Supported Tools & Triggers

Tools
Create DNS RecordTool to create a new DNS record in a Cloudflare zone.
Create Zone Lockdown RuleTool to create a Zone Lockdown rule.
Create Rule in RulesetTool to add a rule to an existing ruleset.
Create RulesetTool to create an account- or zone-scoped ruleset.
Delete DNS RecordTool to delete a DNS record.
Delete DNSSECTool to delete DNSSEC records for a zone.
Delete Rule from RulesetTool to delete a specific rule from a ruleset.
Delete RulesetTool to delete all versions of a ruleset.
Delete a zoneTool to delete an existing zone.
Get Entrypoint Ruleset VersionTool to get a specific version of an entry point ruleset.
Get Lockdown RuleTool to get a Zone Lockdown rule.
Get Regional Tiered CacheTool to get the regional tiered cache setting for a zone.
Get RulesetTool to fetch the latest version of a ruleset by ID.
Get Zone DetailsTool to get details for a specific zone.
List DNS RecordsTool to list DNS records for a given Cloudflare zone.
List Cloudflare ZonesTool to list, search, sort, and filter Cloudflare zones.
Overwrite DNS RecordTool to completely overwrite a DNS record.
Rerun Zone Activation CheckTool to trigger a new activation check for a PENDING zone.
Update DNSSEC StatusTool to update DNSSEC configuration for a zone.
Update Lockdown RuleTool to update a zone lockdown rule.
Update Rule in RulesetTool to update a specific rule in a ruleset.
Update RulesetTool to update a Cloudflare ruleset, creating a new version.
Update Cloudflare ZoneTool to edit a Cloudflare zone.
Upload File to S3Tool to upload arbitrary file content to the app’s temporary R2/S3 bucket.

Way Forward

Now that Cloudflare api key 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 api key MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Cloudflare api key MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Cloudflare api key MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Cloudflare api key MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Cloudflare api key MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Cloudflare api key MCP with Claude Cowork

Codex logo

Codex

Use Cloudflare api key MCP with Codex

Cursor logo

Cursor

Use Cloudflare api key MCP with Cursor

OpenClaw logo

OpenClaw

Use Cloudflare api key MCP with OpenClaw

Hermes logo

Hermes

Use Cloudflare api key MCP with Hermes

CLI logo

CLI

Use Cloudflare api key MCP with CLI

Google ADK logo

Google ADK

Use Cloudflare api key MCP with Google ADK

LangChain logo

LangChain

Use Cloudflare api key MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Cloudflare api key MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Cloudflare api key MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Cloudflare api key MCP with LlamaIndex

CrewAI logo

CrewAI

Use Cloudflare api key MCP with CrewAI

VS Code logo

VS Code

Use Cloudflare api key MCP with VS Code

FAQ

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

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↗