StudioSphere Pulse — Audio Intelligence

StudioSphere Pulse — Free Loops and Audio Intelligence MCP

Current workflow evidence is maintained in the compatibility matrix. On October 29, 2026, one approved production SDK trial completed the 180-second CC0 demo through keyed reconnection, analysis, results and fresh anonymous saved-job recovery. All three tools were cache hits. This verifies trial delivery and recovery, not fresh detector execution or an LLM-host workflow. See the redacted trial report.

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

Local creative example

Try licensed loop → reviewed tempo grid → motion cuts: a CC0 loop, local custom player, human review controls, portable cut list and optional local MP4. Timing starts provisional; no analysis, purchase or credentials are created. This is an example, not automatic beat detection, DAW control or a video-provider integration.

Building a game with an agent? Use the game-audio starter for licensed CC0 music, source records, Unity import steps and an optional free estimate for your own authorized audio. The starter does not provide a one-shot SFX library or certify Unity/Blender MCP integration. Existing kit metadata needs no paid analysis.

Portable plugin package

This repository is the public documentation, MCP metadata and plugin package for StudioSphere Pulse, operated by StudioSphere Inc. It does not include the private production implementation.

The root plugin.json and mcp.json use the portable Agent Plugins format, supported by OpenAI and Cursor. Plugin version 0.1.0 points to the anonymous Streamable HTTP endpoint above, with no bundled credentials, local executable, dependencies or lifecycle hooks. The existing Pulse icon is in assets/icon.png. See plugin installation and validation.

Cursor local import connected all ten tools on October 12, 2026. A scoped host conversation validated loop search, licence/attribution retrieval, a free demo estimate, pack information and the anonymous missing-key response. Negative scenarios left paid analysis, trial issuance and Checkout creation unperformed; this does not establish server enforcement or paid-host compatibility. OpenAI personal ZIP import succeeded; runtime validation and public business publisher verification remain pending. This package is not a claim of marketplace acceptance or universal host compatibility.

Start without an account

Open the existing StudioSphere Pulse Community listing in Claude. Publisher: StudioSphere Inc. Community is automated review, not Anthropic verification. Reuse an existing connection. After free discovery, use the estimate-task builder on the connection guide: choose an authorized public HTTPS audio URL and BPM, musical key or waveform, then review and copy a free-estimate task. It stops before analysis, payment or credential creation and retains original-job recovery. Choices stay on the page until you copy them; keep private keys and signed URLs out. Only the canonical Copper Step demo receives its actual CC0 attribution; other audio is not assigned a licence. Costs, BPM and key are estimates requiring review. Review conditional Studio notes and upfront/minimum Checkout charges before explicitly approving spending.

Try the anonymous browser demonstration on the connection guide: search one CC0 loop, retrieve its licence and source credit, then preview or download it. After a successful retrieval, Plan my track’s estimate jumps to the existing estimate-task builder without changing your audio URL or selected tools. The loop’s licence does not cover other audio; use a source you have rights, permission, lawful access or another legal basis to submit. Navigating to the planner starts no estimate, analysis or payment. No key, account, analysis job or payment is created by discovery. 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.

Two scoped workflows through one existing configured Claude connector were validated on October 12, 2026: buffered Checkout with an automatic refund, and explicit minimum-charge Checkout after tool refresh and a fresh conversation. The short-track BPM/key/waveform job completed; provider-backed receipts confirmed US$0.50 captured, US$0 refunded and US$0.50 net. This does not certify anonymous initialization, OAuth, trial/banked-token workflows, other hosts or live over-cap rejection; cap rejection and uncertain-submission controls have local fixture evidence. HTTP/SDK fixtures are separate evidence, not general host certification or directory approval.

Ten tools

For eligible quotes, analysis_options.checkout.upfront_payment_estimate previews the current upfront USD payment using Pulse's existing Checkout charge builder. It is not a reserved price or the charge on a saved link; review the hosted amount before paying. Admission follows the gateway's rounded-cent rule.

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

Studio notes for your creative workflow

Before spending approval, read estimate_cost.analysis_options.result_delivery. It describes the selected analysis deliverable: Studio notes for a DAW session, sample-library tags or project notes. This is advisory, not an analyzed result or a reason to add tools the user does not need.

