AutoRender MCP

io.github.autorenderPublished by GitHub account autorenderv0.1.0Updated Oct 24, 2026

AutoRender's MCP server for media assets, transformations, delivery, and workflow automation.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

AutoRender's remote MCP server gives an assistant access to media assets, transformations, delivery and workflow automation.

What you can do
Work with media assets managed in AutoRender, such as finding and handling stored files, based on the registry description. Apply transformations to media as part of a workflow. Handle delivery of media assets. Automate media-related workflows. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Consider it when your media assets live in AutoRender and you want an assistant to help with transformations, delivery or workflow automation around them. It is less useful if you do not already use AutoRender.
Requirements
A remote streamable HTTP endpoint at api-mcp.autorender.io. OAuth authentication is required, so you need an AutoRender account that can authorize the connection. No environment variables, headers or packages are declared.
Before you install
The server requires OAuth sign-in, which grants the assistant access to your AutoRender account; review the scopes requested during authorization. The description mentions transformations, delivery and workflow automation, which may change or publish media, so confirm before letting it act. No tool list is published, so the exact write operations are unknown.

Installation

In SourceWeft

  1. Open AutoRender 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 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/io.github.autorender%2Fautorender-mcp/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": {
    "autorender": {
      "type": "http",
      "url": "https://api-mcp.autorender.io/sse"
    }
  }
}

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. v0.1.0LatestSep 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.