StudioSphere Pulse

Discover free, licensed loops and analyze authorized audio for BPM, musical key and waveform data.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Start Trial: Start a temporary, email-free Pulse trial for one URL analysis. Read trial_policy and trial_allowance for the actual duration cap and remaining attempts; an existing trial key may have a
  • Estimate Cost: Estimate the cost to analyze an audio file before committing. Always call this first. Returns an estimated cost in dollars, a job_estimate_id and expires_at. Review the estimate before
  • 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 h

What data it sees

Do you need an account

No: the server works without sign-in

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.

Connect anonymously to https://mcp.studiosphere.space/mcp using Streamable HTTP. Begin with search_open_loops, then get_open_loop. Preserve each sample’s exact licence, required attribution and source credits. Connection instructions: https://pulse.studiosphere.space/connect. No account or tokens are needed for loop search or retrieval.

Analysis is separate. First-time users can try one URL track up to five minutes using a private temporary trial key. The current default allowance is 78 tokens, expires after 24 hours and allows a second queued attempt only if the first fails; the returned allowance controls use. API keys bind when the MCP session initializes. End the anonymous connection and reconnect after obtaining a trial key. Trial issuance creates a credential and requires the user’s approval.

Ongoing analysis uses one-off Checkout or banked tokens. Starter is 1,000 tokens for USD $5 as verified October 8, 2026 locally / October 9 UTC. Call list_token_packs for current options and estimate_cost before analysis. Prices and costs are estimates to review before spending. Checkout links are presented to the user; do not complete payment automatically.

Submit audio only with rights, permission, lawful access or another legal basis. BPM and musical key are estimates requiring review. Pulse processes audio for analysis and does not store it as user audio. OAuth and bearer/header-key authentication are not implemented. Actual Smithery, Claude and ChatGPT host workflows, including paid authentication, remain untested; protocol/SDK success does not establish host compatibility.

Docs: https://pulse.studiosphere.space/docs Privacy: https://pulse.studiosphere.space/privacy Terms: https://pulse.studiosphere.space/terms Support: support@studiosphere.space

How to connect

How to connect StudioSphere Pulse to Claude

The server address to paste into Claude settings:

https://pulse--studiosphere.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect StudioSphere Pulse to ChatGPT

The server address to paste into ChatGPT settings:

https://pulse--studiosphere.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect StudioSphere Pulse to Cursor

The server address to paste into Cursor settings:

https://pulse--studiosphere.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (10)

Raw names from tools/list. Only developers need these.

start_trialStart a temporary, email-free Pulse trial for one URL analysis. Read trial_policy and trial_allowance for the actual duration cap and remaining attempts; an existing trial key may have a lower cap. One completed/partial analysis consumes the allowance regardless of remaining tokens. A failed analysis may retry only when attempts remain. No Stripe Checkout session is created. Store the returned private API key in the client or a trusted local environment; never repost it in logs, screenshots, shared chats or issues. Confirm rights, permission, lawful access, or another legal basis before analysis. The original CC0 demo is https://pulse.studiosphere.space/assets/pulse-demo.mp3 (180 seconds); use it only if it fits the returned cap.
estimate_costEstimate the cost to analyze an audio file before committing. Always call this first. Returns an estimated cost in dollars, a job_estimate_id and expires_at. Review the estimate before spending; final cost depends on measured duration and completed analysis. Free — never charged. If processing or payment returns estimate_pricing_changed, get a fresh free estimate with estimate_cost, present the new price, and wait for explicit user approval before processing or payment. Never silently retry analysis or purchase.
analyze_trackRun 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. If processing or payment returns estimate_pricing_changed, get a fresh free estimate with estimate_cost, present the new price, and wait for explicit user approval before processing or payment. Never silently retry analysis or purchase.
request_payment_linkGenerate 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. If processing or payment returns estimate_pricing_changed, get a fresh free estimate with estimate_cost, present the new price, and wait for explicit user approval before processing or payment. Never silently retry analysis or purchase.
get_job_statusCheck 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.
get_token_balanceCheck the banked token balance for the authenticated Pulse account. Requires PULSE_API_KEY.
list_token_packsList the available Pulse token packs (tier label, token count, price). Use before purchase_token_pack to show options to the user.
purchase_token_packCreate 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.
search_open_loopsFind released original synthesis kits and individually auditioned source samples by keyword, pack, BPM, key and licence. Automated checks are not listening review. Free; no account or tokens required. Source tags are creator hints. Preserve attribution when required and follow each sample’s licence.
get_open_loopGet a released sample’s metadata, exact licence, attribution, preview and WAV download URLs. Free; no account or tokens required. Keep attribution when using the sample in a song.