Register Claude as a Verified Cloudflare Bot

[a-maccormack]

Problem Statement

I've stumbled upon an issue where cloudflare blocked claude web connection to my mcp server and it turned out this was due to my organization having set the Block AI Bots domain rule.

Proposed Solution

This rule is definitely valuable and we wish to continue having it on, which is why it would be nice to have claude registered as a verified bot. More on this below:

https://developers.cloudflare.com/bots/concepts/bot/verified-bots/

Alternatives Considered

I searched on cloudflare to see if there is a claude verified bot configuration that I can use but this was not the case. For now, I've created a custom rule to filter out claude's traffic to my server so that it doesn't get blocked.

Area

Developer Experience

Priority

Medium - Would be helpful

Additional Context

#79

[kailana-esper]

Adding our team's experience here to support this request.

We use Claude daily for work, and one of our primary use cases is retrieving content from our own public Zendesk Help Center documentation via Claude-User. This is being blocked by Cloudflare's 'Block AI Bots' managed rule on Zendesk's infrastructure — meaning we can't use Claude to access our own public docs.

We've opened a support ticket with Zendesk and are looking for solutions, but the root fix needs to come from Anthropic's side.

The lack of Cloudflare Verified Bot status for Claude-User is particularly frustrating because it conflates user-directed content retrieval with training crawlers — these are meaningfully different use cases, and users shouldn't be penalized for the former. Anthropic's own documentation distinguishes between ClaudeBot, Claude-User, and Claude-SearchBot, but Cloudflare's blunt 'Block AI Bots' rule treats them all the same.

Hoping this gets prioritized. Happy to provide more detail on our use case if helpful.

[localden]

Thanks for the suggestion. Cloudflare bot verification is a broader effort that spans more than the MCP connector surface tracked in this repository, so we are not going to track it here. For server operators behind Cloudflare's bot protections, the workaround documented in #49 (allowlisting Claude's published outbound IP range and the Claude-User user agent) is the dependable path today. The published IP range is at https://platform.claude.com/docs/en/api/ip-addresses.