StudioSphere Pulse

Privacy-first audio intelligence over the Model Context Protocol. BPM, musical key, and waveform peaks for any public audio URL. Audio is processed in memory and never stored. Pay-per-second, no subscription.

Keywords: audio MCP · BPM detection · musical key detection · waveform analysis · music information retrieval · audio intelligence API · remote MCP server · Streamable HTTP transport.

What it does

Pulse analyses any public audio URL (or a direct upload, with an account) and returns structured metadata your AI assistant can act on:

• BPM — tempo with confidence and beat count, time-signature inference
• 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 https://pulse.studiosphere.space/terms.

For a short setup walkthrough, see docs/pulse-mcp-quickstart.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:

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

Restart Claude Desktop.

Claude Code (CLI)

claude mcp add --transport http studiosphere-pulse \
  https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

Verify with claude mcp list.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

ChatGPT

The Pulse server speaks Streamable HTTP at https://mcp.studiosphere.space/mcp. Add it via whichever connector / GPT-action surface your account exposes; supply the API key as the api_key query parameter.

Get an API key

Register at https://pulse.studiosphere.space/signup. Keys begin with sk_pulse_ and are shown once — store them in a password manager.

The hosted /connect page (https://pulse.studiosphere.space/connect) generates the per-client config snippet with your key stamped in for one-click copy.

Tools available to the assistant

Workflow agents should follow

1. Call estimate_cost with the audio URL and selected tools.
2. Show the user the returned cost_display and duration_estimate_sec.
3. Confirm the user has the right to submit the audio.
4. Call analyze_track (banked tokens) or request_payment_link (anonymous one-time payment).
5. Poll get_job_status until terminal (completed, partial, failed).
6. Surface the result.

Pricing is per-second of audio analyzed × per-tool multiplier. Banked-token pricing skips the $0.50 Stripe minimum and the per-job Checkout redirect.

Why agents use Pulse

• Sample-pack tagging and search
• DAW / session preparation
• Remix and mashup compatibility checks
• Licensed music-library enrichment
• Sync and catalog metadata workflows
• Content-creator music selection from approved libraries

Agents must only submit audio when the user confirms rights to analyze it. The analyze_track tool requires an explicit attestation_confirmed: true for this reason.

Repository scope

This repository contains only public-facing documentation, registry metadata, and client examples. It does not contain production service source code, deployment configuration, credentials, private infrastructure notes, migrations, or internal operational documentation.

Security

Do not send private, copyrighted, or third-party audio unless you have the right to submit it for analysis. Do not publish Pulse API keys in client configs, prompts, logs, or issue reports.

Security questions: pulse@studiosphere.space.

License

See LICENSE in this repository. Pulse is operated by StudioSphere Inc., Quebec, Canada.