Media

Audio BPM Transition Builder

Create a DJ-style, pitch-preserving speed ramp between two BPM values.

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'http://127.0.0.1:3003/api/upload/presign/audio-bpm-transition-builder' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"audioFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'http://127.0.0.1:3003/en/api/tools/audio-bpm-transition-builder' \
  -F 'audioFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'sourceBpm=120' \
  -F 'targetBpm=128' \
  -F 'transitionStartSec=0' \
  -F 'transitionDurationSec=4' \
  -F 'rampShape=linear' \
  -F 'rampResolution=detailed' \
  -F 'outputFormat=wav'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST http://127.0.0.1:3003/en/api/tools/audio-bpm-transition-builder

Parameters

Name	Type	Required	Description
audioFile	fileupload required	Yes	—
sourceBpm	number	Yes	—
targetBpm	number	Yes	—
transitionStartSec	number	Yes	—
transitionDurationSec	number	Yes	—
rampShape	select	Yes	—
rampResolution	select	Yes	—
outputFormat	select	Yes	—

File-type parameters must be uploaded first via POST /upload/audio-bpm-transition-builder, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-audio-bpm-transition-builder": {
      "name": "audio-bpm-transition-builder",
      "description": "Create a DJ-style, pitch-preserving speed ramp between two BPM values.",
      "baseUrl": "http://127.0.0.1:3003/mcp/sse?toolId=audio-bpm-transition-builder",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "audio-bpm-transition-builder",
    "arguments": {
  "audioFile": "https://example.com/file.ext",
  "sourceBpm": 120,
  "targetBpm": 128,
  "transitionStartSec": 0,
  "transitionDurationSec": 4,
  "rampShape": "linear",
  "rampResolution": "detailed",
  "outputFormat": "wav"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]