Repository navigation
MCP clients
Drydock's tools are an MCP server, so any MCP client can use them: Claude Desktop, Claude Code, LM Studio, or your own agent. The same Drydock.exe runs it with --mcp.
Add this to %APPDATA%\Claude\claude_desktop_config.json and restart Claude Desktop:
{
"mcpServers": {
"se2-modsdk": {
"command": "C:\\path\\to\\Drydock.exe",
"args": ["--mcp"]
}
}
}claude mcp add se2-modsdk -- C:\path\to\Drydock.exe --mcp
The command is C:\path\to\Drydock.exe with the argument --mcp, over stdio. Use the full path to the exe: clients start servers from their own folder.
By default the client sees all 60 tools. A small model chooses better from fewer, so you can narrow the list with the SE2_MCP_PROFILE environment variable:
| Profile | Tools | About |
|---|---|---|
full |
60 | everything, including the live editor, Mod HUB and Blender |
core |
29 | knowledge, lookup and careful editing; what the workshop's assistant uses |
mini |
13 | the smallest useful set |
"env": { "SE2_MCP_PROFILE": "core" }A session starts with work_on(), which picks the mod to work on and remembers it, and ends with finish_and_publish(), which removes the editor bridge (it must never ship inside a mod) and says what still blocks publishing. The server's own instructions tell the model this; the README has the details of every tool.
Drydock, by Heft · github.com/heft21/drydock-se2 · MIT license · not made or endorsed by Keen Software House