Model Context Protocol

Find a loop. Build something great.

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.

Hear what a connection can do

Your first loop, without an account.

Try the actual anonymous MCP connection in your browser. We’ll search for one free CC0 drum loop and retrieve its licence and attribution. No key, analysis job or payment is created.

Browse Open Loops

Connect → search → retrieve rights → preview your loop.

This browser demonstration is not an assistant host test. Use the instructions below to connect your own assistant. Privacy · Support

Start free, without a key

  1. Connect to https://mcp.studiosphere.space/mcp using Streamable HTTP, with no authentication.
  2. Ask your assistant to call search_open_loops, then select a result and call get_open_loop.
  3. Keep the returned license, license URL and attribution with the download. Follow each sample’s terms, including credit for CC-BY samples.
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.

Browse in your browser at Open Loops. Search and retrieval cost no tokens. Sample tags are creator hints; BPM and musical key are estimates requiring review.

https://pulse.studiosphere.space/mcp leads here. The actual protocol endpoint is on mcp.studiosphere.space.

Claude remote connector

Open Pulse in Claude

Use the existing StudioSphere Pulse Community listing by StudioSphere Inc. If Pulse is already connected, reuse it. Community means automated review, not Anthropic verification; availability depends on your workspace.

If the listing is unavailable in your workspace and Pulse is not connected, use Claude’s remote connector interface: Customize → Connectors → Add custom connector (labels can vary by plan). Enter the name StudioSphere Pulse and the URL below; choose No sign in for free discovery. Organization owners may need to enable custom connectors first.

https://mcp.studiosphere.space/mcp

Enable the connector in the conversation and try the free search/get prompt. Remote connections run from Claude’s cloud. Local Desktop configuration files are not the remote-connector setup path.

Anonymous setup follows Claude’s documentation; anonymous initialization has not been validated in Claude. Controlled Checkout tests used an existing configured connector. Expand Claude connection troubleshooting below for the scoped evidence and recovery steps.

Claude connection troubleshooting

Existing Claude connector: stale tools or interrupted chat

Use these steps only if your existing StudioSphere Pulse connector is missing the new payment-tool fields.

  1. Open Settings → Customize → Connectors → Yours → StudioSphere Pulse → More options → Refresh tools list (labels can vary). Keep the connector URL, private key and tool approval permissions unchanged.
  2. Start a fresh conversation using the same existing connector. In the observed test, refresh left the already-open conversation on the old schema.
  3. Confirm the loaded request_payment_link includes accept_minimum_charge (boolean) and max_upfront_amount_cents (integer). Stop and contact support if these fields are still missing; do not omit acceptance or the spending ceiling.

Carry the original job_id, payment_url and continuation.review_url privately into the fresh conversation. After interruption, call get_job_status for the original saved job; never create a replacement purchase, new analysis or new key to resume it. Contact support if the payment URL is lost.

Refreshing tools does not authorize spending. Confirm rights, permission, lawful access or another legal basis; the human must explicitly accept the minimum final cost and upfront ceiling and complete Checkout themselves.

New anonymous setup follows Claude’s documentation; anonymous initialization has not been validated in Claude. 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.

Claude Code (CLI)

Add an anonymous Streamable HTTP connection. Quote URLs so query characters work in zsh:

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

Run claude mcp list, enable Pulse and use search_open_loops → get_open_loop. This example follows Claude Code’s HTTP setup documentation; actual host onboarding has not been tested.

Cline

Use Cline’s MCP server settings with an anonymous Streamable HTTP connection:

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

Follow Cline’s current MCP instructions. This configuration has not passed an actual Cline host test; marketplace availability and paid access are not claimed.

ChatGPT

If your workspace offers custom MCP connections, use the public endpoint and the No authentication option for discovery. Availability depends on your plan and administrator settings.

https://mcp.studiosphere.space/mcp

ChatGPT does not present custom Pulse API keys. Pulse does not implement the OAuth flow required for authenticated ChatGPT use. Do not paste a key into this setup or treat a REST action as an MCP connection. Actual ChatGPT host onboarding is untested, and Pulse is not claimed to be in its directory.

See OpenAI’s custom MCP guide and authentication requirements.

Transport and authentication limits

End the old connection, update its URL privately and reconnect to initialize a new session when using a trial or account key. Query URLs can leak into client configuration, history or logs; never share a real key or store it in version control. Secure host-compatible paid authentication still needs assessment and approval.

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

This is a transport illustration for clients that explicitly support query-key initialization, not a universal host configuration.

One-off analysis without an account

Stay on your anonymous connection to analyze an authorized track through human-completed Checkout. No Pulse account, API key or token pack is needed for this path.

See the analysis plan before you pay

Choose an audio URL and only the tools your project needs, then copy a free-estimate task for your existing connected assistant. BPM and key help prepare session metadata; add waveform for visual peak data. This page makes no analysis or payment request. The initial source is the original Copper Step CC0 demo; check its licence and provenance.

Use accessible public HTTPS audio you have rights, permission, lawful access or another legal basis to submit. Keep private keys and signed URLs out. Your choices stay on this page; review them before pasting into an assistant. For a local file, use Pulse’s browser analysis flow.

