Skill

tunnel-management

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-extended

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use the `cloudflare-extended` MCP server tools to create and manage Cloudflare Tunnels.

Supporting Assets

references/tunnel-ingress.md

SKILL.md

Similar Skills

cache-components

139.3k

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.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Cloudflare Tunnel Management

Use the cloudflare-extended MCP server tools to create and manage Cloudflare Tunnels.

What is a Cloudflare Tunnel?

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.

Workflows

Listing tunnels

Call cf_list_tunnels. Show name, ID, status, and active connections. Filter by name if the user specifies one.

Creating a tunnel

Ask for a tunnel name (descriptive, e.g. homelab-web, office-api).
Call cf_create_tunnel. A secret is auto-generated if not provided.
Show the tunnel ID — the user will need it to configure ingress and run cloudflared.
Offer to configure ingress rules next (see below).

Configuring ingress rules

Ingress rules map hostnames/paths to backend services. The last rule must be a catch-all.

Ask the user: what hostname(s) should route to what service(s)?
Build the ingress array accordingly.
Call cf_put_tunnel_config with the ingress array.
Remind the user they also need a DNS CNAME pointing the hostname to <tunnel-id>.cfargotunnel.com — offer to create it using the DNS tools.

Getting the tunnel token

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>

Deleting a tunnel

Confirm the tunnel name/ID with the user.
Warn: active connections will be dropped.
Call cf_delete_tunnel.

Ingress Rule Format

See references/tunnel-ingress.md for full ingress configuration reference.

Connecting Tunnel to DNS

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:

Create a CNAME record: hostname → <tunnel-id>.cfargotunnel.com
Set proxied: true

Offer to do this automatically using cf_create_dns_record.