Borrowing it
Nothing to install: this file belongs to ptaczek/daw-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ptaczek/daw-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ptaczek/daw-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/ptaczek/daw-mcp/claude-md)<a href="https://agentmods.dev/instructions/ptaczek/daw-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ptaczek/daw-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.03688 | $0.03688 |
| Opus 5 | $0.01844 | $0.01844 |
| Sonnet 5 | $0.00738 | $0.00738 |
| Haiku 4.5 | $0.00369 | $0.00369 |
Grade A, and why
daw-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAW MCP Project
MCP server for controlling DAWs (Bitwig Studio, Ableton Live) from Claude.
Scope: Session View / Clip Launcher Only
This project intentionally targets only the clip launcher (Bitwig) / session view (Ableton) paradigm. Arrangement view is out of scope.
Rationale:
- Clip launcher provides discrete, addressable units (track × slot) - ideal for AI-driven workflows
- Arrangement view has continuous timeline addressing - fragile, less intuitive for AI
- Bitwig's Control Surface API doesn't expose arrangement clips at all
- Ableton's API has arrangement access, but asymmetric support across DAWs is undesirable
- The user arranges clips into songs - that's human creative territory
Implications:
- No arrangement clip creation, reading, or note manipulation
- No Reaper support (Reaper lacks a clip launcher paradigm entirely)
- MIDI/OSC alternatives were considered but rejected - not worth the complexity
Workflow: AI generates clips in launcher slots → User arranges them into songs on timeline.
Project Structure
bitwig-extension/- Java extension for Bitwig Studio (TCP server on port 8181)ableton-extension/- Python MIDI Remote Script for Ableton Live (port 8182)mcp-server/- TypeScript MCP server that bridges Claude to DAW extensions
Building (Development)
# Bitwig extension
cd bitwig-extension && gradle build && gradle copyExtension
# MCP server
cd mcp-server && npm install && npm run build
Release Build
Creates a distributable ZIP with all components:
./scripts/release.sh 1.0.0
Output: release/daw-mcp-1.0.0.zip (~325KB)
Contents:
BitwigMCP.bwextension- Java extension (cross-platform, single file)AbletonMCP/- Python Remote Scripts (cross-platform)mcp-server.js- Bundled MCP server (~215KB, requires Node.js)config.example.json- Example configurationREADME.md- Installation instructions
How it works:
- Builds Bitwig extension via Gradle
- Bundles MCP server with esbuild into single JS file
- Copies Ableton Python scripts
- Creates ZIP archive
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 396 lines · 3,688 tokens per session scan A cf4ce5ac0cf1
daw-mcp CLAUDE.md is an instructions file published in the GitHub repository ptaczek/daw-mcp (16 stars, last pushed 8mo ago), licensed MIT. It adds 3,688 tokens to every session, about $0.0184 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.