StudioSphere Pulse — Audio Intelligence MCP server

Rights-aware audio intelligence over the Model Context Protocol.

BPM, musical key, and waveform peaks for authorized public audio URLs. Audio is

processed for analysis and not stored as user audio. Estimate before analysis,

try one short URL analysis before account setup, request a small evaluation

credit for qualified API/MCP workflow testing, then pay per second with no subscription.

Keywords: audio MCP · rights-aware audio intelligence · BPM detection · musical key detection · waveform analysis · music information retrieval · audio intelligence API · remote MCP server · REST API · Streamable HTTP transport · estimate before analysis · pay per second.

What it does

Pulse analyses authorized public audio URLs (or a direct upload, with an account) and returns structured metadata your AI assistant can act on. Shareable Google Drive, Dropbox, and other document-repository links work when the user has permission and the file is accessible to anyone with the link:

• BPM — tempo with confidence and beat count
• Musical key — root + scale (e.g. B minor) with confidence
• Waveform — peak-amplitude array suitable for visualization

Track structure segmentation and chord transcription are marked coming soon and are intentionally rejected by v1.0 routes.

Why creators and agents trust Pulse

Full transparency at .

For a short setup walkthrough, see docs/pulse-mcp-quickstart.md. For agent and builder scenarios, see docs/agent-playbook.md.

Service URLs

MCP client setup

The Pulse MCP server uses Streamable HTTP transport. Authentication is by Pulse API key passed as the api_key query parameter on the connection URL.

Claude Desktop

Open Settings → Developer → Edit Config, then merge:

Shortened. The full README is on GitHub.