Skip to main content
Glama

White Hat Thumbnails — MCP server

Lets an AI assistant run your Roblox thumbnails end to end from a chat window: read how they are performing, generate new ones, publish them, choose which are live, rotate them automatically, and talk to your Discord team about it.

"how are the thumbnails doing on +1 dumpling escape?"
"what am I actually allowed to do on magnet simulator?"
"generate three variants from this reference and put the best one live"
"drop the worst performer and promote the next one from the queue"
"go notify the thumbnail team on +1 dumpling escape walls to pay this link,
 with two options approve and disapprove"

Everything runs against your own account. A key only reaches the projects you already have access to on the site, and it can never read back a stored credential — only tell you whether one is there and whether it works.


Setup

1. Get a key

Sign in at https://whitehatthumbnails.vercel.app, open Keys, and create one. It is shown once — copy it then.

2. Install

git clone https://github.com/Haydebug/whitehat-thumbnails-mcp.git
cd whitehat-thumbnails-mcp
npm install
npm run build

3. Point your assistant at it

claude mcp add whitehat-thumbnails \
  --env WHT_API_KEY=wht_your_key_here \
  -- node /absolute/path/to/whitehat-thumbnails-mcp/dist/index.js

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "whitehat-thumbnails": {
      "command": "node",
      "args": ["/absolute/path/to/whitehat-thumbnails-mcp/dist/index.js"],
      "env": { "WHT_API_KEY": "wht_your_key_here" }
    }
  }
}

The config file lives at:

  • macOS ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows %APPDATA%\Claude\claude_desktop_config.json

Restart Claude Desktop afterwards.

Use an absolute path — the assistant does not run from this folder.


Related MCP server: GPT Image MCP Server

Tools

Knowing what you can do

Tool

What it does

check_permissions

Probes one game and reports exactly which tools will work on it, and why the rest will not

set_project_credentials

Store an Open Cloud key and/or a Roblox cookie on a game — the two things the report asks for

Projects

Tool

What it does

list_projects

Your games and their universe ids

get_game_info

Look up any Roblox game by link, place id or universe id — it need not be yours

search_roblox_games

Search Roblox by name or keyword

add_project

Put a game on your account, pinned to whichever Roblox account can edit it

list_collaborators / invite_collaborator

Who else reaches a project, and a single-use invite link

Thumbnails

Tool

What it does

get_thumbnails

Live and inactive thumbnails with QPTR, impressions, qualified plays, average playtime

set_active_thumbnails

Choose which thumbnails Roblox actually shows — replace, add or remove

upload_thumbnail

Publish a local image as a game thumbnail

delete_thumbnail

Permanently remove a thumbnail from the game

get_qptr_trend

Daily click-through and impressions over 7, 14 or 30 days

get_thumbnail_momentum

Which individual thumbnails are rising, falling or flat

export_thumbnail_report

The whole set, ordered by QPTR, as a PDF written to disk

Making thumbnails

Tool

What it does

generate_thumbnail

Generate an image from a prompt and references, write it to disk, optionally publish it

list_generations

Everything generated for a game, with the prompts behind each one

upload_generation

Publish something from that history without re-uploading it

list_style_profiles

The named style guides generation can be pointed at

Rotating them

Tool

What it does

get_auto_swap

Whether a game rotates itself, on what rules, and what recent runs did

configure_auto_swap

Turn rotation on or off and set its thresholds

run_auto_swap

Fire one rotation now, without waiting for the schedule

get_queue

What is lined up to go live next

queue_thumbnail / unqueue_thumbnail

Add to or remove from that line

Discord

Tool

What it does

list_discord_roles

Roles that can be notified

notify_team

DM a role, optionally with images and two answer buttons

get_notification_history

What was already sent, with per-person answers and paid status

create_ticket

Open a ticket — posts an embed with Approve/Deny in the game's channel

list_tickets

Just the tickets on a game, with what is still unanswered or unpaid

list_artist_channels

Text channels in the studio server, with ids

create_channel / link_channel

Make a channel, and point a game's tickets at one

get_channel_messages

Read a channel — author, time, text, attachment URLs

