Shawarma

studio.shawarmaPublished by shawarma.studioOfficial publisherv1.26.1Updated Oct 30, 2026

Make and edit instrumental music from your agent: songs you can keep changing, MP3/WAV export

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant create and keep editing instrumental songs, then export them as MP3 or WAV.

What you can do
  • Create instrumental music from a prompt inside the assistant.
  • Edit and revise existing songs iteratively rather than starting over.
  • Export finished tracks as MP3 or WAV files.
When to use it
Useful when you want an assistant to generate instrumental background tracks or sketches and refine them over several turns, then hand back downloadable audio files.
Requirements
A remote endpoint at shawarma.studio over streamable HTTP; no local package. Authentication is required: either an OAuth sign-in or a Bearer key from the provider's developer page sent in the Authorization header.
Before you install
Access is tied to a provider account and an Authorization credential; keep the key private. The server creates and modifies music projects on the provider's side, so generated content and prompts are sent to a third party. No pricing or usage limits are stated here.

Installation

In SourceWeft

  1. Open Shawarma 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/studio.shawarma%2Fmusic/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": {
    "shawarma": {
      "type": "http",
      "url": "https://shawarma.studio/mcp"
    }
  }
}

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.26.1LatestOct 30, 2026

Score

83% 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
  • 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.