WaveForge

net.waveforgePublished by waveforge.netOfficial publisherv1.0.1Updated Nov 5, 2026

Audio-reactive music visualizer: turn a track and cover art into a music video.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that turns an audio track and cover art into an audio-reactive music video, using a WaveForge API key.

What you can do
  • Generate music videos from a track and cover art, with visuals reacting to the audio.
  • No tool list is published, so the exact operations are not documented; the server is described only as an audio-reactive music visualizer.
  • Renders are tied to a WaveForge account and its API keys, which distinguish test renders from paid live renders.
When to use it
Worth adding when you want an assistant to produce music videos or visualizer renders from audio and artwork without leaving the chat, and you already have or can create a WaveForge account.
Requirements
Remote streamable HTTP endpoint at waveforge.net; no local package or runtime needed. A WaveForge API key created in the dashboard, sent as a bearer token in the Authorization header. A test key (wf_test_ prefix) or a live key (wf_live_ prefix) determines whether renders are free tests or paid.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared transcripts. Live keys spend real money on video renders, so start with a test key. Uploaded audio and cover art are sent to a third-party service, and renders may be created or stored on your WaveForge account.

Installation

In SourceWeft

  1. Open WaveForge 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/net.waveforge%2Fwaveforge/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": {
    "waveforge": {
      "type": "http",
      "url": "https://waveforge.net/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Nov 4, 2026

Score

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

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