send_channel_message

Post in a channel as the bot, as plain text or an embed, optionally with images

Game names are matched loosely, so "dumpling escape" finds "+1 Dumpling SMASH Walls". If a name is ambiguous the tool says so and lists the candidates rather than guessing.

Knowing what you are allowed to do

Authority over a Roblox game is not one permission. It is spread across a .ROBLOSECURITY cookie (uploads, deletes, swapping the live set), an Open Cloud key (analytics), a personalization config Roblox only creates once a game has several thumbnails (whether there is a swappable live set at all), and a Discord bot (tickets and notifications). Any of them can be missing on its own, and the failure you see is the same shrug either way.

check_permissions probes all of them at once and answers in two lists:

MAGNET SIMULATOR LEGENDS — universeId 7592711723
You own this project.
Open Cloud key: stored (••••YkpR), encrypted at rest
Roblox account: WH_AIbot (the shared default account)

WORKS (6)
  get_thumbnails
      2 active, 124 inactive
  analytics (QPTR, impressions, playtime)
      figures came back for 16 of 126 thumbnails via the Open Cloud key ••••YkpR
  set_active_thumbnails
      a personalization config was resolved, so the live set can be changed
  …

DOES NOT WORK (2)
  upload_thumbnail, delete_thumbnail
      WH_AIbot (the shared default account) is signed in but Roblox refuses it
      edit access to this game
      Fix: give that account permission on the experience, or store a cookie for
      one that already has it with set_project_credentials.
  ticket posting to a channel
      this game is not linked to a Discord channel, so tickets only go out as DMs
      Fix: call create_channel with this game, or link_channel with an id.

Every "no" carries the reason and the fix, because "no" on its own sends you round the same loop again. Run it before a write you care about, or after one fails and it is not obvious which credential was missing.

The two credentials it asks for go in with set_project_credentials. They are stored encrypted and never read back — the report can say a key is present and whether it works, and nothing more.

Choosing what is live

Uploading a thumbnail does not show it to anyone. Roblox keeps every image a game has ever had and serves a chosen subset; set_active_thumbnails is what changes that subset, and it takes effect immediately.

set_active_thumbnails(game: "magnet simulator", ids: ["108286870859415"], mode: "add")
set_active_thumbnails(game: "magnet simulator", ids: ["112922133257215"], mode: "remove")

add and remove adjust what is already live and are what you usually want. replace makes exactly the listed set live and everything else inactive — easy to fire by accident when you meant add. Ids can be the asset ids the reports lead with or the internal thumbnail ids; both are accepted.

Nothing here deletes anything. A deactivated thumbnail keeps its history and can be brought back. delete_thumbnail is the one that cannot be undone, and it refuses to remove a game's last live image.

Generating

generate_thumbnail runs the same pipeline the site's generator page does: your prompt is rewritten against a style guide, then rendered against one or more reference images. The result is written to a file on your machine so it can actually be looked at before it goes anywhere near a game.

generate_thumbnail(
  game: "magnet simulator",
  prompt: "character yanking a giant magnet out of a pile of loot",
  referencePaths: ["ref.png"],
  profile: "Simulator"
)

References can be local paths or public URLs; at least one is required, since the model works from an image rather than from nothing. profile picks one of the style guides list_style_profiles lists. Pass publish: true only when the image has already been agreed on — otherwise generate, look at the file, then upload_thumbnail.

Rotating automatically

Auto-swap drops the worst-performing live thumbnails by QPTR and promotes replacements from a queue, on a schedule.

queue_thumbnail(game: "magnet simulator", id: "108286870859415")
configure_auto_swap(game: "magnet simulator", enabled: true, dropCount: 1,
                    frequencyMinutes: 1440, qptrThreshold: 2)
run_auto_swap(game: "magnet simulator")

qptrThreshold is a percentage, not a fraction: 2 means 2%. A game with an empty queue will run and do nothing, so check get_queue before turning it on. get_auto_swap shows the rules, the schedule and what recent runs actually moved — and if rotation turned itself off, the reason it gives is the thing to fix.

Answer buttons

notify_team can attach two buttons and let people answer:

notify_team(
  game: "+1 dumpling escape",
  role: "Thumbnail Team",
  message: "Pay here please: https://…",
  askForAnswer: true,
  approveLabel: "Paid",
  declineLabel: "Cancel"
)

Whoever clicks has their decision DM'd to everyone with that role, including themselves. Each person can answer once.

get_notification_history reports each answer on its own line with the person's Discord id and the moment they clicked, so an automation can gate on a specific pair of people having both approved rather than on a count:

2026-08-20T03:42:31.704Z — Hayden S → "Thumbnail Team" (2/2 delivered) · ticket clx…
  Dumpling concept art from lamy
  payment: $10 · https://paypal.me/asianlamy · PAID by Bug at 2026-08-20T03:45:02.118Z
  answers:
    Bug (4207…) = Paid at 2026-08-20T03:45:02.118Z
    ang (9931…) = Deny at 2026-08-20T03:46:44.500Z

Paying for commissioned work

Pass paymentAmount and the ticket becomes an invoice — the DM shows the amount and a pay button, the buttons default to Paid / Cancel, and the first click on Paid marks the ticket paid:

notify_team(
  game: "+1 dumpling escape",
  role: "Thumbnail Team",
  message: "Dumpling concept art from lamy",
  paymentAmount: 10,
  paypalLink: "paypal.me/asianlamy"
)

paid latches. A decline after someone has already marked it paid is recorded as an answer but does not un-pay the ticket — money that went out cannot be recalled by a button.

Tickets

A ticket is the same record as a team notification — same table, same per-person answers, same paid flag — with a title, a type and a channel to live in. It can be opened three ways and they are indistinguishable afterwards:

  • /ticket create in Discord, from any channel or a DM with the bot

  • create_ticket here, for automations

  • the notification tooling on the site

create_ticket(
  game: "+1 dumpling escape",
  type: "concept_review",
  title: "Dumpling wall smash — first pass",
  description: "Three angles from lamy. Picking one for the A/B.",
  imagePaths: ["pass1.png", "pass2.png"]
)

Types are concept_review, final_review, payment and status. Everything but status gets Approve / Deny buttons; a payment ticket gets Paid / Cancel plus the amount and a tappable PayPal link, and the first Paid click sets the paid flag. Answers land in get_notification_history exactly as button answers on a DM do, and the embed in the channel is rewritten as people answer so the message everyone is looking at shows the current state.

Each game posts its tickets to one channel, set once from Discord:

/ticket config game:<game> channel:#lammyta

Without that, a ticket is still created and still readable — it just has nowhere to appear, and the tool says so rather than pretending it was delivered.

Talking to artists

Each artist has their own text channel in the studio server. The three channel tools are a poll loop, not a live feed: read with since set to the lastMessageId you were given last time, and you see only what arrived since.

list_artist_channels()                              → #lammyta — id 1539…
get_channel_messages(channelId: "1539…", since: "…") → replies + art
send_channel_message(channelId: "1539…", text: "…", imagePaths: ["brief.png"])

Attachment URLs from Discord are signed and expire in roughly a day, so download art when you first see it rather than storing the link for later.

Embeds

A channel post can be an embed rather than a line of text — the card with a coloured bar down the side, the same one the notification DMs use. Pass embed instead of, or alongside, text:

send_channel_message(
  channelId: "1539…",
  embed: {
    author: "White Hat Thumbnails · MCP",
    title: "+1 Dumpling SMASH Walls",
    url: "https://whitehatthumbnails.vercel.app/projects/10307670587",
    color: "#facc15",
    description: "Five thumbnails live. **0.41% QPTR** on 1.95M impressions.",
    fields: [
      { name: "Top QPTR", value: "0.41%", inline: true },
      { name: "Impressions", value: "1,947,283", inline: true }
    ],
    thumbnailUrl: "https://tr.rbxcdn.com/…",
    imageUrl: "https://tr.rbxcdn.com/…",
    footer: "Sent by the MCP",
    buttons: [{ label: "View project", url: "https://whitehatthumbnails.vercel.app/…" }]
  }
)

The shape is flat on purpose — Discord nests the footer, the image and every button inside wrappers, and none of that is worth knowing to send a message. Fields are cut to the lengths Discord enforces rather than sent long, because it rejects the whole message over one oversized field.

Buttons here only open links. A button that asks a question and records the answer belongs to notify_team or create_ticket, which have somewhere to write the answer down.

For the bot to see a channel it needs View Channel, Read Message History, Send Messages and Attach Files there. Invite it with:

https://discord.com/oauth2/authorize?client_id=<APP_ID>&scope=bot%20applications.commands&permissions=117760

Both scopes matter. bot gets it into the server; applications.commands is what makes /ticket visible there. A bot invited without the second one works fine for DMs and channel posts while its slash commands silently never appear.


Configuration

Variable

Required

Meaning

WHT_API_KEY

yes

Your key from the Keys page

WHT_BASE_URL

no

Only if you run your own copy of the site


Notes

Discord DMs can be refused, and that is not a bug. Discord will not let a bot message someone who has blocked it, or who has DMs from server members turned off, or who shares no server with the bot. notify_team reports per person which of those happened rather than a single success count.

Roblox moderates uploads asynchronously. upload_thumbnail returning Pending means it was accepted and is being reviewed — usually a few minutes.

Some games are read-only. Uploading and swapping need a Roblox account with edit access to that experience; an Open Cloud key cannot do either. The site shows each project as Full Edit, View Only or Public View, and the tools say when something is unavailable rather than failing silently. check_permissions is the quickest way to find out which case a game is in.

Three tools change what players actually see, and do so the moment they return: set_active_thumbnails, run_auto_swap, and configure_auto_swap with enabled: true. Uploading and generating do not — an uploaded thumbnail sits inactive until something puts it live.

One tool cannot be undone. delete_thumbnail removes the image from Roblox along with its analytics history. Deactivating with set_active_thumbnails(mode: "remove") is the reversible version and is almost always what was meant.

check_permissions does not probe generation. The only honest check would be generating an image, which costs money and leaves a record behind. If generate_thumbnail is going to fail it fails on the first call, with the reason.

Licence

MIT

Available Tools

39 tools
add_projectAdd a game as a projectA

Put a Roblox game on this account so the rest of these tools can act on it. Takes a game link, place id or universe id, looks the game up, and pins it to whichever Roblox account can actually edit it — without that pin, writes default to an account with no access and fail. A game already claimed by someone else is refused rather than taken over. Follow it with check_permissions to see what still needs a credential.

Inputs: game (required), channelName, isUniverseId.

check_permissionsWhat can I do to this gameA

Everything this key is allowed to do to one game, probed rather than assumed: whether analytics are readable, whether the Roblox account behind the project can upload, delete and swap the live set, whether the game has a personalization config at all, whether auto-swap is armed, and whether Discord and its channel are wired up. Call this first when a write is about to happen, or when something failed and it is not obvious which credential was missing — every 'no' comes back with the reason and what would fix it.

Inputs: game (required).

close_ticketClose or reopen a ticketA

Close a ticket once it is done, or open a closed one back up. Closing renames its channel from 🟢-0007 to closed-0007 and greys the embed, so the sidebar stops showing it as live work. The same thing the Close button on the ticket and /close-ticket in Discord do. Name the ticket by its number (0007, or just 7) or by the id create_ticket handed back.

Inputs: game (required), ticket (required), reason, reopen.

configure_auto_swapConfigure auto-swapA

Turn a game's automatic thumbnail rotation on or off and set its rules. Turning it on schedules the next run and clears any self-disabled flag. Every field is optional: only what is passed changes. Rotation pulls replacements from the queue, so a game with an empty queue will run and do nothing — check get_queue before turning it on.

Inputs: game (required), enabled, dropCount, qptrThreshold, +2 more.

create_channelCreate a studio channelA

Make a text channel in the studio Discord server - one per game or per artist. Pass a game to point it at that game at the same time, which is the whole of setting a new game up: the channel exists, its tickets go there, and the site's View channel button follows. Running it twice with the same name reuses the channel already there rather than making a second one. The bot needs Manage Channels; without it this comes back saying so, and the fix is a fresh invite link, not another call.

