MAJR Media Encoding

io.github.majrdotappPublished by GitHub account majrdotappv1.3.2Updated Oct 24, 2026

Encode uploads to web-ready media: video to HLS, audio to AAC, images to WebP. Async jobs.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant encode uploaded media into web-ready formats: video to HLS, audio to AAC, images to WebP, as async jobs.

What you can do
  • Encode uploaded video into HLS for streaming playback
  • Transcode uploaded audio into AAC
  • Convert uploaded images into WebP
  • Run encoding as asynchronous jobs and track their progress
When to use it
Use it when an assistant needs to prepare media for the web — turning source video, audio or images into streaming or compressed delivery formats — without running local encoding tools.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime. A MAJR API key is required, sent as a bearer token in the Authorization header; keys are described as free and instant from the provider.
Before you install
The Authorization header carries a secret API key, so keep it out of logs and shared transcripts. Uploaded media is sent to a third-party encoding service, so avoid confidential or personal content unless that is acceptable. Encoding jobs write and transform files on the remote service.

Installation

In SourceWeft

  1. Open MAJR Media Encoding in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.majrdotapp%2Fmedia-encoding/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.

{
  "mcpServers": {
    "majr-media-encoding": {
      "type": "http",
      "url": "https://encoding.majr.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.3.2LatestSep 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.