1. Install DreamCleanr
Use the GitHub-first install path so the local CLI and MCP module are available on your Mac.
curl -fsSL https://raw.githubusercontent.com/jlsport18/DreamCleanr/main/scripts/install.sh | bash
MCP Setup
DreamCleanr already ships a local MCP server. The MCP surface stays preview-first: you can scan, inspect, render reports, and preview scheduled cleanup without exposing destructive cleanup by default.
Start here
Use the GitHub-first install path so the local CLI and MCP module are available on your Mac.
curl -fsSL https://raw.githubusercontent.com/jlsport18/DreamCleanr/main/scripts/install.sh | bash
Before wiring a client, make sure DreamCleanr is installed and the MCP entrypoint resolves locally.
dreamcleanr --version
python3 -m dreamcleanr.mcp_server
If the second command starts the local server without import errors, the client configs below are the right shape.
Client configs
Reference file: `integrations/claude-mcp.json`
{
"mcpServers": {
"dreamcleanr": {
"command": "python3",
"args": ["-m", "dreamcleanr.mcp_server"]
}
}
}
Reference file: `integrations/codex-mcp.toml`
[mcp_servers.dreamcleanr]
command = "python3"
args = ["-m", "dreamcleanr.mcp_server"]
Reference file: `integrations/vscode-mcp.json`
{
"servers": {
"dreamcleanr": {
"command": "python3",
"args": ["-m", "dreamcleanr.mcp_server"]
}
}
}
Destructive cleanup is intentionally not exposed as a default MCP action.
Troubleshooting
DreamCleanr keeps the MCP setup local and free today, while the premium shell remains a later one-time upgrade.