Announcing Cloudflare Ambassadors, Community Engineers, and another $1M in open-source funding

Summary

Cloudflare introduced an updated community initiative featuring two tracks: Cloudflare Ambassadors and Cloudflare Community Engineers. The Ambassador program selects community leaders for terms lasting up to two years to organize events, lead student groups, and create learning spaces with company-provided credits, resources, and marketing assets. The Community Engineer track offers grants from a new one million dollar open-source fund spanning the next two years to support maintainers of projects such as Astro, Agents SDK, EmDash, Hono, and Vinext. To maintain its Discord server of nearly 100,000 members, a new Discord committee composed of staff and Ambassadors will guide community discussions while automated spam protections handle routine moderation.

Context

Developers, student leaders, and open-source contributors actively build tools and assist peers across Cloudflare's ecosystem, but community organizers often lack formal support, open-source maintainers require long-term funding stability, and rapid community growth in spaces like Discord creates administrative overhead.

Approach / What changed

Cloudflare launched two community tracks: Cloudflare Ambassadors to lead local events and peer education for terms up to two years, and Cloudflare Community Engineers to receive grants from an additional one million dollar open-source fund over two years. Additionally, Cloudflare formed a joint staff and ambassador Discord committee and implemented automated moderation tools to protect community channels.

Takeaways

• Cloudflare Ambassadors can serve terms of up to two years and receive credits, marketing assets, and technical resources to host meetups, workshops, hackathons, or student groups.
• The Cloudflare Community Engineer initiative provides grants from a new one million dollar fund over two years without term limits, initially focusing on developers around projects like Astro, Agents SDK, EmDash, Hono, and Vinext.
• A new Discord committee combining Cloudflare staff and Ambassadors will manage community engagement for nearly 100,000 members while automated anti-spam and link protection tools handle moderation.

Related reading

• Cloudflare · Aug 20, 2026

  From all-or-nothing to task-based OAuth consent

  Cloudflare introduced OAuth scope customization to replace all-or-nothing consent flows for third-party applications. Previously, users had to approve every requested scope or deny access completely, compelling developers of tools like MCP servers to construct custom pre-consent selection interfaces. With the new feature, developers can designate specific permissions as optional alongside required scopes when configuring an OAuth client. During authorization, users can deselect these optional scopes, while unrequested client scopes remain hidden to maintain task-specific consent screens. Because resulting access tokens contain only the granted subset of permissions, client applications must inspect returned scopes after code exchange rather than assuming full authorization.

  Miller Vargas

• Cloudflare · Aug 14, 2026

  Secure all your internal vibe-coded applications — in one click

  AI-assisted development enables employees to build applications rapidly, but unmanaged deployments can accidentally expose internal company data to the public Internet. Cloudflare introduced direct Cloudflare Access integration for Cloudflare Workers, allowing organizations to enforce authentication policies directly at the account or individual Worker level rather than per hostname. When enabled, incoming requests are authenticated before reaching application code across custom domains, routes, workers.dev subdomains, and preview environments. Developers can access authenticated identity data such as emails and groups directly via the Worker context object without manually validating JSON Web Tokens. This capability was implemented on Cloudflare's Rust-based FL2 proxy, which separated Worker routing from Worker execution so routing runs safely prior to Access policy enforcement.

  Chythra Malapati

• Cloudflare · Aug 6, 2026

  The next generation of MCP

  Model Context Protocol previously required stateful connections between clients and remote servers, creating operational complexity around sticky sessions, message replay, and open streams. The newly released MCP 2026-07-28 specification transitions MCP to a fully stateless protocol alongside updated SDKs across TypeScript, Python, Go, and C#. The protocol eliminates mandatory handshakes and session identifiers from core request paths while enabling servers to run on request-scoped infrastructure like Cloudflare Workers. Interactive elicitation is restructured through Multi Round-Trip Requests, which allow servers to return input requirements without sustaining persistent connections. Standardized headers for method names and improved OAuth authorization mechanisms further enable standard web infrastructure to inspect and manage MCP traffic efficiently.

  Matt Carey

• Cloudflare · Aug 7, 2026

  Unveiling good and bad behaviors on the Agentic Internet

  Web traffic increasingly shifts between human interaction and automated agents, rendering point-in-time security checks ineffective against sophisticated automation. Cloudflare addresses this shift through continuous behavioral analysis designed to evaluate trust across entire user sessions rather than relying on static point-in-time hurdles. Its CDN-injected client-side system, Precursor, tracks continuous behavioral indicators like cursor movements to catch mid-session automated takeovers. To counter rapid bot adaptation, Cloudflare is introducing self-adjusting machine learning models under Adaptive Intelligence and non-deterministic defenses such as the AI Labyrinth. These tools allow site owners to poison scraper training data, trap crawlers in synthetic webs, or queue legitimate agents while dynamically penalizing abusive traffic.

  Jin-Hee Lee