Skip to main content
Glama

Barevalue MCP server

Barevalue edits podcast audio. Your agent hands over a raw recording and gets back a finished episode, with noise and levels fixed and filler words and dead air removed, plus a transcript, show notes and highlight clips for longer episodes.

One call to sign up, no sign-in, 10 free hours of editing a month, delivered at up to 320 kbps or lossless. No payment details, and the agent does not operate an editor.

https://barevalue.com/mcp

Streamable HTTP, nothing to install, no key needed to connect. The agent calls barevalue_register with your email address and gets a key in that one call.

Install

Client

One line

Claude Code

claude mcp add --transport http barevalue https://barevalue.com/mcp

Claude Code, with the skill

/plugin install barevalue --marketplace barevalue-ai/barevalue-mcp

Claude (web and desktop)

Settings, Connectors, Add custom connector, then paste https://barevalue.com/mcp/connect

Cursor

Add "barevalue": { "url": "https://barevalue.com/mcp" } under mcpServers in ~/.cursor/mcp.json

ChatGPT

With developer mode on, add a connector and paste https://barevalue.com/mcp/connect

Any agent that reads skills

npx skills add barevalue-ai/barevalue-mcp

A file on your own disk

claude mcp add barevalue -- npx -y barevalue-mcp (the npm bridge, below)

There are two addresses for the same server. https://barevalue.com/mcp is open: the agent registers itself and holds its own key. https://barevalue.com/mcp/connect asks you to sign in to your Barevalue account in a browser first, which is what the Claude and ChatGPT connector screens expect.

The Claude Code plugin line needs Claude Code 2.1.275 or later. On an earlier version, run claude plugin marketplace add barevalue-ai/barevalue-mcp and then claude plugin install barevalue@barevalue. The plugin adds the hosted server and the skill in skills/barevalue-podcast-editing, which teaches an agent the order of calls and what to do when one is refused. This repository is also a Cursor plugin (.cursor-plugin/plugin.json).

Cursor also takes an install link: cursor://anysphere.cursor-deeplink/mcp/install?name=barevalue&config=eyJ1cmwiOiJodHRwczovL2JhcmV2YWx1ZS5jb20vbWNwIn0=

Related MCP server: Retell AI MCP Server

The npm bridge, for a recording on your own machine

The hosted server takes a recording by link. For a file on disk it returns a curl command for the agent to run. The npm package barevalue-mcp does that step itself: barevalue_upload takes the path and sends the file.

You have

Use

A recording that already has a link

The hosted server, https://barevalue.com/mcp

A recording on this machine (Claude Code, Cursor, any local agent)

Either. With this package the agent has no command to run

The package is a bridge to the hosted server. Its tools come from the service (asked for when a client lists them, kept for five minutes), so they are always the current ones.

Claude Code:

claude mcp add barevalue -- npx -y barevalue-mcp

Or in any MCP client's configuration:

{
  "mcpServers": {
    "barevalue": {
      "command": "npx",
      "args": ["-y", "barevalue-mcp"]
    }
  }
}

Node 18 or later.

API key

If your email address has no Barevalue account yet, you do not need one to start. The agent calls barevalue_register with the address and gets a key in that one call, which this server keeps for the rest of the session. You get an email with a link: until you click it the account can edit 30 minutes, after it 10 hours a month.

If the address already has an account, barevalue_register is refused and you make the key yourself (Settings, API Keys on barevalue.com). Set it and the tools stop asking for one:

"env": { "BAREVALUE_API_KEY": "bv_sk_your_key_here" }

What to say

Edit the podcast episode at ~/recordings/ep42.wav with Barevalue. The show is "Tech Talk", the episode is "AI in 2026". Remove the sponsor read at the start.

The agent will:

  1. Upload the file (barevalue_upload)

  2. Order the edit (barevalue_submit_url)

  3. Check on it every minute or so until it is done (barevalue_status), usually 5 to 15 minutes

  4. Give you the download links, and the show notes and transcript as text (barevalue_content)

  5. Ask whether you are happy with it and pass that on (barevalue_feedback), or have it edited again with your notes (barevalue_request_revision)

Tools

The list comes from the service, so tools/list is the authority. Today:

