From cloudflare-extended
Use this skill when the user asks to "manage tunnels", "create a Cloudflare Tunnel", "set up a tunnel", "list tunnels", "delete a tunnel", "configure tunnel ingress", "get tunnel token", "expose a local service", "run cloudflared", or any task involving Cloudflare Tunnel (formerly Argo Tunnel).
npx claudepluginhub pzharyuk/ai-claude-plugins --plugin cloudflare-extendedThis skill uses the workspace's default tool permissions.
Use the `cloudflare-extended` MCP server tools to create and manage Cloudflare Tunnels.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Use the cloudflare-extended MCP server tools to create and manage Cloudflare Tunnels.
A Cloudflare Tunnel creates an outbound-only connection from a server to Cloudflare's network, allowing you to expose internal services without opening inbound firewall ports. The cloudflared daemon runs on the origin server and maintains the connection.
Call cf_list_tunnels. Show name, ID, status, and active connections. Filter by name if the user specifies one.
homelab-web, office-api).cf_create_tunnel. A secret is auto-generated if not provided.cloudflared.Ingress rules map hostnames/paths to backend services. The last rule must be a catch-all.
cf_put_tunnel_config with the ingress array.<tunnel-id>.cfargotunnel.com — offer to create it using the DNS tools.Call cf_get_tunnel_token. The token is used to run cloudflared:
cloudflared tunnel run --token <TOKEN>
Or as a Docker container:
docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <TOKEN>
cf_delete_tunnel.See references/tunnel-ingress.md for full ingress configuration reference.
After creating a tunnel and configuring ingress, the user must create DNS records pointing their hostnames to the tunnel. For each hostname in the ingress rules:
hostname → <tunnel-id>.cfargotunnel.comtrueOffer to do this automatically using cf_create_dns_record.