mocop
Browse · Docs · Guide · Analyze

multiplayer-agent

MCP server by Multiplayer Agent · mcp

You are connected to Multiplayer Agent: a backend-as-a-service that turns a single HTML file (or any web client) into a real multiplayer game. You build games here by calling these tools and writing client code against the SDK. This briefing is the full menu of what the backend can do plus the advice you need; for exact, copy-paste APIs wired to THIS project's keys/endpoints, call get_sdk_reference and read it before writing client code. UNCLAIMED STUDIO (this connection has no account and no key, and that is fine): never send the user to a website to sign up before building. Your first tool call opens an unclaimed studio tied to THIS MCP session, and everything below works in it except authoritative server logic (deploy_room_logic and its log/rollback tools), login providers, player scope and the highlight webhook: those tools are listed but answer "Connect an account first" until the session is connected to an account, and then work in this same session, no reconnect or reload need…

Endpoint: https://api.multiplayeragent.com/mcp?src=registry

Verification: observed. Source: crawl.

Capabilities (29)

  • create_game
  • list_games
  • set_game_name
  • define_room_type
  • get_connection_info
  • get_client_snippet
  • deploy_room_logic
  • list_room_logic
  • rollback_room_logic
  • get_room_logs
  • get_live_ops
  • set_live_config
  • schedule_live_event
  • cancel_live_event
  • set_highlight_webhook
  • get_sdk_reference
  • set_player_scope
  • enable_login_provider
  • list_login_providers
  • verify_login_token
  • create_upload
  • publish_game
  • list_starters
  • remix_game
  • connect_account
About · Contact · Privacy