Inputs: name (required), game, topic, category.

create_ticketFile a ticketA

Open a ticket on a game — the same thing the /ticket command does in Discord. Each ticket gets a channel of its own, named 🟢-0001 and filed under a category named after the game, so the sidebar reads as what is open on it; closing the ticket renames that channel to closed-0001 and drops the dot. The ticket itself is an embed with Approve, Deny and Close buttons. Use type 'payment' with amountUsd to ask for money; it counts as paid once someone clicks Paid.

Inputs: game (required), type (required), title (required), description (required), +5 more.

delete_thumbnailDelete a thumbnail from RobloxA

Permanently remove a thumbnail from a Roblox game. This is not the same as taking it out of the live set — set_active_thumbnails with mode "remove" does that and keeps the image, which is almost always what is wanted. Roblox has no undo for a delete, and the analytics history for that asset goes with it. Only reach for this when the image should not exist on the game at all.

Inputs: id (required), game (required).

export_thumbnail_reportExport a thumbnail PDFA

Render a game's thumbnails and their figures, ordered by QPTR, into a PDF written to this machine — the shareable version of get_thumbnails, for sending to a client or an artist. Images are fetched and embedded, so this takes a few seconds.

Inputs: game (required), range, outputPath, includeInactive.

generate_thumbnailGenerate a thumbnailA

Make a new thumbnail image with the site's AI pipeline — the same one the generator page uses — from a prompt and at least one reference image. The prompt is rewritten against the studio style guide first unless enhance is turned off. The result is written to a file on this machine so it can be looked at, and saved to the project's history. Pass publish to send it straight to Roblox, which is only worth doing when the image has already been agreed on; otherwise generate, look at it, then call upload_thumbnail.

Inputs: game (required), prompt (required), model, enhance, +6 more.

get_auto_swapAuto-swap statusA

Whether a game rotates its own thumbnails, on what schedule and rules, and what the last runs actually did. Auto-swap drops the worst-performing live thumbnails by QPTR and promotes replacements from the queue. A game that turned itself off reports why — that reason is the thing to act on.

Inputs: game (required), logs.

get_channel_messagesRead a channelA

Messages in a studio channel, oldest first, with author, time, text and attachment URLs. Pass the lastMessageId from the previous read as since to get only what is new — that is how a poll avoids re-reading. Attachment links are signed and expire within about a day, so download art when you see it rather than saving the URL.

Inputs: channelId (required), limit, since.

get_game_infoLook up a Roblox gameA

What Roblox knows about a game — name, description, players, visits, likes, creator — from a game link, a place id or a universe id. It does not have to be a project on this account. The reply also says whether any configured Roblox account can edit its thumbnails, which is what decides whether adding it as a project would be read-only.

Inputs: game (required), isUniverseId.

get_notification_historyPast notificationsA

What has already been sent to the team about a game, with timestamps and any answers. Each answer names who gave it, what they chose, their Discord id, and when — so a caller can gate on a specific pair of people having both approved. Payment tickets also report whether they are paid.

Inputs: game (required), limit.

get_qptr_trendQPTR over timeA

A game's daily click-through rate and impressions, to answer whether it is trending up or down rather than how one thumbnail is doing right now. Roblox only serves the last 30 days; anything older comes from the site's own archive, and days it has neither for come back empty rather than as a zero.

Inputs: game (required), range.

get_queueThe swap queueC

Thumbnails lined up to go live, in the order auto-swap will promote them. This is where rotation gets its replacements: an empty queue is why an enabled auto-swap runs and does nothing.

Inputs: game (required).

get_thumbnail_momentumWhich thumbnails are rising or fallingA

Per-thumbnail direction over a window: whether each one's QPTR is climbing, sliding or flat, compared against its own earlier half rather than against the others. Use it to decide what to drop when a game's overall numbers are fine but something in the set is dragging. Needs stored history, so a game added recently will have nothing to compare.

Inputs: game (required), range, includeInactive.

get_thumbnailsGet thumbnail performanceA

Read a game's thumbnails and how they are performing: QPTR, impressions, qualified plays and average playtime, split into the live (active) set and inactive variants. Answers questions like 'how are the thumbnails doing on '.

Inputs: game (required), range, includeInactive.

get_ticket_stageRead a ticket’s stageB

Where a ticket sits in the twelve-stage pipeline, what comes next, any estimate on it, and every stage it has been through with who moved it and when. Use this to answer "how is that going" without reading the channel.

Inputs: game (required), ticket (required).

invite_collaboratorMint an invite linkA

Create a single-use invite token for a project, good for seven days. Whoever redeems it on the site gains access to the project — they can read its thumbnails and act on it, but never see its stored credentials. Owner only. Hand the token to one person; it is spent on first use.

Inputs: game (required).

list_artist_channelsList studio channelsA

The text channels the bot can see in the studio Discord server, with their ids — one per artist. Use this to turn an artist name into a channel id. A channel missing from this list is one the bot has not been given access to.

Inputs: no named parameters.

list_collaboratorsWho else can reach this projectA

The people a project has been shared with, and any invite links still open. Owner only. A shared collaborator can read and act on the project but cannot see or change its stored credentials.

Inputs: game (required).

list_discord_rolesList Discord rolesA

List the Discord roles that can be notified, so a name the user said can be matched to one.

Inputs: game (required).

list_generationsPast generationsA

Every thumbnail generated for a game, newest first, with the prompt behind it, the rewritten prompt the model actually saw, the references used and the stored image URL. Use it to find something made earlier and publish it with upload_generation, or to reuse a prompt that worked.

Inputs: game (required), limit.

list_projectsList projectsA

List the Roblox games on this account, with their universe ids. Use this to turn a game name the user said into an id.

Inputs: no named parameters.

list_style_profilesList style profilesA

The named style guides the prompt enhancer can be pointed at, with the instructions each one carries. Pass a name as profile to generate_thumbnail to generate in that style instead of the studio default.

Inputs: no named parameters.

list_ticketsOpen tickets on a gameD

Just the tickets on a game, without the plain notes get_notification_history mixes in — what was asked for, who answered, and for payment tickets whether the money has been marked paid. Use it to answer 'what is outstanding on this game'.

Inputs: game (required), limit, unansweredOnly.

notify_teamNotify a Discord roleA

DM everyone holding a Discord role about a game. Can attach images and can ask for an answer with two buttons whose labels you choose (for example Approve/Disapprove, or Paid/Cancel). When buttons are used, whoever answers has their decision sent to the whole role. Pass paymentAmount to make it an invoice for commissioned work: the DM shows the amount and a pay button, the buttons default to Paid/Cancel, and clicking Paid marks the ticket paid.

Inputs: game (required), role (required), message (required), ticket, +7 more.

post_ticket_panelPut up the Add ticket buttonA

Post a game's standing "Add ticket" button in its channel. Anyone who clicks it gets a short form, and filing it opens a numbered channel for that ticket under the game's category. create_channel and link_channel already do this when they point a game at a channel, so this is for putting the button back after it has scrolled out of sight, or moving it somewhere else. Posting it again takes the previous one down rather than leaving two.

Inputs: game (required), role, channelId.

queue_thumbnailQueue a thumbnailA

Line an existing thumbnail up to go live at the next rotation. It has to already be on the game — upload it first if it is not. Queuing does not change what players see; auto-swap promotes it when it drops something, or set_active_thumbnails can put it live straight away.

Inputs: id (required), game (required).

run_auto_swapRun auto-swap nowA

Fire a game's rotation once, immediately, without waiting for the schedule or needing it enabled. It applies the same rules — drop the worst live thumbnails by QPTR, promote from the queue — and changes what players see. A run that finds nothing worth swapping reports that rather than failing.

Inputs: game (required).

search_roblox_gamesSearch RobloxA

Search Roblox for games by name or keyword — for finding a game to add, or for looking at what comparable experiences are using as thumbnails. Results are what Roblox shows a signed-in account, so they are tailored rather than absolute.

Inputs: query (required), limit.

send_channel_messagePost in a channelA

