MixMake

io.github.swappyshPublished by GitHub account swappyshv1.0.0Updated Oct 24, 2026

Transcript-based audio editing: transcribe audio, edit by word ID, export edited audio.

The publisher's own server: Make

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Lets an assistant transcribe audio, edit the transcript by word ID, and export the edited audio.

What you can do
MixMake is a remote MCP server for transcript-based audio editing. According to its description, it transcribes audio, lets edits be made by word ID, and exports the edited audio. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Consider it when you want an assistant to work with spoken audio through its transcript rather than a waveform editor, for example cutting, reordering, or removing words and then exporting the result. It is a hosted endpoint, so nothing needs to be installed locally.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's endpoint. No local runtime or package is declared. An optional API key is supplied in the X-Mixmake-Api-Key header for higher daily limits; without it, lower limits apply.
Before you install
The optional X-Mixmake-Api-Key header carries a secret, so keep it out of shared logs and configuration. Editing and exporting produce changed audio, so review the output before relying on it. Audio you submit is processed by a third-party hosted service, which may retain or handle it under its own terms.

Installation

In SourceWeft

  1. Open MixMake in the dashboard and add it to a workspace.
  2. 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.swappysh%2Fmixmake/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": {
    "mixmake": {
      "type": "http",
      "url": "https://mixmake.com/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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

Other Make integrations