search_vanillaLABSCO SUMMARY
Balance checked against the vanilla item, not against a vibe.
The reason to index the game first is that every later answer is grounded: a generated weapon is compared to the real katana's damage and weight, and every referenced item, sound and sprite is confirmed to exist. That turns "this looks about right" into something the server can disagree with.
What it is
A TypeScript server that indexes the game's own script files into a searchable database, then generates, validates and analyses mod scripts against it. It detects Steam, Epic and GOG installations on Windows, Linux, macOS and WSL.
What you get
- Vanilla content searched with type and category filters — search_vanilla
- Scripts generated from templates and real game patterns, for items, recipes, evolved recipes, fixing, sounds and vehicles — generate_script
- Script syntax and references validated, with a strict mode and detailed error reporting — validate_script
- Item, sound and sprite references checked against the game database — check_references
- A whole mod directory analysed for balance, compatibility and structure, with a report — analyze_mod
- Game files parsed and indexed, with the installation path detected for you — parse_game_files
- A Cloudflare Workers deployment path with D1 storage and an HTTP endpoint per tool
Requirements
Node.js 18.0.0 or higher. Clone the repository, npm install, npm run build, then point your client at dist/index.js. Run parse_game_files once to populate the database before the other tools have anything to check against. Deploying to Cloudflare needs Wrangler and a D1 database.
Setup effort
Build from source — git clone https://github.com/wink-/pz-mcp-server.git
USE CASES
01
Making a new item that is not overpowered
Find the closest vanilla equivalents first, then generate the script from real patterns and read the balance analysis before shipping it.
02
Catching a broken reference before the game does
Check every item, sound and sprite name against the indexed game database, rather than finding out from a console error.
03
Reviewing a mod you inherited
Point it at the mod directory and get balance, compatibility and structure reported together, with a quality score and specific issues.
04
Setting up on a new machine
The installation is detected across Steam, Epic and GOG on Windows, Linux, macOS and WSL, so indexing is one call with no path to hunt down.
6 tools
Listed in project docs. Your client may show a different list.
generate_scriptvalidate_scriptcheck_referencesanalyze_modparse_game_filesBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
Node.js 18.0.0 or later
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/wink-/pz-mcp-server.git
cd pz-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop — Local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"pz-mcp-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PZ_MCP_SERVER>/dist/index.js"
]
}
}
}
