Skip to main content
Glama
rocnubie

82-0 Dream MCP Server

by rocnubie
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

82-0 Dream MCP Server

82-0 Dream - NBA All-Time Lineup Game

MCP Badge License: MIT Read Only Zero Config MCP Node Stdio Transport

A Model Context Protocol server that exposes the canonical 82-0 Dream knowledge surface — game modes, roster picks, and scenarios, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://82-0.games

🎮 About 82-0 Dream

82-0 Dream is a browser-based NBA all-time lineup game where the player builds a five-position starting roster across decades and franchises, then runs a season simulation to see how close the chosen lineup gets to a perfect 82-0 record. The draft is structured around a slot machine: each round randomly produces a (team, decade) cell, and the player picks one eligible legend who actually played for that franchise in that period. After five picks the simulation tallies cumulative PTS, REB, AST, STL, and BLK against fixed thresholds — clear every threshold and the lineup goes 82-0; fall short and the record degrades non-linearly toward the minimum ratio. The whole experience runs on the open web with no account, no backend, and no live actions: lineup state is encoded into the URL so any draft can be shared, opened, and reproduced exactly.

Related MCP server: 17-0 MCP Server

Key Features

  • All-time team-era draft system — 1,355 NBA players are indexed across 181 distinct (team, decade) cells, with a median of 14 eligible candidates per cell, giving non-trivial choice on almost every spin.

  • Six-language interface — English, Spanish, Brazilian Portuguese, Japanese, Korean, and Traditional Chinese are all first-class routes, each served from a locale-prefixed URL.

  • Position-agnostic placement — any spin result can be slotted into any open position on the floor, so the player can sequence their draft around scarcity instead of being locked into PG → SG → SF → PF → C.

  • Physical slot machine — a real strip-scroll with deceleration, a stop button, and Web Audio sound effects, rather than a one-frame randomizer.

  • Stat-threshold season simulation — the season verdict is driven by five real basketball stat gates (points, rebounds, assists, steals, blocks), not a single composite rating.

  • Shareable, reproducible drafts — every roster compresses into a short base64 query parameter; opening a shared URL renders the exact same draft sequence and final record.

  • Dynamic OG images — each lineup permalink generates its own Open Graph card on the edge, so a draft posted on social media shows the actual roster rather than a generic preview.

Use Cases

  • Settling pickup arguments — set up the same era constraints for both sides and see whose draft holds up to the simulation gates.

  • Era-themed challenges — restrict picks to a single decade or franchise and see how close a thematic roster can get to a perfect season.

  • Streamer and creator content — record a five-spin draft and post the share URL so viewers can replay the exact run and compare their own attempt.

  • Casual NBA history — encounter unfamiliar role players from the 70s and 80s through the eligibility lists, with each cell surfacing more than just the obvious legends.

  • Social posts — share a permalink with the dynamic OG card to show the chosen lineup and outcome at a glance, without screenshots.

Who Is It For

82-0 Dream is built for fans who enjoy "could this lineup beat the league" debates and want a quick, structured way to express a take. It suits NBA-history hobbyists who already know the rotations of past dynasties and want a sandbox to test those combinations, as well as casual fans who use the team-era constraints as a guided tour of basketball history. The multi-language interface makes it usable for international communities where NBA discussion is active. Because the game is free, has no account, and stores nothing on a server, it works equally well for a one-off social post or a recurring weekly challenge among friends.

Tools

list_scenarios

Return the canonical list of game modes and scenarios the site exposes (free play, daily, leaderboards, etc.). (82-0 Dream)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for 82-0 Dream (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://82-0/scenarios — Available game modes, scenarios, and roster-building constraints.

  • site://82-0/faq — Short FAQ generated from public site metadata.

  • site://82-0/links — Canonical URLs to share with users.

Prompts

tell_me_about_82_0

Summarize what the site is, who it's for, and how it works. — 82-0 Dream

plan_a_run_82_0

Plan a single play-through: pick a mode, draft a roster strategy, and predict outcomes. — 82-0 Dream

Installation

Install via Smithery

npx -y @smithery/cli install 82-0-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/rocnubie/82-0-mcp.git
cd 82-0-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "82-0-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/82-0-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
list_scenariosA

Return the canonical list of game modes and scenarios the site exposes (free play, daily, leaderboards, etc.). (82-0 Dream)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the transparency burden. It indicates a non-mutating operation by using 'Return', but does not disclose any side effects, authentication needs, or return format. For a simple list tool this is acceptable, but more detail (e.g., read-only guarantee, no parameters) would improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that clearly states the action. However, the trailing '(82-0 Dream)' is cryptic and adds little value, slightly detracting from clarity and conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 params, no output schema), the description adequately covers what the tool does and the type of content returned. It could mention whether it requires authentication or if the list is static, but for a list tool with no parameters, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the schema is empty (100% coverage by default). The description adds context about the content of the returned list (game modes, scenarios), which is helpful, though not strictly about parameters. Baseline is 4 due to no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Return') and a clear resource ('canonical list of game modes and scenarios'), with concrete examples (free play, daily, leaderboards). This distinguishes it from the sibling get_official_links, which focuses on links rather than scenarios.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies a read-only, authoritative listing, it does not explicitly state when to use this tool over alternatives or provide exclusions. The sibling tool get_official_links is not mentioned, so guidance is only inferred from the resource type.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_official_links
    • First observedlist_scenarios
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

The two tools serve completely distinct purposes: one returns game scenarios/modes, the other returns official links. There is no overlap or ambiguity in their functions.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'list' and 'get' as the verbs. The naming is clear and predictable.

Tool Count3/5

The server has only two tools, which feels thin for a general-purpose server. However, for a very narrow use case of retrieving canonical lists, the count might be acceptable, but it still borders on being too minimal.

Completeness4/5

The server covers the two core functions implied by its name: listing scenarios and providing official links. Minor gaps might exist, such as retrieving details for a specific scenario, but the surface seems adequately covered for a simple reference server.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • 17-0 MCP Server

    Rocniubi
    A
    license
    A
    quality
    C
    maintenance
    Exposes the canonical 17-0 knowledge surface including game rules, roster constraints, and entry points for the NFL roster strategy game to MCP-compatible AI clients.
    2
    MIT

  • 17-0 MCP Server

    rocnubie
    A
    license
    A
    quality
    C
    maintenance
    Provides verified game rules, official links, and FAQ for the 17-0 NFL roster strategy game to MCP-compatible AI clients.
    2
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/82-0-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server