mcp-game

MCPlayerOne hosts an accessible public MCP Game Server that you can connect to with a variety of tooling without needing to run your own server. You can interact with the server using Warp Preview via an SSE endpoint, Cursor IDE as an MCP tool server, or Claude Desktop to proxy commands through an SSE endpoint. The server exposes a curated set of MCP tools such as listStories, createGame, startGame, getGameState, lookAround, movePlayer, takeItem, examineTarget, getLeaderboard, and getStoryById. These tools let you browse and generate game stories, start sessions, explore locations, manage items, and fetch state and leaderboards for any given story. The SSE endpoint is the primary channel for real-time interactions, and an OpenAPI spec is available for tool integration.

To play, connect using one of the supported methods described in the README (Warp Preview, Cursor, or Claude). Once connected, you can instruct the agent to pick a story or create a new game theme, start a session, and drive actions in the game world by issuing MCP tool calls. For example, you can list stories to see available narratives, generate a new game with createGame, then startGame and movePlayer to navigate through the world. The server focuses on AI-generated mazes, stories, and artifacts, with a synthwave aesthetic powered by Langflow.

Prerequisites:

• Node.js (LTS) and npm installed on your system
• Git to clone repositories

1. Clone the repository: git clone https://github.com/SonicDMG/mcp-game-server.git cd mcp-game-server

2. Install dependencies: npm install

3. Run the development server: npm run dev

4. Open the local app in your browser: http://localhost:3000

Environment variables (optional):

• PORT: Port to run the server on (default 3000)
• Any API keys or integration endpoints required by Langflow, Astra DB, or other services can be added to a .env file following the comments in .env.example

Note: For production deployment, follow your hosting provider's guidance to set environment variables and install dependencies, then use npm run build and npm start or your platform's equivalent.

Tips and common issues:

• If you see 404 or connection errors, verify you are using the correct SSE endpoint and OpenAPI URL as documented in the README.
• SSE sessions stay alive for up to 1 hour of inactivity; reconnect if your session expires.
• When running locally, ensure port 3000 (or your configured port) is not blocked by a firewall.
• The MCP tools are enabled by default in local development; for production, ensure your environment has access to any required API keys or services (Langflow, Lang AI integrations, database endpoints).
• The public server URL used for Warp Preview and Cursor integrations is https://mcplayerone.onrender.com/api/v1/mcp/sse with the corresponding OpenAPI at https://mcplayerone.onrender.com/api/v1/mcp/openapi.json
• If you plan to host your own instance, you can reuse the MCP tool names and API schema to keep compatibility with clients like Warp Preview, Cursor, and Claude.