Sloosh

ai.slooshPublished by sloosh.aiOfficial publisherv0.1.0Updated Nov 5, 2026

Generate images and video, run Spaces and build canvases from your agent. OAuth sign-in.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant generate images and video, run Spaces and build canvases through an OAuth-signed-in Sloosh account.

What you can do
  • Generate images and video from the assistant.
  • Run Spaces.
  • Build canvases.
  • No tool list is published, so exact operations are not documented here.
When to use it
Useful when you want an assistant to produce visual media or assemble canvas-style work inside Sloosh without leaving the chat, and you already have or are willing to create a Sloosh account.
Requirements
A remote streamable HTTP endpoint at mcp.sloosh.ai; no local package or environment variables. OAuth sign-in with a Sloosh account is required.
Before you install
Sign-in is via OAuth, so the server receives access to your Sloosh account; review the scopes granted. Generation and canvas actions may create content or consume account resources, and no tool list is published to confirm what is written or changed.

Installation

In SourceWeft

  1. Open Sloosh 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/ai.sloosh%2Fsloosh/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": {
    "sloosh": {
      "type": "http",
      "url": "https://mcp.sloosh.ai/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. v0.1.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.