Remote MCP

Audio MCP Server for AI Assistants

Use Pulse when an assistant needs audio intelligence tools without building or hosting a local audio-analysis stack.

Who this is for

What Pulse returns

  • estimate_cost
  • analyze_track
  • request_payment_link
  • get_job_status
  • token-pack and account helper tools

Example workflow

Connect the Streamable HTTP MCP endpoint, give the assistant a Pulse API key or payment flow, require rights confirmation, and have the assistant estimate before analysis.

Pricing and estimates

Estimates are free before paid analysis, and first-time users can try one short URL analysis before account setup. Pulse prices selected tools by audio duration using the same tool multipliers exposed by /tools: waveform 0.3 tokens/second, BPM 0.5 tokens/second, and key 0.5 tokens/second. The current token price is $0.005.

60 second bpm, key, waveform example78 tokens$0.39
3 minute full v1.0 suite234 tokens$1.17
Cached resultMay cost less$0.001 current cache-hit price

Examples are illustrative. The final estimate is shown before payment or API-key analysis and may account for selected tools, measured duration, cached analysis, failed tools, and checkout-path constraints.

Rights-aware analysis boundary

Pulse is designed for audio the user has rights, permission, lawful access, or another legal basis to submit. Agents and apps should confirm that before analysis. Pulse does not provide transcription, stem separation, mastering, loudness correction, chord transcription, or track structure segmentation in v1.0.

Pulse is designed to make audio analysis auditable. Each analysis flow should make clear which URL was submitted, which tools were selected, what the estimate was, when rights confirmation was given, and whether the job completed, partially completed, failed, or expired.

Related Pulse resources

MCP setup · API docs · Agent playbook · Terms