Connect Cloudflare to Copilot Studio
Search, read and write Cloudflare from Copilot Studio. Arlet links the two through one MCP connection and takes care of keys and authentication.
Arlet makes Cloudflare's official MCP server (Code Mode) available from the AI client you already use. Signing in and choosing the permissions to grant completes the connection.
This server covers the whole Cloudflare API. The AI first searches the API specification and docs to find the right endpoint, then calls it, which lets it operate DNS, Workers, R2, D1, KV and more within the permissions you granted.
How to connect Cloudflare to Copilot Studio
- 1
In the Arlet dashboard, open Integrations → Add an integration and choose Cloudflare. Sign in with Link Cloudflare, name the connection and click Create.
- 2
Sign in to Copilot Studio with your work account, create a new agent (or open an existing one), and in the Build tab choose Tools → + → Add → Model Context Protocol (MCP) in the right panel.
- 3
In the Add MCP server form, enter "Arlet" as the Server name, https://mcp.arlet.dev/mcp/ as the Server URL, choose OAuth 2.0 for Authentication and "Dynamic (detected)" for Configuration type, then click Add. No Client ID / Secret is needed.
- 4
On the Select a connection screen, choose Create new connection → Create, then sign in with Google on the Arlet authorization screen and click Allow. Click Add to attach the tool to the agent, then Publish to use it from Microsoft 365 Copilot.
Requires a Microsoft work account and a Copilot Studio license (or trial). MCP is available only for agents using generative orchestration and not in Copilot Studio in Teams.
What you can do
Cloudflare tools that Copilot Studio can call.
docsSearch Cloudflare's developer documentation.
searchQuery the Cloudflare API specification with JavaScript to find endpoints.
executeCall the discovered endpoints with JavaScript to run Cloudflare API requests.
The tool list follows what Cloudflare's official MCP server provides and may change.
Example uses
Review and change DNS
List a zone's records and add or change them as instructed.
Audit settings
Read cache and security settings through the API and tabulate them per zone.
Operate Workers, R2 and D1
List Workers and their deployments, and inspect R2 buckets and D1 databases.
Look it up, then do it
Check the procedure in the docs and apply the setting through the API in one go.
Prompts you can use as-is
- List the DNS records for example.com
- Add a TXT record _acme-challenge with value abc123 to example.com
- Tabulate the SSL mode and cache level for every zone I manage
- List my R2 buckets with their creation dates