After analysis, get_job_status may include studio_notes only when the job is completed or partial with usable observed results. Paste the notes into your DAW session or project notes. Preserve warnings, provenance, suppressed values and failed tools; do not fill in missing values or infer structure/chords. BPM and key are estimates requiring review, including half-time/double-time tempo checks and ambiguous key centers. Keep the job ID private when sharing.

studio_notes is not payment confirmation. Read receipts/refund evidence separately and on demand. The notes add no MCP tool or input, do not include audio or the source URL, and grant no spending or rights approval. Local fixture evidence does not establish a new paid-host test or conversion uplift.

Choose how to continue after a free estimate

On the Pulse homepage, Copy task for Claude appears after a current anonymous free estimate. It copies the source, selected tools and advisory quote, including the estimated upfront payment and any minimum final-cost floor. It makes no API call and grants no payment consent. The action is unavailable with a key, after submission or uncertainty, or when the quote expires or its source changes. Review the private quote and URL before sharing them with your existing Pulse connector; confirm rights and explicitly approve spending before human-completed Checkout. After interruption, preserve and poll the original saved job rather than buying again. This new handoff has local browser clipboard and helper-fixture evidence only; the two previously validated existing-connector Checkout workflows do not constitute an actual host test of it. No new MCP tool is added.

estimate_cost works anonymously and now returns analysis_options. Read these before choosing a payment or trial tool:

• One-off Checkout: checkout.eligible checks the current admission minimum. request_payment_link requires explicit human approval and rights confirmation, but no Pulse account or API key. Present the saved link and the upfront charged_display when returned. A reused link may omit charge fields: review its hosted amount rather than treating the usage estimate as the charge. Checkout may collect a buffer, and minimum charges/refund thresholds can leave net payment above measured analysis cost. Review pricing and refunds.
• Trial: trial.duration_within_public_policy is advisory, not an entitlement. Get approval before creating a key, reconnect, and check the per-key allowance. Recover an existing trial instead of minting another key.
• Banked tokens: the estimate does not verify a balance. Use an existing trusted key-aware connection, check get_token_balance, and run analyze_track within an approved rights/spending scope. A trial key cannot buy packs.

No payment or key is created by estimation. Never increase analysis scope to reach a charge floor or automatically retry an uncertain purchase. MCP initialization also supplies this route-selection guidance; protocol/SDK validation remains separate from actual host compatibility.

Resume one-off Checkout analysis

For eligible authorized audio, stay on the anonymous connection: estimate → review costs and rights → approve link creation → request_payment_link → human payment → get_job_status. No Pulse account, key or pack is required.

Save the returned job_id, payment_url and continuation.review_url privately before presenting payment_url. After payment or an interrupted connection, reconnect anonymously and call get_job_status for the same job. Follow continuation: human Checkout pauses for the user, waiting supplies a suggested interval and attempt limit, results need review, and recovery requires checking the saved job or contacting support. Pause after the waiting limit; do not create another analysis or purchase to resume it.

continuation.financial_status_verified is false. A link, redirect, completed analysis or analysis cost does not prove payment or refund settlement. Status and result pages cannot restore a lost Checkout link; contact support with the saved job ID rather than creating another purchase. Terminal Checkout result pages show billing separately; during recovery use the optional receipt API on demand; receipt_api_url is an existing on-demand REST read, not another MCP tool. SDK fixtures test reconnection and synthetic payment states, not real payments or assistant-host compatibility.

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 29 issued trial had 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.4), Smithery, Glama connector. A listing is not a compatibility endorsement.

Support/security questions: [email protected]. 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.

Explicit short-track Checkout offer

Below the normal admission minimum, checkout.eligible remains false. Read analysis_options.checkout.minimum_charge_offer, when present. Show the estimated upfront payment and minimum_final_cost_usd; the existing final-cost floor is US$0.50, and refund thresholds can leave a higher net payment. Free trial and already-funded tokens remain alternatives. Never increase analysis scope to qualify.

Only after explicit human acceptance, call request_payment_link with the same job_estimate_id, attestation_confirmed:true, accept_minimum_charge:true, and max_upfront_amount_cents set to the approved upfront ceiling in whole USD cents. Rights approval alone is not spending approval. A quote or buffer change above that ceiling returns checkout_amount_exceeds_approval before a new purchase is created. Review again; never raise the ceiling or retry automatically. On interruption, retain the original job and payment link privately and poll that job. Live minimum-charge completion and receipt evidence covers the one scoped Claude purchase described above; live over-cap rejection and broader host compatibility remain unverified.

