Barevalue

What Barevalue does

The Barevalue MCP server connects agents to Barevalue’s podcast editing service, which processes raw recordings and returns a finished episode. Editing can fix noise and levels, remove filler words and dead air, and produce a transcript, show notes, and an edit summary. Longer episodes may also receive highlight clips.

The service is intended for the 🎙️ Podcasts category and supports an end-to-end order flow: register or authenticate, provide audio, submit editing instructions, monitor progress, retrieve results, and request another pass when needed. Agents can also report whether an edit was satisfactory.

How it works

The hosted server is available over Streamable HTTP at https://barevalue.com/mcp. An agent can register with an email address through barevalue_register; for a new account, the response includes an API key that the server retains for the session. An existing account requires an API key created in Barevalue account settings.

Audio can be submitted by URL with barevalue_submit_url. For recordings stored on the agent’s machine, the barevalue-mcp npm package acts as a local bridge and provides barevalue_upload, which sends the file to Barevalue storage before the order is placed.

A typical workflow uploads or references the recording, submits editing instructions, checks barevalue_status until processing finishes, and reads the resulting download links and text content. barevalue_content returns the transcript, show notes, and edit summary. If the result needs changes, barevalue_request_revision accepts new instructions for a finished order.

Setup and configuration

For a hosted connection, configure an MCP client with https://barevalue.com/mcp. This endpoint lets the agent register itself and manage its session key. The /mcp/connect endpoint uses browser sign-in first and is intended for connector interfaces that expect an authenticated account.

For local files, configure the client to run npx -y barevalue-mcp. Node.js 18 or later is required for this bridge. Claude Code can add it with claude mcp add barevalue -- npx -y barevalue-mcp; other MCP clients can use the same command and arguments in their server configuration.

Set BAREVALUE_API_KEY when an existing account key should be used. It is optional for initial registration. When set, the configured key is the only key used, and an invalid value stops startup or produces an authentication error that requires replacing or removing the variable before restarting.

Tools and capabilities

The available tools include:

• barevalue_register for creating an account and obtaining a key.
• barevalue_upload and barevalue_submit_url for supplying recordings.
• barevalue_validate for checking audio at a URL before ordering.
• barevalue_estimate for checking whether an order length will be accepted.
• barevalue_status for progress, remaining time, download links, and edit changes.
• barevalue_content for transcripts, show notes, and summaries.
• barevalue_feedback and barevalue_request_revision for post-edit responses.
• barevalue_updates, barevalue_list_orders, and barevalue_account for account activity, order history, and remaining minutes or pace limits.
• barevalue_pricing and barevalue_api_status for plan and processing information.

Limitations and notes

Each order contains one audio file and one audio track. Files can be up to 60 minutes and 750 MB, using supported formats including MP3, WAV, M4A, FLAC, AAC, OGG, Opus, WMA, or AIFF. The free plan permits one active order and limits processing to 120 minutes within five hours; a new account can edit 30 minutes until its email link is confirmed, then receives 10 free hours per month.

An uploaded file must be ordered within two hours and can only be ordered once. The Barevalue MCP server does not provide a local audio editor; it submits work to the service and returns the resulting assets and text. The hosted service uses links, while local-file handling depends on the npm bridge.