Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

rdyrct

by baronunreadversion 1.1.0i★ –iRuns in the cloud
Registry nameio.github.baronunread/rdyrct

Install

Overview

Description from the maker (original English)

Create and manage short links and QR codes, and read click analytics, on your own domain.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://rdyrct.com/api/mcp

Run this in your terminal

claude mcp add --transport http rdyrct https://rdyrct.com/api/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "rdyrct": {
      "url": "https://rdyrct.com/api/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "rdyrct": {
      "type": "http",
      "url": "https://rdyrct.com/api/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://rdyrct.com/api/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account baronunread, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 2969 servers in this category
  • Published to the registry more recently than 75% of the other 2969 servers in this category
  • Basic checks equal to or better than 100% of the other 2969 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is rdyrct safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 9 days ago
Install

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 9 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

rdyrct

Organization-based link shortener + QR codes, running entirely on Cloudflare's edge.


Deploy in one click

Cloudflare copies this repository to your GitHub account, creates the database, storage and queues, and asks for one thing: the email of the account that becomes the platform admin. Leave every other value as it is. The first build serves your copy on its workers.dev address, generates the session key and applies the migrations; each push to your copy deploys it again. When you want your own domain, see Move to your own domain.

Prefer a terminal? bun run setup does the same from a clone: see Deploy to Cloudflare Workers.


Features

  • Short links with custom or random slugs, optional UTM parameters (source, medium, campaign, term, content) applied at redirect time.
  • Grouped link addresses: renaming a link keeps the old slug redirecting for 48 hours before it's freed, and a link can carry extra aliases that all redirect to the same destination.
  • QR codes per link (paid plans), with an optional logo in the center, live preview, and PNG/SVG download.
  • Custom domains (Pro): connect links.yourbrand.com via Cloudflare for SaaS, with slugs namespaced per domain.
  • Organizations with owner / admin / member roles: admins manage the team, domains, and billing; members manage links.
  • Magic-link invites: single-use, valid for 7 days, sent by email.
  • Privacy-friendly analytics: clicks per day, top links, countries, referrers, devices. No IP addresses are ever stored.
  • Per-user Free/Hobby/Pro billing through Polar, which acts as Merchant of Record and handles tax/VAT.
  • Secret-pinned superadmin console: the account matching SUPERADMIN_EMAIL gets a cloud-console panel for usage, org drill-down, and plan management. It 404s for everyone else.

Stack

rdyrct is built Cloudflare-first: the entire product runs in a single Worker with no separate backend to host:

  • Cloudflare Workers: one Worker serves the API, the redirect hot path, and the static React app.
  • D1: SQLite at the edge, source of truth for auth, orgs, links, clicks, and domains.
  • KV: slug → destination lookups on the redirect hot path, so a click never waits on D1.
  • R2: QR logo images, keyed by org, served immutable and cached.
  • Cloudflare for SaaS: custom hostnames for paid orgs' own short-link domains.
  • Workers Rate Limiting: separate abuse controls for auth, email, writes, uploads, domains, billing, and click recording.

Application layer:


Local development

What you need
  • Bun 1.4 or newer.
  • Node 24 or newer. Bun runs the scripts, but portless and wrangler run on Node.
  • macOS or Linux. Dev servers run behind portless (installed with the project), which gives each one a stable HTTPS name instead of a port.
  • Optional: the Polar CLI, only to receive sandbox billing webhooks.
First run
bun install

bun run dev

That is the whole setup. On the first run bun run dev:

  1. creates .dev.vars from .dev.vars.local.example, with an auth secret of its own (every other value works locally as it is);
  2. applies the local database migrations (it does this on every run, so a pull never leaves you a migration behind);
  3. starts the app, a local email inbox and a local Google sign-in, each behind portless (portless may ask for your password once, to listen on port 443 and trust its own certificate);
  4. prints the addresses once the app answers:
  rdyrct     https://rdyrct.localhost

scenarios https://rdyrct.localhost/__dev/scenarios inbox https://rdyrct-mail.localhost/emails (header: authorization: Bearer test_token_admin) google https://rdyrct-google.localhost

Then, in a second terminal, fill the database with fake organizations, links and clicks:

bun run db:seed:local

and open the scenarios page. It signs you in as a seeded account in each state the app has: pro-owner, hobby-owner, free-owner, fresh (a brand-new account), member, viewer, over-plan, grace-ended, locked-org, click-cap and admin. /__dev/scenarios/ ?to=/links opens a page directly.

Ctrl+C stops everything. If one of the three crashes, the other two stop with it.

Day to day
  • One name per checkout. The main checkout is rdyrct, rdyrct-mail, rdyrct-google; a git worktree gets the branch in its names (rdyrct- , rdyrct- -mail…), so any number of checkouts run side by side. bun scripts/dev-hosts.ts prints this checkout's addresses.
  • Email. Sign-up codes and every other mail land in the local inbox, never a real one:
  curl "$(bun scripts/dev-hosts.ts mail)/emails" -H 'authorization: Bearer test_token_admin'
  • Google sign-in goes through the local emulator with two accounts, testuser@gmail.com and admin@gmail.com.
  • The admin console. Open the admin scenario. (Or set SUPERADMIN_EMAIL in .dev.vars and sign up with that address.)
  • Start the database over: bun run db:reset:local, then bun run dev and bun run db:seed:local again.
  • rdyrct.com's own pages. The dev server runs the self-hosted app. Add VITE_RDYRCT_SITE=1 to .env to work on the landing and marketing pages.
From another computer or a phone

Switch portless to LAN mode once:

sudo portless service install --lan

The addresses then end in .local (https://rdyrct.local) and any device on the same network opens them; bun run dev says so when it starts. The first visit from another device shows a certificate warning, because that device does not trust portless's certificate: continue past it. Every name is a single word before .local on purpose: Windows finds only those on a network. On Linux, LAN mode needs avahi-utils.

Integrations
ServiceLocallyWhat to do
Email (Resend)the local inboxnothing
Google sign-inthe local emulatornothing
Bot check (Turnstile)Cloudflare's always-pass test keysnothing
Custom domains (Cloudflare for SaaS)simulated: DNS is ready after ~3 s and TLS after ~12 s (CF_DEV_ENV=simulated; instant skips the wait)nothing
Billing (Polar)your Polar sandboxplan limits work as they are; checkout needs the sandbox token and product ids in .dev.vars. Run bun run polar:listen beside bun run dev to receive webhooks. bun run dev gives the app the secret polar listen signs them with, so there is nothing to copy
Blog (/blog)proxied to the rdyrct-blog dev serverrun that repo's dev server; BLOG_ORIGIN_URL points at it
When something is off
  • "`.dev.vars` sets this checkout's addresses": bun run dev works out APP_URL, APP_HOST, SHARED_LINK_HOST, RESEND_BASE_URL and GOOGLE_EMULATOR_URL itself. Delete the lines it lists from .dev.vars (an old copy has them).
  • "Invalid origin" when saving or signing out: open the address bun run dev printed, not localhost: .
  • A page will not load at all: bunx portless doctor checks the proxy, and bunx portless list shows what is running.
  • The seed stops with a 500: the local database is busy (a browser test run, say). Run it again when it is quiet.

Tests

bun run test          # fast unit tests

bun run test:worker # Worker routes with local D1 and KV bindings bun run e2e:install # install Chromium for Playwright once bun run e2e:smoke # real-browser baseline regression checks bun run verify # types, lint, formatting, unit, and Worker tests

Playwright owns the local server lifecycle and never resets or seeds local Cloudflare state, so the browser tests run with or without bun run dev. The browser and Worker tests bring their own settings, so your .dev.vars and .env never change what they see. Failed browser tests keep a screenshot and trace in test-results/.


Deploy to Cloudflare Workers

git clone https://github.com/baronunread/rdyrct

cd rdyrct && bun install bun run setup

Setup asks three things: a name for the worker (Enter keeps rdyrct), a domain on your Cloudflare account (or Enter, for a free `*.w

Only the beginning is shown; read the rest in the repo

Ask PopNx