What does your project need?

Review the estimate-only task

A free estimate describes the possible deliverable, not a result or reserved price. Ready to process your own authorized track? Review the current quote and follow the separate approval steps below.

  1. Call estimate_cost with the authorized audio URL and selected tools. Before approving spending, read analysis_options.result_delivery: the selected analysis can return Studio notes for a DAW session, sample-library tags or project notes. The estimate describes the deliverable; it contains no analyzed result. Review analysis_options.checkout: eligibility, billing terms and the estimated upfront payment when present.
  2. Confirm rights, permission, lawful access, or another legal basis and get human approval to create a payment link. Then call request_payment_link with the quote’s job_estimate_id and attestation_confirmed: true.
  3. Save the returned job_id, payment_url and continuation.review_url privately. Present payment_url for the human to review the hosted amount and complete payment. A reused link may omit charge fields; the analysis estimate is not the charge.
  4. After the human returns, call get_job_status for that same job. Follow continuation: wait within its suggested polling limit, review available results, or contact support when recovery is needed.
  5. On get_job_status, optional studio_notes appears only for completed or partial jobs with usable observed results. Paste the notes into your DAW session or project notes, keeping warnings, provenance, suppressed values and failed tools visible. BPM and key remain estimates requiring review; do not fill in missing values or infer structure/chords. Keep the job ID private when sharing. studio_notes is not payment confirmation; review receipts and refunds separately.

If interrupted, reconnect anonymously and poll the saved job. Do not request another payment link or submit another analysis to resume it. A Checkout link, redirect or completed analysis does not confirm payment or refund settlement. Status and result pages cannot restore a lost Checkout link; contact support with the saved job ID if you no longer have payment_url. Terminal Checkout result pages show billing separately. During recovery, receipt_api_url is an optional REST read, not another MCP tool.

One-off Checkout starts at $0.50 and can capture a buffered amount above analysis cost. Review minimum charges and refund thresholds. For a below-minimum quote, read minimum_charge_offer. Show its estimated upfront payment and minimum final cost; only after explicit acceptance send accept_minimum_charge: true and max_upfront_amount_cents equal to the approved upfront ceiling. Rights confirmation alone is not spending approval. An exceeded ceiling needs fresh human review. An eligible approved trial or already-funded tokens remain alternatives; do not increase scope just to trigger payment. The existing Claude connector’s minimum-charge Checkout was validated with human-completed payment; see the scoped evidence above.

Optional: one authorized audio trial

One analysis up to 5 minutes. URL only; BPM, key and waveform. Up to two queued attempts if the first fails. Rights, permission, lawful access, or another legal basis required. Read the current policy at /tools; the returned per-key allowance controls your trial. Default expiry is 24 hours. Remaining tokens do not grant another song.

  1. With human approval to create a private temporary key, call start_trial once. Treat any returned trial key as private.
  2. Keep it in a trusted client; end the anonymous connection, set the private query-key URL and reconnect to initialize a new session.
  3. Call get_token_balance to read the allowance, then estimate_cost using the original CC0 Copper Step demo (180 seconds), when it fits. Read its CC0 provenance.
  4. Review the estimate and confirm rights, permission, lawful access, or another legal basis; call analyze_track with the quote ID and attestation_confirmed: true, then poll get_job_status.

If interrupted, preserve the private key and job ID. Reconnect and poll before retrying; do not mint another key or resubmit an uncertain job. The trial is URL-only and allows at most two queued attempts if the first fails. BPM and musical key are estimates requiring review.

The demo’s 180-second BPM/key/waveform example estimates 47 tokens ($0.24) at current configured rates. Duration and final costs can differ; request a fresh free estimate before processing. One-off Checkout starts at $0.50; banked usage has no per-job minimum. Read current tiers with list_token_packs or in the token shop.

Autonomous agent setup (one-time human step)

  1. Create a Pulse account only when you want ongoing analysis; fund it through the token shop.
  2. Use a trusted key-aware client and initialize a new private connection. Set a spending limit and a rights policy for the authorized scope.
  3. Call get_token_balance → estimate_cost → review cost and rights → analyze_track → get_job_status.

The two scoped existing-connector Claude Checkout tests do not establish general host support. ChatGPT, Cline and Smithery host tests remain uncompleted; a successful SDK/protocol connection is separate evidence.

Machine-readable journey: /.well-known/pulse/agent-journey.json · Agent playbook

Only the Transport illustration changes as you type. The anonymous demonstration never reads or sends this field. It creates no account. Use a placeholder for shared examples, never a real key.

Ten tools on the live service

search_open_loopsFree anonymous search of licensed samples.
get_open_loopExact license, attribution, preview and download.
estimate_costFree estimated cost for authorized audio.
start_trialCreates a private temporary key; reconnect before use.
analyze_trackBPM/key estimates and waveform; key and rights required.
request_payment_linkCreates one-off Checkout; rights and human approval required.
get_job_statusSaved-job continuation, results and review notes.
get_token_balancePrivate account/trial balance and allowance.
list_token_packsCurrent tiers, including Starter.
purchase_token_packCreates Checkout to fund an account; human completes payment.

Structure and chord analysis are coming soon and unavailable.