# Cloudflare DNS Analytics MCP server
> Analyze DNS performance and inspect DNS settings for your Cloudflare zones and account.
- Listing: https://mcp.tc/i/cloudflare-dns-analytics
- Connect: use the server's own URL `https://dns-analytics.mcp.cloudflare.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: Cloudflare
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage:
- Repository:
## About
Connects to the Cloudflare DNS Analytics API so an assistant can list the zones in your account, fetch DNS reports for a zone over a chosen time frame, and read DNS settings at account and zone level. It helps with spotting high-traffic zones and debugging or tuning DNS configuration.
Runs as a hosted remote server at https://dns-analytics.mcp.cloudflare.com/mcp using streamable HTTP. You sign in with Cloudflare OAuth in the browser, and the tools become available after authorization. If your credentials reach several accounts, pass an account ID or set a cf-account-id header.
## What it can do
- List zones under the active Cloudflare account
- Fetch a DNS report for a zone over a time frame
- Show DNS settings for the account
- Show DNS settings for a specific zone
- Compare zones to find the one with the most traffic
## Example prompts
- "List zones under my Cloudflare account."
- "Show me the DNS report for example.com for the last 7 days."
- "What are the DNS settings for my account?"
- "Which of my zones has the highest traffic?"
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http cloudflare-dns-analytics https://dns-analytics.mcp.cloudflare.com/mcp
```
2. Start Claude Code, type `/mcp`, pick **cloudflare-dns-analytics** and choose **Authenticate**. A browser window opens for the Cloudflare sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Settings → Connectors** and click **Add custom connector**.
2. Name it **Cloudflare DNS Analytics** and paste this URL:
```url
https://dns-analytics.mcp.cloudflare.com/mcp
```
3. Click **Add**, then **Connect**, and sign in when Cloudflare asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://dns-analytics.mcp.cloudflare.com/mcp` and click **Add**.
3. Click **Connect** and sign in when Cloudflare asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.
2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.
3. Paste `https://dns-analytics.mcp.cloudflare.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Cloudflare to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"cloudflare-dns-analytics": {
"url": "https://dns-analytics.mcp.cloudflare.com/mcp"
}
}
}
```
Cursor shows **Needs login** next to the server. Click it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"cloudflare-dns-analytics","type":"http","url":"https://dns-analytics.mcp.cloudflare.com/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"cloudflare-dns-analytics": {
"type": "http",
"url": "https://dns-analytics.mcp.cloudflare.com/mcp"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"cloudflare-dns-analytics": {
"serverUrl": "https://dns-analytics.mcp.cloudflare.com/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add cloudflare-dns-analytics --url https://dns-analytics.mcp.cloudflare.com/mcp
codex mcp login cloudflare-dns-analytics
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.cloudflare-dns-analytics]
url = "https://dns-analytics.mcp.cloudflare.com/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http cloudflare-dns-analytics https://dns-analytics.mcp.cloudflare.com/mcp
```
Then, inside Gemini CLI, run `/mcp auth cloudflare-dns-analytics` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"cloudflare-dns-analytics": {
"type": "http",
"url": "https://dns-analytics.mcp.cloudflare.com/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://dns-analytics.mcp.cloudflare.com/mcp`.
## Details
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03
---
Source: https://mcp.tc/i/cloudflare-dns-analytics (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report