DAIW

kr.daiwPublished by daiw.krOfficial publisherv0.1.17Updated Nov 1, 2026

Compose, mix, master and export in Logic Pro, REAPER or Ableton Live by talking to an AI engineer.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant act as an AI audio engineer for composing, mixing, mastering and exporting in Logic Pro, REAPER or Ableton Live.

What you can do
  • Compose music through conversation with an AI engineer.
  • Mix and master sessions in Logic Pro, REAPER or Ableton Live.
  • Export finished audio from those DAW sessions.
  • No tool list is published, so the exact commands available are not documented.
When to use it
Worth considering if you work in Logic Pro, REAPER or Ableton Live and want an assistant to help compose, mix, master or export projects through conversation instead of manual DAW work.
Requirements
A remote MCP endpoint at mcp.daiw.kr over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. A DAIW account and a supported DAW (Logic Pro, REAPER or Ableton Live) are implied by the description.
Before you install
OAuth grants the server access to your DAIW account, so review the scopes requested. The server can change and export audio projects, so work on copies or versioned sessions. No tool list, README or instructions are published, so what it does to your sessions and where your audio data goes cannot be verified.

Installation

In SourceWeft

  1. Open DAIW 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/kr.daiw%2Fdaiw/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": {
    "daiw": {
      "type": "http",
      "url": "https://mcp.daiw.kr/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

2
  1. v0.1.17LatestNov 1, 2026
  2. v0.1.16Oct 31, 2026

Score

56% 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

    Publish an icon in the registry entry.

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