The README is honest about the gap between ambition and code — the tool list is `get_server_info` and `check_affinity_designer`, and the automation layer is described as where it is heading. Useful if you want to follow or contribute to Windows-side Affinity automation; not yet something to build a workflow on. The MSI requirement is the detail that decides whether it can see your install at all.
An early-stage MCP server aimed at driving Affinity Designer from an assistant. The stated target is document manipulation, layer management, export operations and tool automation, driven on Windows through PowerShell scripting, COM where available, Win32 for window management and .NET for the rest. What is built today is the groundwork: the server reports its own state and finds your Affinity installation.
- The server's information and status returned to the client — `get_server_info`
- A check for whether Affinity Designer is installed and where — `check_affinity_designer`
- Non-standard install locations handled by editing `affinity-install-paths.json` in the project root; the server tries each path in order until one resolves, with separate Windows and macOS lists
- Everything beyond those two — documents, layers, exports — is the project's stated direction, not shipped behaviour
Windows is the primary target; macOS is explicitly seeking contributors for the AppleScript/JXA side. Affinity must be installed from the MSI installer from the official site, so it lands under `C:\Program Files\` and registers the entries automation needs — a store-style install will not be found. Node >= 18.0.0 and TypeScript 5.0+; clone, `npm install`, `npm run build`, then point your client at `dist/index.js`. No account and no key.