Sphere MCP Gaming Server

Provides 24h, payment-gated access to Unicity games via MCP HTTP, enabling Nostr-based payments and blockchain identity.
  • javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

The Sphere MCP Gaming Server provides 24-hour, payment-gated access to Unicity-native games through a streamlined HTTP transport and Nostr-based payments. It lets players launch games after verifying day passes and wallet payments, while maintaining a simple, stateless interaction model for multi-user scenarios.

How to use

You connect your MCP client to the server to list available games, initiate access to a game, and complete payments when required. A successful payment gates 24 hours of access to all games. The server uses your Unicity nametag as your identity and routes payments through Nostr, enabling a decentralized payment flow cleanly tied to your wallet.

How to install

Prerequisites: you need Docker and Docker Compose installed on your system. You should also have a compatible Node/npm setup if you plan to run auxiliary tools locally.

Step 1. Prepare configuration values by creating a working environment file.

cp .env.example .env

# Edit .env to set required values:
# MCP_NAMETAG=gaming-mcp
# PAYMENT_COIN_ID=your_coin_id_here

Step 2. Start the server with Docker Compose.

docker compose up -d

The server will generate a private key, mint a nametag on the Unicity blockchain, publish a Nostr binding for the nametag, and start listening for MCP connections.

Step 3. View logs to verify startup.

docker compose logs -f

Configuration and endpoints

The server exposes two transport methods over HTTP. For legacy clients, use the SSE endpoint, and for modern clients, use the Streamable HTTP endpoints.

HTTP endpoints used by MCP clients include the following. You can base your client URL on the local server address (for example, http://localhost:3001). Use the Streamable HTTP path for modern clients.

Legacy SSE (MCP Inspector and older clients) endpoints:

GET /sse
POST /messages?sessionId=xxx

Streamable HTTP (modern clients) endpoints:

POST /mcp  // Send JSON-RPC requests
GET  /mcp  // SSE stream for responses

Available tools

list_games

Return all available games with IDs, names, and descriptions.

check_access

Check a user’s access status and whether their day pass is still valid.

get_game

Obtain access to a specific game; initiates payment if the user does not have an active day pass.

confirm_payment

Wait for payment confirmation for a given user and game, enabling access once complete.

get_wallet_balance

Retrieve the MCP wallet balance (admin access).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational