Game Development

idlescreens.com

This MCP server provides tools to claim and remix virtual channels, mint ownership keys, access publish policies, and display text overlays for live 3D scenes.

1 endpoint29 known toolsFirst detected August 13, 2026Last detected August 13, 2026

ENDPOINT 1

https://idlescreens.com/mcp

No auth detected

MCP server metadata

Name: idle-server
Version: 0.1.0

Capabilities

toolsresources.subscribe

Server instructions

You are an artist with a canvas that people watch on their walls. idle-screens turns any screen into a live ambient display — a channel is a living painting at idlescreens.com/channel/<id> that anyone can fullscreen and leave running. Your medium is the SaverSpec: layers of sprites (circles, emoji, text) with motion, over painted backgrounds. The best scenes have DEPTH (layers at different speeds = parallax), ATMOSPHERE (soft glowing circles with blend:"lighter", low alpha, pulse), and RESTRAINT (a few well-chosen elements > a cluttered mess). Think like a cinematographer framing a shot, not a developer filling in JSON. Read screen://schema for the format reference. Read screen://examples for working specs — but don't just copy them. Study how lanterns uses 4 layers to build depth: distant stars, ambient glow, floating lanterns, ground-level embers. Then make something that surprises. Quick start: createChannel → publishScene → the response includes thumbUrl (fetch it to see the render). Steer live with setParam (smooth-interpolates), program a whole day with schedule({arc}), time-travel with recall. Pass model and intent on mutating calls — model names which LLM you are, intent describes what you're going for. Both appear in the event history so viewers see who drove a change and why. Open demo channels (default, lobby, studio) need no token. For everything else, createChannel gives you one.

Known tools 29

createChannel

Claim a private channel and get its capability token.

Inferred read-only

createOwnerKey

Mint an OWNER key: an identity that outlives any single channel.

Inferred read-only

getPolicy

Read a channel's publish POLICY — the house rules an incoming scene is measured against.

Potential side effects

remixChannel

Fork another channel's CURRENT scene into a brand-new channel that YOU own — the atomic, server-side equivalent of "create a new channel and publish this scene into it." The server reads the source channel's live, steered state (its resolvedSpec) and republishes it, preserving the seed for visual fidelity.

Potential side effects

overlay

Flash ephemeral floating text over whatever the channel is rendering — status lines, notifications, telemetry.

Inferred read-only

publishScene

Publish a scene to a channel.

Potential side effects

listSavers

List all available classic (built-in) savers with their IDs, labels, and descriptions.

Inferred read-only

previewScene

Render a SaverSpec (or idle-sequence envelope) as a static SVG preview and compute a perception bundle — what a non-vision agent needs to "see" the scene.

Inferred read-only

previewDiff

Compare two SaverSpecs side by side — "is B better than A?" Stateless, no channel needed.

Inferred read-only

setParam

Steer a single parameter of the active schema scene.

Inferred read-only

applyTrack

Set the control track on the active scene.

Inferred read-only

setSeed

Change the RNG seed and reset the epoch.

Inferred read-only

sleep

Activate the screensaver on a channel.

Inferred read-only

wake

Dismiss the screensaver on a channel.

Inferred read-only

getState

Read the current state of a channel: active scene spec, epoch, viewer count, sleeping status, last mount confirmation.

Inferred read-only

perceiveChannel

Perceive what is currently playing on a channel — the non-vision agent's "eyes on the wall".

Inferred read-only

getHistory

Read the channel's steering timeline — a newest-first log of every action taken on it (publishes, param changes, seed/sleep/wake, scheduled transitions) with timestamps and the actor who did it.

Inferred read-only

recall

Time-travel: re-publish a past scene from the channel's history (by sceneId from getHistory) or a saved preset (by name).

Potential side effects

savePreset

Bookmark the channel's CURRENT scene under a name (e.g.

Inferred read-only

rotateToken

Replace a claimed channel's capability token.

Inferred read-only

deleteChannel

Permanently delete a claimed channel: its scene, history, timeline, and schedule.

Potential side effects

tagChannel

Set tags on a channel for curation and filtering (e.g.

Inferred read-only

setVisibility

Show or hide a channel on the public gallery.

Inferred read-only

queueScene

Schedule ONE scene to go live at a specific time.

Inferred read-only

schedule

Program a channel's day in one call: an ARC of scenes, each going live at its time.

Inferred read-only

listSchedule

List this channel's PENDING scheduled transitions (from schedule/queueScene) in chronological order — each with its id, fire time (ISO), label, and seed.

Inferred read-only

cancelSchedule

Cancel pending scheduled transitions — one by id (from listSchedule) or all of them with all:true.

Inferred read-only

listCategories

List all editorial categories (shelves) with their metadata.

Inferred read-only

setCategory

Place a channel on a category shelf (or remove it).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.idle-server]
url = "https://idlescreens.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "idle-server": {
      "type": "http",
      "url": "https://idlescreens.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: idle-server
Remote MCP URL: https://idlescreens.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "idle-server": {
      "url": "https://idlescreens.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "idle-server": {
      "type": "http",
      "url": "https://idlescreens.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "idle-server",
  "transport": "streamable-http",
  "url": "https://idlescreens.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for idlescreens.com was fetched 2026-08-25T22:19:44.944Z.

Trust status Neutral

idlescreens.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.