Cassette Publish

gg.cassettePublished by cassette.ggOfficial publisherv1.0.0Updated Nov 5, 2026

Publish a browser game to Cassette from your coding agent. OAuth sign-in; a person approves.

The publisher's own server: Cassette Game Finder

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets a coding agent publish a browser game to Cassette, with OAuth sign-in and a person approving the action.

What you can do
  • Publish a browser game from a coding agent to Cassette.
  • Sign in through OAuth, with a person approving the connection.
  • No tool list is published, so the exact publishing steps are not documented here.
When to use it
Use it when you build a browser game with an AI coding agent and want to ship it to Cassette without leaving the agent workflow.
Requirements
A remote MCP endpoint at cassette.gg over streamable HTTP. OAuth authentication is required, and a person must approve the sign-in. No environment variables or headers are declared.
Before you install
Publishing pushes content to a live Cassette account, so review what the agent will upload before approving. Access is granted through OAuth sign-in that a person must approve; only approve it for agents you trust.

Installation

In SourceWeft

  1. Open Cassette Publish 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/gg.cassette%2Fpublish/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": {
    "cassette-publish": {
      "type": "http",
      "url": "https://cassette.gg/mcp/publish"
    }
  }
}

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.0LatestNov 5, 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.

Other Cassette integrations