StudioSphere Pulse — Free Loops and Audio Intelligence MCP

MCP serverMedia

Pulse adds audio analysis to your AI, so it can read the tempo, musical key, and waveform of any audio file you share. Audio is never stored, and you are billed by the second.

Then ask your AI: use StudioSphere Pulse to start trial

Details

Available today. Use it as a step in a pipeline you build, or from your connected AI.

Add Pulse, then share an audio file and ask for its tempo, key, or waveform. You are billed by the second for the audio you analyze.

What your AI can do with it

  • Detect the tempo of a track in beats per minute
  • Identify the musical key of a song
  • Get waveform data from an audio file
  • Analyze audio without the file ever being stored
  • Compare several tracks by tempo or key

Install StudioSphere Pulse — Free Loops and Audio Intelligence MCP

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user studiosphere-pulse-free-loops-an 'https://mcp.studiosphere.space/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://mcp.studiosphere.space/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=studiosphere-pulse-free-loops-an&config=eyJ1cmwiOiJodHRwczovL21jcC5zdHVkaW9zcGhlcmUuc3BhY2UvbWNwIn0=

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://mcp.studiosphere.space/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add studiosphere-pulse-free-loops-an --url 'https://mcp.studiosphere.space/mcp'

    Run it once, then sign in with codex mcp login studiosphere-pulse-free-loops-an if the server asks for an account.

From the project's README

As published by notpaulb/studiosphere-pulse-mcp in README.md.

Discover free, licensed loops and analyze authorized audio for BPM, musical key and waveform data. Start with free discovery and see estimated costs before paid analysis.

Pulse · Connection guide · Open Loops · Quickstart

Start without an account

Try the anonymous browser demonstration on the connection guide: search one CC0 loop, retrieve its licence and source credit, then preview or download it. No key, account, analysis job or payment is created. This is a browser demonstration, not assistant-host certification.

Connect anonymously using Streamable HTTP:

https://mcp.studiosphere.space/mcp

The product-domain MCP entry leads to the human /connect instructions; it is not the protocol endpoint.

Ask your assistant:

Use Pulse to search for five free licensed loops. Get one with get_open_loop and show its preview, download, exact license and attribution. Do not create a key, account, analysis job or payment link.

Call search_open_loops, then get_open_loop with a returned pol_id. Retain the license, license URL and attribution with the sample. Follow each sample's terms; CC-BY samples require credit. Free discovery costs no tokens. Sample tags are creator hints; BPM and musical key are estimates requiring review.

Connection examples and host limits

Claude remote connector: use Customize → Connectors → Add custom connector, enter StudioSphere Pulse and the anonymous URL above, choose No sign in, and enable the connector in the conversation. Labels and organization permissions can vary. Use the remote interface rather than local Desktop JSON configuration. See Claude's instructions.

Claude Code: the quoted URL also works with zsh query characters:

claude mcp add --transport http studiosphere-pulse 'https://mcp.studiosphere.space/mcp'
claude mcp list

This follows Claude Code HTTP setup; it is not an actual Claude Code test result.

Cline: follow Cline MCP setup, with an anonymous remote configuration:

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "streamableHttp",
      "url": "https://mcp.studiosphere.space/mcp"
    }
  }
}

ChatGPT: where custom MCP connections are available, the public URL with No authentication is the candidate discovery setup. ChatGPT cannot present custom Pulse API keys, and Pulse does not implement OAuth. Authenticated ChatGPT use is not supported by the current authentication boundary. See OpenAI's custom MCP guide and auth requirements.

Actual Claude, ChatGPT, Cline and Smithery host onboarding has not been tested. HTTP/SDK tests are protocol evidence, not host certification or directory approval. Paid compatibility is unverified; a public tool scan does not validate it.

Ten tools

ToolKey neededBehavior
search_open_loopsNoSearch free licensed samples.
get_open_loopNoExact license, attribution, preview and download.
estimate_costNoFree estimated cost/duration and quote ID.
start_trialNoCreates a private temporary key; reconnect before use.
analyze_trackYesSubmit authorized audio for BPM/key estimates and waveform.
request_payment_linkNoCreates one-off Checkout after rights confirmation; human completes payment.
get_job_statusNoJob status, results and review notes.
get_token_balanceYesPrivate account/trial balance and allowance.
list_token_packsNoCurrent tiers, including Starter.
purchase_token_packYesCreates Checkout to fund an account; human completes payment.

structure and chords are coming soon and unavailable. This public repository contains documentation and metadata, not the production implementation.

Optional authorized audio trial

Create credentials only with the human's approval. First-time users can call start_trial for a private temporary key. End the anonymous connection and reconnect to initialize with that key in a trusted key-aware client. Authentication is bound at initialization; adding a key to a later request does not upgrade an existing session.

https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

This private URL illustrates the current transport, not universal host support. Quote it in shell commands. Query credentials can leak through client configuration, history or logs; never put real keys in shared prompts, screenshots, issues or version control. Pulse's MCP boundary does not support OAuth or bearer authentication. The REST API's Bearer support is a different interface.

Read get_token_balance for the per-key allowance. The October 7 live default is 78 tokens, up to 300 seconds, 24-hour expiry, one completed/partial URL analysis, at most two queued attempts if the first fails. Read live /tools and the returned allowance because configuration can differ. Remaining tokens do not grant a second song; no ongoing free tier is promised.

Authorized first-party example: Copper Step CC0 MP3, 180 seconds; CC0 provenance.

  1. Call estimate_cost with that URL and selected tools; review cost and duration.
  2. Confirm rights, permission, lawful access or another legal basis to submit the audio.
  3. Call analyze_track with the quote ID and attestation_confirmed: true.
  4. Poll get_job_status; review BPM/key estimates and confidence notes.

If interrupted, retain the private key/job ID, reconnect and poll before retrying. Do not mint another key or resubmit an uncertain job. If pricing changes, request a fresh free estimate and obtain approval again before processing or payment.

Estimated costs and ongoing use

Live October 7 defaults: $0.005/token, cached analysis $0.001/token; waveform 0.06, BPM 0.10 and key 0.10 tokens/second, rounded up per tool. A three-minute full-suite example estimates 47 tokens, exact $0.235 displayed $0.24; five minutes estimates 78 tokens/$0.39. Final costs use measured duration; request a fresh estimate, not a fixed-price promise.

Current packs: Starter 1K/$5, 10K/$50, 50K/$250, 200K/$1,000 (USD). Read list_token_packs before purchase. Banked usage has no per-job minimum; one-off Checkout has a $0.50 minimum. A short track can stay below that floor; do not increase scope just to trigger a charge.

Humans fund accounts through the token shop. Agents need a trusted key-aware connection, a spending limit and an authorized rights policy. Checkout creation is not payment success. Refund requests, pending refunds and confirmed money returned are different states; consult receipts and support for attention cases.

Privacy, support and discovery

Audio is processed for analysis and not stored as user audio; temporary processing can use disk. Stripe hosts payment entry; Pulse retains operational account/job/billing records and payment identifiers. See the privacy policy for privacy and retention details. Public pages also request typography from Google Fonts.

Terms · API docs · Machine-readable journey · MCP health

Existing listings: Official Registry (space.studiosphere/pulse,1.0.2), Smithery, Glama connector. A listing is not a compatibility endorsement.

Support/security questions: support@studiosphere.space. Never send your API key.

Operated by StudioSphere Inc., Quebec, Canada. See LICENSE for this documentation repository; sample rights are defined by each sample's own license.

Tools it offers (10)

What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.

  • start_trial
  • estimate_cost
  • analyze_track
  • request_payment_link
  • get_job_status
  • get_token_balance
  • list_token_packs
  • purchase_token_pack
  • search_open_loops
  • get_open_loop

Signals

Last commit
Oct 2026
Advanced
Delivery
pulse MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
space-studiosphere-pulse
Source
github.com/notpaulb/studiosphere-pulse-mcp
Hosted endpoint
https://mcp.studiosphere.space/mcp