Existing Claude connector: stale tools or interrupted chat

Use these steps only if an existing StudioSphere Pulse connector is missing the new request_payment_link fields. In Claude, open Settings → Customize → Connectors → Yours → StudioSphere Pulse → More options → Refresh tools list (labels can vary). Keep the saved connector URL, private key and tool approval permissions unchanged; do not remove/recreate the connector or create a new key.

Start a fresh conversation using the same existing connector. A refresh did not update the already-open conversation in the observed test. Confirm the loaded tool includes accept_minimum_charge (boolean) and max_upfront_amount_cents (integer) before any approved minimum-charge request. If those fields are still missing, stop and contact support; do not submit using the older schema or omit the acceptance/ceiling.

Carry the original job_id, payment_url and continuation.review_url privately into the fresh conversation. After an interruption, call get_job_status for the original saved job; never create a replacement purchase, new analysis or new key to resume it. If the payment URL is lost, contact support. Refreshing tools or starting a chat is not spending approval: the human must explicitly accept the minimum final cost and upfront ceiling and complete Checkout themselves.

Search interpretation

In MCP 1.0.4, musical-key filters accept common spellings such as Am and a minor for A minor; major/minor remain distinct. Enharmonic spellings and Camelot codes are not converted. BPM, pack and licence constraints are never silently widened.

Keyword search ranks any matching term. Read each returned search_match: matched_terms, missing_terms and complete distinguish partial results. A drums-only match for “lofi drums” does not establish a lo-fi genre. Empty results remain empty; ask before relaxing a hard filter. Older deployments may omit this additive field. These explanations are query matching, not musical quality or harmonic-fit scores. Preserve exact licence, licence URL and attribution, and audition samples before use.

Choose an assistant host

The MCP 1.0.4 connection guide offers Claude, Claude Code, Cursor, Codex, ChatGPT, Gemini CLI, Cline and generic transport instructions. Existing connections should be reused. Guides start with anonymous licensed discovery or a free estimate, retain the selected source/tools, and do not create credentials, jobs or payment links. Gemini CLI uses httpUrl; this is not consumer Gemini Connected Apps certification. Codex CLI/IDE uses codex mcp add studiosphere-pulse --url 'https://mcp.studiosphere.space/mcp'. Cursor manual configuration uses a remote url entry. Setup instructions are candidates until the specific host workflow is tested; the recorded Cursor/Grok plugin and existing-Claude-Checkout evidence remain scoped as shown in the compatibility matrix.

References checked October 29: Codex, Cursor, Gemini CLI, ChatGPT, Claude Code and Cline.

Curated loops, project matching and portable exports

Use Find loops for your project for released loops, without an account or analysis. Existing individually auditioned source loops are separate from technically checked original synthesis; automated checks are not listening approval. The catalogue and complete-kit player remain available.

In your existing connected assistant, call search_open_loops with, for example:

{"project_bpm":120,"bpm_tolerance":5,"key":"Am","role":"bass","review_basis":"original_synthesis","limit":5}

Read project_match reasons and search_match.missing_terms. Project mode requires an explicit major/minor key when supplied; it cannot combine with bpm_min/bpm_max. Keys stay exact: no relative-key, enharmonic or transposition inference. include_unkeyed_percussion:true optionally admits unspecified-key percussion tag hints, requiring audition; this is not proof of atonality or musical fit. No additional MCP tool is added.

get_open_loop and search items include provenance_url and metadata_export_url. For several selected IDs use /open-loops/export?ids=POL_ID_1,POL_ID_2&format=json, csv or zip. Select 1–8 unique released IDs. ZIP includes unchanged WAVs, manifest, spreadsheet-safe metadata, per-file rights and credits, limited to 16 MiB audio plus 1 MiB metadata and a 30-second build. If busy, respect Retry-After; if too large, export metadata and download WAVs individually. Interrupted or unavailable exports publish no partial archive; retry the same selection rather than starting audio analysis.

Follow each file's exact licence. Mixed CC0/CC-BY selections have no blanket CC0 licence. Released hashes and source/applicability records support traceability, not proof of authorship or distributor acceptance. Audition the loops together and retain required credits in your project. This flow creates no trial, credentials, analysis or payment. Native assistant-host and DAW import testing require separate evidence.