One-command public URL for the LucidLink MCP server via a Cloudflare quick tunnel
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"lucidlink-mcp-cloudflared","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# lucidlink-mcp-cloudflared One command, one URL: serve the [LucidLink MCP](https://pypi.org/project/lucidlink-mcp/) to **any MCP client that supports remote connectors** — claude.ai (web, mobile, Cowork), Cursor, Codex, and friends — through a [Cloudflare quick tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/trycloudflare/). ```bash uvx lucidlink-mcp-cloudflared ``` starts the **team gateway** and prints one connector URL (`https://<random>.trycloudflare.com/mcp`). Add it once to your client (claude.ai: Settings → Connectors); each person who connects enrolls with their own service-account token and gets their own isolated backend, identity, and audit trail. Ctrl+C kills server, tunnel, and URL together — nothing persists anywhere. Details under [Team mode](#team-mode-one-url-per-member-auth). For a personal, no-OAuth endpoint (the URL itself is the credential): ```bash uvx lucidlink-mcp-cloudflared solo ``` prints `https://<random-words>.trycloudflare.com/<secret>/mcp`, paste-ready, and self-tests it over the exact edge-and-back path a remote client will use. ## Why a separate package The official `lucidlink-mcp` package deliberately never spawns a tunnel vendor's binary or routes your traffic anywhere — its `--http` mode binds a local port and leaves the pipe to you. This companion is the explicitly-chosen convenience that adds the pipe. Installing it is the opt-in. ## Prerequisites - A LucidLink service-account token per person (a workspace admin mints them in the LucidLink admin app under Service Accounts). **No pre-setup needed**: in team mode each member pastes their token on the enrollment page when they click Connect; in `solo` mode, first run walks you through pasting and verifying yours — the same wizard as `lucidlink-mcp-setup`, saved to the same `~/.lucidlink/mcp-config.json` every LucidLink MCP client reads. - `cloudflared` on PATH — **never downloaded for you**: - macO…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.