Tool

What it does

barevalue_register

Create an account and get an API key in one call

barevalue_upload

Upload an audio file from this machine

barevalue_submit_url

Order editing, for an upload or for audio at a link

barevalue_status

Progress, time remaining, download links, what the edit changed

barevalue_content

Show notes, transcript and edit summary as text

barevalue_feedback

Say whether the edit was good

barevalue_request_revision

Have a finished order edited again with new instructions

barevalue_updates

Everything new on the account since the last call

barevalue_list_orders

Recent orders

barevalue_account

Minutes left this month and the pace limits

barevalue_estimate

Whether an order of a given length would be accepted

barevalue_validate

Pre-check audio at a link

barevalue_pricing, barevalue_api_status

Plans and current processing times

Limits

  • Audio only. One file per order, with one audio track, up to 60 minutes and 750 MB

  • MP3, WAV, M4A, FLAC, AAC, OGG, Opus, WMA and AIFF

  • The free plan edits one order at a time and 120 minutes in any 5 hours

  • An uploaded file can be ordered once, within 2 hours of the upload

Changes in 1.4.0

  • The tools now come from the hosted server. barevalue_submit (with order_id), the webhook tools and human editing are gone: the service retired them

  • barevalue_upload uses the new upload flow and returns an upload_id for barevalue_submit_url

  • BAREVALUE_API_KEY is optional

  • BAREVALUE_API_URL is no longer read

  • With BAREVALUE_API_KEY set, that key is the only one used: an api_key passed to a tool is ignored and barevalue_register does not replace it

  • barevalue_upload sends audio files only (by the real file's extension) and no call follows a redirect

Changes in 1.4.1

  • A BAREVALUE_API_KEY that cannot be a key (empty quotes, two layers of quotes, a quote that is not closed) stops the server at startup with one line that says how to set it. Before, the first ran without a key and the others got a 401 on every call

  • When the service refuses the key in BAREVALUE_API_KEY (revoked, expired, mistyped), the answer now says so and what to do: set a working key or remove the variable, then restart. That key is still the only one used. A key the session got from barevalue_register and that is later refused is dropped, so a working key can be passed as api_key (registering the same address again is refused: it has an account by then)

  • barevalue_upload sends the file only to Barevalue's own storage host. Any other upload address is refused before a byte is sent

  • A long upload reports progress to a client that asks for it (a progress token on the call), about once a second

  • Cancelling the call stops the upload, and so does the client going away. The same file asked for again reuses the upload it had been given, so retries do not use up the account's unordered uploads

  • A second barevalue_upload call for a file that is still on its way joins that upload and returns the same upload_id, in place of sending the file twice

  • A streamed answer from the service is read correctly when it carries other messages or stays open after the answer

  • barevalue_upload opens the file once and sends what it checked, so a file swapped in afterwards is not sent. A file with more than one name on disk (a hard link) is refused: copy it and upload the copy. A file the program may not read is refused in plain words

Changes in 1.4.2

  • An upload no longer waits for ever when storage sends the start of an answer and then drops the connection. The call is answered with the reason, the file is closed, and the same file asked for again goes to the upload it had been given. An upload that goes quiet for 120 seconds is stopped the same way. A yes from storage that comes before the whole file was sent no longer counts as an upload

  • barevalue_submit_url sends an idempotency key. An order that got no answer (a timeout, a broken connection) and is asked for again with the same arguments within 30 minutes goes out with the same key, so it is not placed twice. The timeout message says so. When the answer is that earlier order, it says so and what became of it. If it failed, the same call once more places a new order. If it is being edited or done, the same call keeps giving that order, and a second order of the same recording takes an idempotency_key of your own. An idempotency_key you pass yourself is sent as given

  • barevalue_upload lists api_key like the other tools while the session has no key. It always took one

  • The texts about barevalue_register no longer promise a key to an address that already has an account: that call is refused, and the key comes from Settings, API Keys

Changes in 1.4.3

  • The program is the same as 1.4.2. On the service's side, a file longer than 60 minutes is now refused before any editing and uses none of the allowance. Before, one could be accepted and fail part-way

  • The package now names its repository, barevalue-ai/barevalue-mcp, and this page leads with the hosted server and how to add it to each client

  • The repository is a Claude Code plugin and a Cursor plugin, and the skill names the second address, https://barevalue.com/mcp/connect

Development

npm install
npm run build
node test-mcp.js                                   # live read-only smoke test, then the local tests; no key needed
node test-mcp.js --offline                         # the local tests only, against a stub inside the test
BAREVALUE_API_KEY=... node test-mcp.js episode.mp3 # also uploads the file, places no order

Support

support@barevalue.com, the developer page or the API documentation, which is also plain markdown at https://barevalue.com/llms-full.txt.

License

MIT

Available Tools

13 tools
barevalue_accountAInspect

Get Barevalue account information including credit balance, AI subscription status, bonus minutes, and pricing. Use this to check available balance before submitting orders.

Inputs: no named parameters.

barevalue_estimateAInspect

Calculate the cost of an AI podcast editing order before submission. Returns breakdown of AI bonus minutes, subscription minutes, credits, and payment required.

Inputs: duration_minutes (required).

barevalue_list_ordersBInspect

List recent orders with their status. Useful for checking on multiple orders or finding a specific order.

Inputs: page, per_page, status.

barevalue_statusAInspect

Check the status of an order. Returns current processing state and, when complete, download URLs for edited audio, transcript PDF, transcript DOCX, and show notes.

Inputs: order_id (required).

barevalue_submitAInspect

Submit an uploaded audio file for AI podcast editing. Charges credits/subscription minutes. Requires order_id and s3_key from barevalue_upload.

Inputs: order_id (required), s3_key (required), podcast_name (required), episode_name (required), +5 more.

barevalue_submit_urlAInspect

Submit a podcast for AI editing using a public URL. The file will be downloaded and processed. Useful for files hosted on Dropbox, Google Drive (with public link), or other file hosting services.

Inputs: file_url (required), podcast_name (required), episode_name (required), episode_number, +4 more.

barevalue_uploadAInspect

Upload an audio file for AI podcast editing. Handles getting a presigned S3 URL and uploading the file. Returns order_id and s3_key needed for submission. Maximum file size: 750MB.

Inputs: file_path (required), filename.

barevalue_validateAInspect

Pre-check an audio file from a URL before submission. Validates speech content (minimum 10%) and detects music-only content. Does NOT charge credits. Use this for external URLs before submitting. Note: For files uploaded via barevalue_upload, validation is not needed - go directly to submit.

Inputs: file_url (required).

barevalue_webhook_createBInspect

Create a new webhook to receive notifications. Returns the webhook with its signing secret (shown only once - save it!).

Inputs: url (required), events (required).

barevalue_webhook_deleteAInspect

Delete a webhook. This cannot be undone.

Inputs: webhook_id (required).

barevalue_webhook_rotate_secretAInspect

Generate a new signing secret for a webhook. The old secret will immediately stop working. Returns the new secret (shown only once).

Inputs: webhook_id (required).

barevalue_webhooks_listAInspect

List all configured webhooks for your account. Webhooks send notifications when orders complete, fail, or are refunded.

Inputs: no named parameters.

barevalue_webhook_updateCInspect

Update an existing webhook URL, events, or active status.

Inputs: webhook_id (required), url, events, is_active.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. For example, barevalue_upload handles file uploads, barevalue_submit processes uploaded files, and barevalue_submit_url handles URL-based submissions, all targeting specific workflow steps. The webhook tools (create, delete, rotate_secret, list, update) are also well-differentiated, covering distinct CRUD operations.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with the 'barevalue_' prefix, such as barevalue_account, barevalue_estimate, and barevalue_list_orders. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 13 tools, the count is well-scoped for the AI podcast editing domain. It covers core operations (upload, submit, status), support functions (account, estimate, validate), and webhook management, ensuring each tool earns its place without being overwhelming or insufficient.

    Completeness5/5

    The tool set provides complete coverage for the podcast editing workflow, including file handling (upload, submit via URL), order management (list, status), cost estimation, account checks, and full webhook CRUD operations. There are no obvious gaps, as all essential lifecycle stages from pre-submission to post-processing are addressed.

    Related MCP Connectors

    Related MCP Servers