Say something in a studio channel as the bot, as plain text or as an embed — the card with a coloured bar, a title, fields and link buttons. Images can be attached either way. Meant for messages that were already agreed on — briefs, thank-yous, status notes — not for improvising a conversation with an artist.

Inputs: channelId (required), text, embed, imagePaths.

set_active_thumbnailsChoose which thumbnails are liveA

Change which of a game's thumbnails Roblox shows on the homepage. Ids can be either the asset ids get_thumbnails leads with or the internal thumbnail ids — both are accepted and resolved. mode 'replace' makes exactly the listed set live and everything else inactive; 'add' and 'remove' adjust the current set instead, which is what you usually want when acting on one thumbnail. The change is immediate and Roblox starts serving it to players; nothing is deleted either way, so an inactive variant can always be brought back.

Inputs: ids (required), game (required), mode.

set_project_credentialsStore Roblox credentials for a gameA

Attach an Open Cloud API key and/or a .ROBLOSECURITY cookie to a game — the two things check_permissions reports missing. The key unlocks analytics; the cookie unlocks uploading, deleting and swapping the live set. Both are stored encrypted and never read back. Pass an empty string to clear one: clearing the cookie reverts the game to the shared default account. Owner only. Do not invent these values — they come from the user.

Inputs: game (required), openCloudKey, robloSecurity.

set_ticket_stageMove a ticket along the pipelineA

Set which of the twelve production stages a ticket is on, and redraw the pinned status card in its channel. Every move posts its own card in the ticket channel rather than editing the last one, so the channel is a readable record of how the work went; only the newest stays pinned. Jumping several stages at once is allowed and the card names the ones that were skipped. Opening a ticket puts it on 'ordered' and clicking Approve moves it to 'confirmed' automatically; every stage after that is set here or with /ticket status. The two review gates are stored apart — 'concept_review' waits on the idea, 'art_review' waits on the finished art — even though both read as "Waiting for review" to a person.

Inputs: game (required), stage (required), ticket (required), eta, +1 more.

unqueue_thumbnailTake a thumbnail out of the queueA

Remove an entry from the swap queue so auto-swap will not promote it. The thumbnail itself is untouched and stays on the game.

Inputs: id (required), game (required).

upload_generationPublish a stored generationA

Publish an image already in a project's history to Roblox, by its generation id from list_generations. Nothing is downloaded or re-uploaded — the site sends its own stored copy — and the resulting Roblox asset id is recorded against the generation, which is what later lets its analytics be traced back to the prompt that made it.

Inputs: game (required), generationId (required).

upload_thumbnailUpload a thumbnail to RobloxA

Publish a local image as a thumbnail on a Roblox game. Roblox moderates asynchronously, so a Pending result is normal rather than a failure.

Inputs: game (required), imagePath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 39 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: notifications, projects, channels, thumbnails, generations, auto-swap, queue, analytics, reports, permissions, credentials, tickets, and collaborators. Even seemingly similar tools like get_thumbnails, get_qptr_trend, and get_thumbnail_momentum measure different metrics (current performance, overall trend, per-thumbnail direction). Descriptions clearly delineate boundaries, minimizing agent misselection.

    Naming Consistency5/5

    All 39 tools follow a consistent snake_case verb_noun pattern (e.g., list_projects, set_active_thumbnails, get_auto_swap, queue_thumbnail). There are no mixed conventions or vague verbs like 'process' or 'run'. The naming is predictable and aligns with the action each tool performs.

    Tool Count3/5

    At 39 tools, the surface is heavy and exceeds the typical 15-tool sweet spot. However, the server covers a broad domain—Roblox thumbnail management, Discord integration, ticket workflows, analytics, and collaboration—so each tool earns its place. Still, the sheer number may overwhelm agents, making this borderline between 'heavy but justified' and 'too many'.

    Completeness4/5

    The toolset covers the full lifecycle: project onboarding, credential setup, thumbnail generation/upload/deletion, active set management, auto-swap configuration, queue management, analytics tracking, reporting, notifications, ticketing, and collaboration. Minor gaps exist (e.g., no remove_project or revoke_collaborator), but agents can work around these with existing tools. Overall, the surface is nearly complete for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers