Asobiai

games.asobiaiPublished by asobiai.gamesOfficial publisherv1.0.0Updated Oct 24, 2026

Publish AI-made browser games and get a shareable URL. Update, test and read player feedback.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Publish AI-made browser games to a hosted platform and get a shareable URL, with updates, testing and player feedback.

What you can do
A remote MCP server for publishing browser games created with AI assistance. According to the registry description, it lets an assistant publish a game and return a shareable URL, update an existing game, test it, and read player feedback.
When to use it
Use it when you have an AI-generated browser game you want to put online quickly and share by link, or when you want an assistant to push updates and check how players are responding.
Requirements
A remote streamable HTTP endpoint at asobiai.games; no local package or runtime is needed. Authentication is OAuth and is required, so the user must sign in and authorize access.
Before you install
Publishing and updating games writes content to a third-party hosted service, so anything published becomes visible to others through its URL. Player feedback is read from that service. Review what the assistant is allowed to publish or change before authorizing.

Installation

In SourceWeft

  1. Open Asobiai in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/games.asobiai%2Fasobiai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "asobiai": {
      "type": "http",
      "url": "https://asobiai.games/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 23, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.