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
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Slashloop MCP

by man0lversion 1.0.0i★ –iRuns in the cloud
Registry nameio.github.man0l/slashloop

Install

Overview

Description from the maker (original English)

Track TikTok niches, score outliers, extract hooks, draft remakes via MCP.

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://mcp.slashloop.dev/mcp

Run this in your terminal

claude mcp add --transport http slashloop https://mcp.slashloop.dev/mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "slashloop": {
      "url": "https://mcp.slashloop.dev/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": {
    "slashloop": {
      "type": "http",
      "url": "https://mcp.slashloop.dev/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://mcp.slashloop.dev/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 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account man0l, 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 2954 servers in this category
  • Published to the registry more recently than 84% of the other 2954 servers in this category
  • Basic checks equal to or better than 100% of the other 2954 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 Slashloop MCP 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.0.0) reached the registry 6 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.

slashloop

Hosted MCP server for viral short-form video research — track TikTok / Reels / Shorts sources, find outlier videos, run Gemini video analysis, and turn winners into hooks, ideas, and creative briefs.

Remote HTTP MCP only (no local stdio server): hosted on Cloudflare Workers (D1 + R2 + KV + Cron Triggers), authenticated via Supabase OAuth2 until the native-IdP swap (see docs/cf-full-backend-plan.md). Vercel is retired. API keys (Gemini, the scraper proxy) live server-side, so installers never handle them.

SurfaceWhereInstallClient
Claude pluginclaude-plugin//plugin marketplace add man0l/slashloopClaude Code
Connectordeployed hostadd …/mcp as a custom connectorClaude Desktop, Cowork, claude.ai

Live endpoint: https://mcp.slashloop.dev/mcp

Agent skills

skills/ contains installable agent skills for the remote MCP: slashloop-sources, slashloop-refresh, slashloop-gallery, slashloop-experiments, and slashloop. After publication to npm, install them with:

npx slashloop-skills install --codex

Use --claude, --project, or --target for another skills root. Copy a skill directory into your agent's skills root (for Codex, $CODEX_HOME/skills) and read its SKILL.md before running the workflow. Every skill requires an explicit workspace ID or exact workspace name; none silently defaults to the primary workspace.

src/

register-tools.ts # 63 tools, shared with the remote host tools/ # sources, feed, video, hooks, creative, studio, settings, experiments analysis/ # Gemini native + text analyzers lib/ # scrapers, gemini, spend-cap, storage, media, retention remote/ # OAuth + Streamable HTTP handlers api/ # Web-standard per-method handlers, dispatched by the Worker

via src/cf/router.ts (several URL paths share one file).

api/billing.ts # Checkout, Billing Portal, status — called by slashloop-site api/stripe/ # Webhook — the only thing that grants/revokes credits api/cron/ # Scheduled jobs (media retention sweep, weekly digest) claude-plugin/ # Claude Code plugin (skills + bundled remote MCP)

Install

Claude Code (plugin — skills + remote MCP)
/plugin marketplace add man0l/slashloop

Then install slashloop from the Marketplace tab. The plugin registers the remote MCP server and the /slashloop:track, /slashloop:discover skills. On first tool call, complete the Supabase OAuth login in the browser.

Claude Desktop / Cowork / claude.ai (connector)

Settings → Connectors → Add custom connector → https://mcp.slashloop.dev/mcp → log in → consent. All 63 tools (plus whoami) are then available; ask in plain language ("track tiktok creator @x", "find outlier videos about Y").

The /slashloop:track / /discover slash shortcuts are Claude Code plugin

skills. In Desktop/Cowork you don't need them — the connector exposes every

tool directly.

Self-host (Workers primary; Supabase OAuth)

Cutover in progress: Worker + D1 is primary (docs/cf-full-backend-plan.md,

runbook docs/cloudflare-migration.md, checks docs/cf-cutover-checklist.md).

Below is the Supabase OAuth setup and local dev server.

Vercel is retired (project deleted, api/mcp.ts / api/pages.ts

entrypoints removed in SLA-1243). The Supabase steps below are kept for the

OAuth setup; remote:dev is the local server.

1. Supabase dashboard
  1. Auth → URL Configuration → Site URL = your public connector URL.
  2. Auth → OAuth Server → Enable. Authorization path = /oauth/consent. Turn on Dynamic client registration.
  3. JWT signing → asymmetric (RS256).
  4. Email/password enabled + a user.
2. Env
cp .env.example .env

DATABASE_URL + DIRECT_URL (Supabase Postgres pooler)

SUPABASE_URL, SUPABASE_ANON_KEY

GEMINI_API_KEY, SCRAPER_PROXY_URL, PROXY_TRAFFIC_CAP_GB, PUBLIC_URL

3. Run / deploy
bun install

bun run remote:dev # local: http://localhost:8788 (+ tunnel for OAuth)

Schema changes

Production schema is managed by Supabase migrations, not Prisma. SQL files in supabase/migrations/ are applied by the Supabase GitHub integration on merge to the default branch. prisma/schema.prisma stays the source of truth for the *client* (types + query builder) — the two must be kept in sync by hand.

To add a schema change:

# 1. Edit prisma/schema.prisma

2. Generate the delta SQL (offline — no DB connection needed):

bunx prisma migrate diff \ --from-schema-datamodel \ --to-schema-datamodel prisma/schema.prisma \ --script > supabase/migrations/$(date +%Y%m%d%H%M%S)_your_change.sql

3. Harden it with IF NOT EXISTS guards (see the billing migration for the

pattern), commit, and merge — Supabase applies it.

bun run db:generate # refresh the Prisma client

Media storage (optional)

TikTok cover images and MP4s are persisted to Supabase Storage so the feed doesn't render broken images once the source CDN's signed URLs expire, and so re-analysis can skip a metered proxy download. Leave SUPABASE_SECRET_KEY unset and the entire path no-ops — everything else works as before.

Setup is one step: set SUPABASE_SECRET_KEY and CRON_SECRET in Vercel. Two buckets are needed — `thumbs` (public, 5MiB, images only) and `media` (private, 100MiB, `video/mp4` only). supabase/migrations/*_media_storage_buckets.sql creates them if they're absent, so a fresh project or a local supabase start comes up ready.

That migration is create-only (ON CONFLICT DO NOTHING) — it never

reconciles a bucket that already exists, so dashboard settings are safe from

it. It also downgrades a permissions failure on storage.buckets to a

NOTICE rather than blocking a deploy.

So on a project whose buckets were created by hand — which includes this

one — the size limits and mime allowlists above **do not exist and will not

be added by deploying**. A bucket made in the dashboard has no limit unless

someone typed one in. Nothing breaks without them; they are a ceiling, not a

requirement. To actually get them, set them in the dashboard.

The setting that does matter is `media` must be private — public would

mean an open mirror of scraped video. Worth confirming once.

Retention defaults to 3 days and is a per-workspace setting changed via the update_settings tool, capped per plan. Supabase has no object lifecycle rules, so expiry runs as a daily Vercel Cron (/api/cron/media-retention).

Analysis runs off the request path

analyze_video with the gemini-native backend queues rather than analysing inline, and returns a jobId. Poll get_video — analysisJob reports progress, analysis carries the result once it lands. gemini-text still returns its analysis directly; it is one text call and finishes in seconds.

The reason is a hard ceiling, not a preference: a native analysis has to download the MP4, upload it to Gemini, wait for processing and then generate, which does not fit api/mcp.ts's 60s maxDuration — and the Vercel plan cannot raise it. The MCP client applies its own timeout too, so a synchronous call could not be rescued by a bigger server budget anyway.

Enqueueing fires a non-blocking call to /api/jobs/analyze, which runs the job on a fresh invocation with its own 60s. That dispatch is best-effort and nothing depends on it.

What makes the queue reliable is `pg_cron`, running inside Postgres every minute (supabase/migrations/*_pgcron_drain_analyze_jobs.sql). Vercel Cron is capped at one run per day on this plan and rejects sub-daily expressions at deploy time; pg_cron is not subject to that at all. Each minute it POSTs /api/jobs/analyze, but only when a row is queued or running — so an idle queue costs zero function invocations.

The job does nothing else: recovering abandoned claims is the worker's job, in TypeScript, so MAX_ATTEMPTS and STUCK_AFTER_MINUTES have exactly one definition (src/lib/jobs.ts) instead of a second copy in SQL that drifts. running is in the gate because only the worker can decide a claim is abandoned.

Two secrets must exist in Supabase Vault or the job is a deliberate no-op:

Vault secretValue
cron_secretmust equal the CRON_SECRET env var the worker checks
worker_base_urle.g. https://mcp.slashloop.dev, no trailing slash

They are read by name at run time and are not in the migration. If you rotate CRON_SECRET in Vercel, update the Vault copy too, or the drain silently 401s.

There is deliberately no Vercel Cron fallback for this. A daily duplicate of a per-minute job is a third code path earning its keep only if pg_cron breaks, and it would mask that breakage rather than surface it. If the drain stops, jobs visibly pile up in queued — which is the signal you want.

Full design, including the later phases: docs/media-storage-plan.md.

⚠️ Do not run `bun run db:push` against production. It bypasses the

migration history entirely and will drift from what Supabase has applied.

It exists only for throwaway local databases. Likewise, never run

prisma migrate — it maintains its own _prisma_migrations table that

Supabase knows nothing about.

Routes
RoutePurpose
POST /mcpMCP endpoint (Bearer JWT)
GET /.well-known/oauth-protected-resourceRFC 9728 → Supabase AS
GET /loginEmail/password sign-in
GET /oauth/consentConsent UI
GET /healthLiveness
POST /api/billing/checkoutBearer JWT. Creates a Stripe Checkout Session, returns { url }
POST /api/billing/portalBearer JWT. Creates a Billing Portal session, returns { url }
GET /api/billing/statusBearer JWT. Returns { planKey, planCredits, packCredits, periodEnd, billingStatus }
POST /api/stripe/webhookStripe signature, not JWT. The only thing that grants/revokes credits
POST /api/jobs/analyzeCRON_SECRET. Drains queued analyses off the request path
GET /api/cron/media-retentionCRON_SECRET. Daily. Expires stored media

The three /api/billing/* routes carry CORS for SITE_URL (the landing site's origin); /mcp and /api/stripe/webhook don't need it — neither is called from a browser.

Required variables

VariableRequired?Purpose
DATABASE_URLyesSupabase Postgres pooler (?pgbouncer=true&connection_limit=1)
DIRECT_URLlocal onlySupabase session-mode URL (port 5432). Prisma's datasource declares it, but production schema changes go through supabase/migrations/ — see "Schema changes" above
SUPABASE_URLyes (remote)https://YOUR-PROJECT.supabase.co
SUPABASE_ANON_KEYyes (remote)Supabase publishable key
GEMINI_API_KEYyesPowers gemini-native (primary) + gemini-text (fallback) analysis, hook variations, briefs
SCRAPER_PROXY_URLfor live TikTokResidential proxy for list scrapes + single-video download
PROXY_TRAFFIC_CAP_GBoptionalMonthly proxy traffic cap in gigabytes of wire bytes, i.e. compressed + headers (default 0.25)
PUBLIC_URLyes (prod)Public origin Claude reaches
SITE_URLyes (billing)Origin of slashloop-site — Checkout/Portal redirects + CORS
STRIPE_MODEno (default live)live or test — which key set the app uses
STRIPE_SECRET_KEY / STRIPE_TEST_SECRET_KEYyes (billing)Live / test Stripe API keys
STRIPE_WEBHOOK_SECRET / STRIPE_TEST_WEBHOOK_SECRETyes (billing)Live / test signing secrets for /api/stripe/webhook

| STRIPE_PRICE_* / STRIPE_TEST_PRICE_* | yes (billing) | Live / test Price ids (CREATOR_MONTH, CREATOR_YEAR, PRO_MONTH, `PRO_YE

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

Ask PopNx