Orcool Studio MCP

io.github.ryss30Published by GitHub account ryss30v1.0.1Updated Oct 24, 2026

AI tools for mobile app ad production: concepts, avatars, video rendering, performance feedback.

VerifiedSSEWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

A remote MCP server that gives an assistant AI tools for producing mobile app ad creatives, including concepts, avatars, video rendering and performance results

What you can do
Orcool Studio MCP is a hosted endpoint that exposes AI tools for mobile app advertising production. According to its description, it covers ad concepts, avatars, video rendering and performance feedback. No individual tool names or parameters are published, so the exact operations are not documented here.
When to use it
Consider it when you are producing ad creatives for a mobile app and want an assistant to help with concepts, avatar assets, rendered video, or reviewing how ads performed.
Requirements
A remote SSE endpoint at mcp.orcool.com. OAuth authentication is required, so you need an Orcool account or equivalent authorization. No environment variables or headers are declared.
Before you install
The server is hosted by a third party, so anything you submit for ad production is sent to that provider. It requires OAuth sign-in, which grants it access under the scopes you approve. Tool behavior, data retention and any costs are not described in the available information.

Installation

In SourceWeft

  1. Open Orcool Studio MCP 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 SSE. 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/io.github.ryss30%2Forcool-studio/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": {
    "orcool-studio": {
      "type": "sse",
      "url": "https://mcp.orcool.com/"
    }
  }
}

README

This repository has no README.

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.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.