StemConsole

ai.stemconsolePublished by stemconsole.aiOfficial publisherv1.1.0Updated Oct 26, 2026

Split songs into vocals, drums, bass, guitar and piano stems, in batches; manage songs and setlists

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote StemConsole MCP server that lets an assistant split songs into vocals, drums, bass, guitar and piano stems in batches and manage songs and setlists.

What you can do
  • Split songs into separate stems: vocals, drums, bass, guitar and piano
  • Run stem separation in batches across multiple songs
  • Manage a library of songs and organize them into setlists
  • Check service capabilities and get a task URL, which work without an API key
When to use it
Useful when you want an assistant to separate a track into individual instrument parts, process several songs at once, or keep songs and setlists organized without leaving the chat.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site; no local package to install. OAuth authentication is required, and full functionality needs an Authorization header carrying a Bearer token with a StemConsole API key obtained from the developer site. Without the key only the free capability and task-URL tools work.
Before you install
The server asks for an API key sent in the Authorization header, so treat it as a secret and check how it is stored. Uploading songs sends audio to a third-party service, and batch processing may consume paid quota or credits; confirm limits and pricing before running large jobs.

Installation

In SourceWeft

  1. Open StemConsole in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.stemconsole%2Fstemconsole/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "stemconsole": {
      "type": "http",
      "url": "https://stemconsole.ai/mcp/account"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestOct 18, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.