StudioSphere Pulse MCP MCP server

StudioSphere Pulse is an official audio intelligence server that provides BPM detection, musical key identification, and waveform peak analysis for public audio URLs. It operates on a pay-per-second model with privacy-first processing, ensuring audio is not stored. The server integrates with AI assistants via MCP to enable rights-aware audio analysis for music apps, DJ tools, and catalog workflows.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by StudioSphere

MCP endpoint (Streamable HTTP)

https://mcp.studiosphere.space/mcp

Vendor documentation

What you can do with it

Detect BPM tempo and confidence for music apps and DJ tools
Identify musical key for harmonic mixing and playlist grouping
Extract waveform peaks for audio previews and timeline visualization
Enrich music catalogs with structured audio metadata

Tools advertised by the last live check:

start_trial
estimate_cost
analyze_track
request_payment_link
get_job_status
get_token_balance
list_token_packs
purchase_token_pack

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add studiosphere-pulse-mcp --url https://mcp.studiosphere.space/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable studiosphere-pulse-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start studiosphere-pulse-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "studiosphere-pulse-mcp": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "studiosphere-pulse-mcp": {
      "serverUrl": "https://mcp.studiosphere.space/mcp"
    }
  }
}

See all 782

Do you run StudioSphere Pulse MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing