Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"claude-dj": {
"args": [
"~/claude-dj-mcp/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server that lets Claude act as an autonomous radio DJ using Strudel live-coded music.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in entertainment / ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
The official MCP server implementation for the Perplexity API Platform
MCP Security Weekly
Get CVE alerts and security updates for Claude Dj Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that lets Claude act as an autonomous radio DJ using Strudel live-coded music.
⚠️ This project is designed for local development and personal use only.
Important security considerations:
Access-Control-Allow-Origin: *)dj_speak tool executes shell commands (macOS say) with user-controlled inputRecommendations:
Claude (MCP client)
│ stdio (JSON-RPC)
▼
MCP Server (Node.js)
│ In-memory state: pendingCode, pendingAction, browserState, requestQueue
│
├─ HTTP Server (port 6002, auto-increment if busy)
│ GET / → HTML page with <strudel-editor> + request bar
│ GET /api/poll → Browser polls: returns pending code/action
│ POST /api/state → Browser posts: started, activeCode, error, cps
│ POST /api/request → User submits song/vibe request from browser UI
│ GET /api/health → Health check
│
└─ Browser (opened via `open` package)
<strudel-editor> web component (loaded from unpkg CDN)
Polls /api/poll every 1s, executes pending actions
Posts state back via /api/state after each action
Request bar at bottom for user input
npm install
npm run build
Add to your MCP settings (e.g., ~/.config/claude-code/mcp.json):
{
"mcpServers": {
"claude-dj": {
"command": "node",
"args": ["~/claude-dj-mcp/dist/index.js"]
}
}
}
In Claude Code or Claude Desktop:
Use the claude-dj skill to start a DJ session
Or call tools directly:
Call start_session, then tell me when audio is ready
Once the session is started and audio is active:
play_pattern with Strudel codedj_speak with DJ commentarywait(30-90) to let the music playUsers can type requests in the browser UI:
Claude will acknowledge and incorporate requests into the next patterns.
| Tool | Description |
|---|---|
start_session | Starts HTTP server and opens browser with Strudel REPL |
play_pattern | Sends Strudel code to browser for evaluation |
stop_music | Stops the current pattern |
get_session_state | Returns browser state (started, activeCode, error, cps) |
set_tempo | Sets BPM or CPS |
dj_speak | macOS text-to-speech announcement (fire-and-forget) |
check_requests | Drains user request queue from browser UI |
wait | Blocks N seconds, then returns |