get_server_infoLABSCO SUMMARY
Two tools today: the install probe, and the server's own status.
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.
What it is
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.
What you get
- 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.jsonin 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
Requirements
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.
Setup effort
Build from source — git clone https://github.com/szgk/mcp-affinity-designer.git
USE CASES
01
Confirming the automation path can see Affinity at all
Run the installation check before anything else — an MSI install under Program Files is what the whole approach depends on.
02
Pointing it at a non-standard install
Add your executable's full path to the platform section of the install-paths file; the server walks the list in order until one works.
03
Checking the server is alive from the client
Ask for server info to confirm the connection and see what state it reports before debugging further.
2 tools
Listed in project docs. Your client may show a different list.
check_affinity_designerBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/szgk/mcp-affinity-designer.git
cd mcp-affinity-designer
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"affinity-designer": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_AFFINITY_DESIGNER>/dist/index.js"
]
}
}
}
