Singing Pitch Tracker MCP Server

What the code does

We read the source, 4 d ago · rules ccca72095570

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        result = subprocess.run(

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        subprocess.run(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add pitch-mcp -- uvx pitch-mcp

{
  "mcpServers": {
    "pitch-mcp": {
      "args": [
        "pitch-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.pitch-mcp]
command = "uvx"
args = ["pitch-mcp"]

{
  "mcpServers": {
    "pitch-mcp": {
      "args": [
        "pitch-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "pitch-mcp": {
      "args": [
        "pitch-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: PITCH_BACKEND (Pitch detection algorithm: librosa (default) or crepe). The author declared them in the registry entry; get the values from the project itself.