Cleanvoice

ai.cleanvoicePublished by cleanvoice.aiOfficial publisherv1.0.0Updated Oct 29, 2026

Remove noise, cut filler words and add Studio Sound to audio and video, with transcripts.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Cleanvoice MCP lets an assistant clean up audio and video: remove noise, cut filler words, add Studio Sound, and get transcripts.

What you can do
  • Clean up audio and video by removing background noise and filler words.
  • Apply Studio Sound processing to recordings.
  • Produce transcripts alongside the processed media.
  • No individual tools are listed, so the exact operations are not documented in the supplied material.
When to use it
Useful when you want an assistant to tidy up podcast episodes, interviews, voice recordings or video before publishing, and to get a transcript at the same time.
Requirements
A remote MCP endpoint at api.cleanvoice.ai over streamable HTTP. Authentication is required: OAuth sign-in with a Cleanvoice account, or an API key sent in the X-API-Key header for headless setups, obtained from the Cleanvoice app site.
Before you install
Processing sends your audio and video to Cleanvoice's cloud service, so consider whether the recordings are sensitive. The API key is a secret; keep it out of shared logs and configuration. Media processing may consume paid account credits, which the supplied material does not clarify.

Installation

In SourceWeft

  1. Open Cleanvoice 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/ai.cleanvoice%2Fcleanvoice/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": {
    "cleanvoice": {
      "type": "http",
      "url": "https://api.cleanvoice.ai/mcp"
    }
  }
}

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.0LatestOct 29, 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.