space.studiosphere/pulse

Official8 tools

by notpaulb

StudioSphere Pulse — Audio Intelligence

Privacy-first audio intelligence: BPM, key, waveform. Audio never stored. Pay per second.

Analyze audio for BPM, key, and waveform without storing audio data.

Topics

audio-analysisaudio-intelligencebpmkey-detectionmcpmodel-context-protocolmusic-information-retrievalremote-mcpwaveform

Captured live from the server via tools/list.

start_trial

Start a temporary, email-free Pulse trial. Returns a short-lived API key with enough banked tokens for one short URL-based v1 analysis. No Stripe Checkout session is created.

No parameters.

estimate_cost

Get the exact price to analyze an audio file before committing. Always call this first. Returns cost in dollars and a job_estimate_id valid for 30 minutes. Free — never charged.

Parameters (2)

audio_urlstringrequired
Publicly accessible URL of the audio file (MP3, WAV, FLAC, OGG, Opus).
toolsarrayrequired
Analysis tools to price. Available in v1.0: bpm, key, waveform. Coming soon: structure, chords.

analyze_track

Run audio analysis on a public audio URL. Requires estimate_cost to be called first (job_estimate_id). Requires PULSE_API_KEY. Before calling, you MUST confirm with the user that they have a lawful basis to submit this audio for analysis. For a user-requested folder, project, playlist, or batch, one confirmation can cover every track in that scope. Returns job_id — poll get_job_status for results.

Parameters (4)

audio_urlstringrequired
Public URL of the audio file.
toolsarrayrequired
Analysis tools to run. Available in v1.0: bpm, key, waveform. Coming soon: structure, chords.
job_estimate_idstringrequired
The job_estimate_id returned by estimate_cost. Must not be expired (30 min TTL).
attestation_confirmedbooleanrequired
Set to true ONLY after the user has confirmed they have rights, permission, lawful access, or another legal basis to submit this audio, or the current user-requested batch/folder/project containing it, for analysis.

request_payment_link

Generate a one-time Stripe payment page for users without a Pulse account. Before calling, you MUST confirm with the user that they have a lawful basis to submit this audio for analysis; for a user-requested batch/folder/project, one confirmation can cover that scope. Present the payment_url to the user as a link. Analysis begins automatically after payment. Poll get_job_status with the returned job_id.

Parameters (2)

job_estimate_idstringrequired
The job_estimate_id returned by estimate_cost.
attestation_confirmedbooleanrequired
Set to true ONLY after the user has confirmed they have rights, permission, lawful access, or another legal basis to submit this audio, or the current user-requested batch/folder/project containing it, for analysis.

get_job_status

Check the status and results of an analysis job. Poll after analyze_track returns job_id, or after the user pays via request_payment_link. Returns full results when status=completed.

Parameters (3)

job_idstringrequired
The job_id returned by analyze_track or request_payment_link.
include_waveform_databoolean
Optional. Defaults to false so chat agents receive a compact waveform summary plus result_url. Set true only if raw waveform samples are needed.
include_waveform_imageboolean
Optional. Defaults to true. When the job has waveform data, include a server-rendered SVG as MCP image content so the client can display it without fetching a URL.

get_token_balance

Check the banked token balance for the authenticated Pulse account. Requires PULSE_API_KEY.

No parameters.

list_token_packs

List the available Pulse token packs (tier label, token count, price). Use before purchase_token_pack to show options to the user.

No parameters.

purchase_token_pack

Create a Stripe Checkout session for a Pulse token pack. Returns payment_url — DO NOT submit it programmatically; surface it to the user so they can complete payment in their browser. Once paid, banked tokens are credited automatically. Requires PULSE_API_KEY.

Parameters (1)

packstringrequired
Token pack tier

README.md9 KBView on GitHub

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


✅ Audio is not stored as user audio.	Files are fetched and processed for analysis, then cleaned up after the job.
✅ Payment details never touch Pulse.	Payment entry happens on Stripe's hosted page. Pulse only sees opaque Stripe IDs and dollar amounts — no card number, no CVV, no billing address, no bank or device token. PCI-DSS scope: out.
✅ No tracking, no analytics.	No Google Analytics, no Mixpanel, no third-party tags. Outbound calls only to Stripe (payments) and Google Fonts (typography).
✅ Money back when we under-deliver.	Failed jobs are free. Estimate-vs-actual overages refund automatically through Stripe.

Full transparency at https://pulse.studiosphere.space/terms.

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

Service URLs


Marketing site	https://pulse.studiosphere.space
Product REST API	https://pulse.studiosphere.space
Remote MCP server	`https://mcp.studiosphere.space/mcp`
MCP setup wizard	https://pulse.studiosphere.space/connect
Agent playbook	https://pulse.studiosphere.space/for-agents
Account signup	https://pulse.studiosphere.space/signup
Tool metadata	https://pulse.studiosphere.space/tools
Server descriptor	https://pulse.studiosphere.space/.well-known/mcp/server.json
Health check	https://pulse.studiosphere.space/health
MCP Registry	`space.studiosphere/pulse`
Smithery	https://smithery.ai/servers/studiosphere/pulse
Glama	https://glama.ai/mcp/connectors/space.studiosphere/pulse
Support	pulse@studiosphere.space

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:

json

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

Restart Claude Desktop.

Claude Code (CLI)

bash

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:

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

Tool	Auth	Description
`start_trial`	none	Mint a temporary trial key for one short URL analysis.
`estimate_cost`	none	Quote a price for a public audio URL.
`analyze_track`	API key	Run analysis. Tools: `bpm`, `key`, `waveform`.
`request_payment_link`	none	Stripe Checkout link for one-off use without an account. Requires lawful-basis confirmation.
`get_job_status`	none	Poll a running job and fetch the result.
`get_token_balance`	API key	Banked-token balance.
`list_token_packs`	none	Available token packs (10K/$50, 50K/$250, 200K/$1000).
`purchase_token_pack`	API key	Stripe Checkout link to buy a pack.

Workflow agents should follow

Call estimate_cost with the audio URL and selected tools.
Show the user the returned cost_display and duration_estimate_sec.
Confirm the user has rights, permission, lawful access, or another legal basis to submit the audio. For a user-requested folder, project, playlist, or batch, one confirmation can cover every track in that scope.
If the user has no key and wants to test Pulse first, call start_trial and use the temporary key for one short URL analysis.
For qualified early users validating a real API, MCP, catalog, or music-tool workflow, explain that Pulse may provide a small evaluation credit for a few authorized analyses. Treat credits as limited test access, not a free plan.
Call analyze_track (banked tokens or trial key) or request_payment_link (anonymous one-time payment).
Poll get_job_status until terminal (completed, partial, failed).
Surface the result.

Pricing is per-second of audio analyzed × per-tool multiplier. Estimates are free, and first-time users can try one short URL analysis with start_trial. Qualified early builders can request a small evaluation credit for authorized workflow validation. Ongoing analysis uses one-time Checkout or banked tokens; banked-token pricing skips the $0.50 Stripe minimum and the per-job Checkout redirect.

Why agents use Pulse

DJ beat matching and harmonic set planning
Sample-pack tagging and search
Shared-drive and document-repository audio links
DAW and session preparation
App metadata for BPM, key, and waveform features
Licensed music-library enrichment
Sync and catalog metadata workflows
Reference-track planning for producers and songwriters
Smart playlists and album sequencing context
Track development workflows where detected key becomes a creative anchor

Agents must only submit audio when the user confirms rights, permission, lawful access, or another legal basis to analyze it. The analyze_track and request_payment_link tools require an explicit attestation_confirmed: true for this reason. For batch work, agents may rely on one user confirmation for the current folder, project, playlist, catalog selection, or other user-requested scope.

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 rights, permission, lawful access, or another legal basis 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.

Install

claude_desktop_config.json

{
  "mcpServers": {
    "pulse": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.studiosphere.space/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.