EncySoftware.DmcMcp 0.5.0

dmc-mcp

MCP server for publishing post-processors to Digital Machine Center from Cursor or Claude Code — the DMC counterpart of ency-extension-mcp.

Publishing does not submit for moderation by itself: the author looks at what the AI filled in first.

Two ways to fill in a card

Server AI (default). publish_post / publish_folder with ai=true: the backend reads the archive and fills the description, control, machine, axes and cover with its own AI — the company's keys, one house style, nothing for the author to write.

Your own agent. publish_post(..., ai=false) uploads the archive and nothing more. Then inspect_archive(file) hands the agent the facts — machine name, axes and travels, equipment, controls mentioned, whether there is a picture inside — and the agent writes the description itself, sets the fields with update_post, and puts a cover with set_cover (its own picture) or regenerate_cover(source: "archive") (the picture from the archive, no AI). The author sees the text before it is saved, and pays for no AI but their own.

Manifest for publish_folder

A CSV next to the files; only the file column is required, the rest are optional and only override what they name:

file,name,controllerManufacturer,controllerSeries,controllerModel,machineManufacturer,machineModel,machineType,numberOfAxes
fanuc-0i.sppx,"Fanuc 0i-MF for Haas VF-2",Fanuc,0i,MF,Haas,VF-2,MILLING,3
siemens.sppx,Siemens 828D for DMG,Siemens,828D,,DMG MORI,,MILLING,3

Columns: file, name, description, controllerManufacturer, controllerSeries, controllerModel, machineManufacturer, machineSeries, machineModel, machineType (MILLING, TURNING, MILL_TURN, WIRE_EDM, LASER, PLASMA, WATERJET, GRINDING, ROBOT, EDM, ROUTER, SWISS, GAS_PLASMA_LASER, ADDITIVE, OTHER), numberOfAxes. An unknown column is an error, not a silently dropped one.

Install (Cursor, Claude Code)

Requires the .NET 8 SDK.

dotnet tool install -g EncySoftware.DmcMcp
dmc-mcp setup

Until the package is on nuget.org, install from the .nupkg attached to the latest release: dotnet tool install -g EncySoftware.DmcMcp --add-source <folder with the .nupkg>.

setup writes the dmc server into ~/.cursor/mcp.json (merging with your other servers), registers it in Claude Code when its CLI is installed, and signs you in. Restart the editor afterwards. --no-login skips the sign-in.

Sign-in — dmc-mcp login — opens the sign-in page in your browser (licsys account); the tool keeps only a refresh token in %APPDATA%\dmc-mcp\auth.json and never sees the password. --password is the fallback for a machine without a browser. A publisher role in DMC is required.

Something not working? dmc-mcp doctor checks the sign-in, whether DMC accepts the token and grants the publisher role, and whether the server is registered in Cursor and Claude Code — one line per check. setup and doctor also mention a newer version on nuget.org when there is one.

Long imports report progress into the editor (MCP progress notifications) while they run.

By hand instead of setup — login, plus in ~/.cursor/mcp.json:

{ "mcpServers": { "dmc": { "command": "dmc-mcp" } } }

What it looks like

1. "publish the post C:\posts\fanuc-0i.sppx, it's Fanuc 0i-MF for a Haas VF-2" → publish_post — a draft link and what the AI filled in.
2. "the control is Siemens 828D, not Fanuc" → update_post.
3. "submit it for review" → submit_post.
4. "is it published?" → check_post_status.

Settings

Everything that ties the tool to DMC lives in one file — src/Brand.cs.

Development

dotnet test tests/DmcMcp.Tests.csproj   # logic; DMC is faked, no network
dotnet run --project src                 # stdio server, talk JSON-RPC to it
dotnet pack src -c Release -o pkg        # the tool's .nupkg

Releases

Push a version tag (v0.1.1): publish-tool.yml runs the tests, packs the tool with that version, attaches the .nupkg to the GitHub release and publishes it to nuget.org through trusted publishing — no key is stored in this repository.