🍋 Lemonade Stand MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Lemonade Stand MCP Server?

The Lemonade Stand MCP Server is a demonstration of the Model Context Protocol (MCP) that allows users to play the classic Lemonade Stand game through Claude Desktop, showcasing how AI models can interact with external data sources and tools.

How to use Lemonade Stand MCP Server?

To use the server, clone the repository, install the necessary dependencies, configure Claude Desktop with the server details, and start a new game by interacting with Claude.

Key features of Lemonade Stand MCP Server?

  • Dynamic weather system affecting sales
  • Business simulation with supply and demand
  • Strategic pricing and inventory management
  • 14-day game cycle with profit tracking
  • Fully playable through Claude Desktop

Use cases of Lemonade Stand MCP Server?

  1. Educational tool for understanding business concepts
  2. Simulation of economic principles in a fun environment
  3. Interactive gameplay experience using AI

FAQ from Lemonade Stand MCP Server?

  • Can I play the game on any platform?

Yes! The server can be run on any platform that supports Node.js and Claude Desktop.

  • Is there a cost to use the Lemonade Stand MCP Server?

No, it is free to use as it is an open-source project.

  • What do I need to run the server?

You need Node.js, Claude Desktop, and npm installed on your machine.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago