Connect your AI assistant to DupliWalker
MCP, the Model Context Protocol, is an open standard that lets an AI assistant use tools on your computer. DupliWalker Desktop includes an MCP connection, so an assistant that can start a local MCP server can look at what DupliWalker has found and, when you approve it, run an automation script in the app. This site has setup steps for Claude Code, Codex and Claude Desktop, and says below which of them Deltopia has checked.
Why use it. Describe what you want in your own words. The assistant reads DupliWalker’s automation API, writes a script and asks to run it. You see the script first, and nothing runs until you click Allow Once.
Where it applies. DupliWalker Desktop Beta 5 (version 1.0.0-beta.5), a public beta for Mac with Apple Silicon. It does not work with DupliWalker for the web. What the connection needs, during the beta and in release builds, is under Requirements.
Set up the connectionDownload DupliWalker for Mac
What you can ask
These example requests read the results of a scan you have already run in DupliWalker. Each one makes the assistant write a short script, which you then approve or deny.
- “List the duplicate groups in my current DupliWalker results and show the five largest, with the paths of their files.”
- “Which identical folders did DupliWalker find in the current results, and how many files does each one hold?”
- “Which duplicates appear in both my Dupli folders and my Reference folders?”
A script can use anything DupliWalker’s automation API offers, including actions that change or delete files. The examples above only read. Read every script before you allow it.
You stay in control
- It is off until you turn it on. The setting is Allow AI agents to run automation scripts (MCP), under Settings › General › AI agents. To find it, click the gear icon at the top right of the window to open Application Settings, then choose General.
- Every run needs your approval. DupliWalker shows you the script and “Requested by client via MCP”, with two buttons: Deny and Allow Once. There is no “always allow” for MCP.
- You can take access back at any time. Turning the setting off closes the assistant’s session at once. An approval dialog that is waiting is closed and that script does not run. The assistant gets a connection error, and cannot reconnect until you turn the setting back on.
The setup guide shows what the approval looks like.
Requirements
You need:
- DupliWalker Desktop 1.0.0-beta.5 or later, on a Mac with Apple Silicon running macOS 12 or later. Older builds do not include the connection. Download it here.
- During the public beta: nothing extra. DupliWalker Desktop Beta 5 is a public beta. Until 1 de febrero de 2027 a las 00:00 UTC, every feature is unlocked for every user, including this connection, with Pro or with no licence, as the download page says. The beta build expires then; it does not switch to licence-based access, so a licence does not keep it working, and you will need a newer DupliWalker build from the download page.
- Release-build policy (separate from the beta): the custom-automation right. MCP scripts count as custom automation. In release (non-beta) builds, this connection needs Oro or the Trial: Pro does not include custom automation, and a script is refused with “This edition does not include running custom automation scripts, so the script was not run.”
- An AI client on the same Mac that can start a local MCP server, such as one in the table below.
Setup steps by client
These are the clients the setup guide has steps for. A row is a set of steps, not a promise that the client works with DupliWalker Desktop: the last column says what Deltopia has checked, and where it has not, the steps follow that client’s own documentation. DupliWalker Desktop is for Macs with Apple Silicon, so every row is macOS on Apple Silicon.
| Client | How to connect | Checked by Deltopia |
|---|---|---|
| Claude Code | One command: claude mcp add | Not yet checked — steps follow Claude Code's documentation |
| Codex (command line) | One command, codex mcp add, or an entry in ~/.codex/config.toml | Not yet checked — steps follow Codex's documentation |
| Claude Desktop: extension | The DupliWalker extension file (.mcpb, not code-signed) | Not yet checked — steps follow Claude Desktop's documentation |
| Claude Desktop: manual configuration | A manual entry in claude_desktop_config.json | Not yet checked — steps follow Claude Desktop's documentation |
| claude.ai and ChatGPT in a web browser | Cannot connect: a web page cannot start a program on your Mac | Not applicable |
Questions
Does the connection leave my computer?
The connection between the assistant and DupliWalker is local: a small launcher program on your Mac talks to the app on the same Mac. That does not keep your content on your computer. Whatever a script returns or logs, such as file names, paths and sizes, goes to the AI client, and the company behind it processes it under its own terms. Read the script and its result with that in mind.
Does DupliWalker have to be running?
Yes. If the app is not running, or MCP is switched off, the launcher answers “DupliWalker is not running. Start it, then reconnect.” If you quit the app while an assistant is connected, the assistant has to reconnect after you start it again.
Why can’t I choose “always allow”?
Each script is different, and an assistant writes it just for that request. So an approval covers one run only, and DupliWalker does not offer to remember it.
How do I turn it off or reconnect?
Click the gear icon at the top right of the window, choose General, and turn off the setting in the AI agents section to cut access at once. The assistant’s session is closed and it gets a connection error; reconnecting fails with “DupliWalker is not running. Start it, then reconnect.” until the setting is back on. To reconnect, turn it back on and start your assistant’s connection again. The setup guide has the details for each client.
Do I need Oro?
During the public beta, no: until 1 de febrero de 2027 a las 00:00 UTC, every feature is unlocked for every user, including this connection. The beta build expires then; it does not switch to licence-based access, and you will need a newer DupliWalker build.
Release-build policy, which is separate: in release (non-beta) builds, yes, or the trial. MCP scripts count as custom automation, which Oro and the trial include and Pro does not, and a script is refused on Pro with “This edition does not include running custom automation scripts, so the script was not run.” See Requirements.
Does it work with DupliWalker for the web?
No. The setting and the launcher are part of DupliWalker Desktop. DupliWalker in the browser does not offer this connection.
Can I use it from Claude or ChatGPT in the browser?
No. Those are web pages, and they cannot reach a program on your Mac.
Which Macs and systems are supported?
Macs with Apple Silicon. Builds for Intel Macs, Windows and Linux come later in the beta, as the download page says.