Hiroska

com.hiroskaPublished by hiroska.comOfficial publisherv1.0.0Updated Oct 26, 2026

AI video studio: generate with 80+ AI models, edit on a timeline and export 4K, from an assistant.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Hiroska is a remote AI video studio MCP server that lets an assistant generate video with 80+ AI models, edit on a timeline and export in 4K.

What you can do
  • Generate video with a large library of AI models
  • Edit generated clips on a timeline
  • Export finished work in 4K
  • Connect an assistant to a hosted video studio over a remote endpoint
When to use it
Useful when you want an assistant to produce or revise AI-generated video without leaving the chat, for example drafting clips from prompts, arranging them on a timeline and exporting a final cut.
Requirements
A remote MCP endpoint at hiroska.com over streamable HTTP. Authentication is required: OAuth sign-in, or an Authorization header carrying a bearer API key from the account's Connected AI settings for clients without OAuth. A Hiroska account is implied.
Before you install
The server requires account credentials: either OAuth sign-in or an Authorization bearer API key, which should be treated as a secret. Generation and export likely consume paid account resources, though the input does not state pricing. Prompts and media are sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Hiroska 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/com.hiroska%2Fhiroska/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": {
    "hiroska": {
      "type": "http",
      "url": "https://hiroska.com/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 22, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.