
zed-assistant/mcp
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Zed Assistant MCP is a remote Model Context Protocol server that lets an AI assistant (Claude, ChatGPT, or any other MCP-compatible client) manage one or more : check server status, moderate players,...
Обзор
Zed Assistant MCP is a remote Model Context Protocol server that lets an AI assistant (Claude, ChatGPT, or any other MCP-compatible client) manage one or more : check server status, moderate players, edit server/sandbox configuration, tail the game log, and run raw admin commands - all through natural-language conversation instead of RCON consoles or hand-edited .ini/.lua files. It works with any Project Zomboid server that has RCON enabled and writes the usual Server/*.ini / Server/*_SandboxVars.lua files - that includes both servers run via the standalone and servers ("Host" from the game's main menu). Both produce similar on-disk layout and RCON interface, so Zed Assistant MCP treats them identically. It runs as a single Go binary that exposes: - an (login + token issuing), so only accounts you approve can connect, and - an (/mcp) that speaks Streamable HTTP and requires a valid bearer token on every request.
README
Показан фрагмент оригинального README. Открыть оригинал.
Zed Assistant MCP
Zed Assistant MCP is a remote Model Context Protocol server that lets an AI assistant (Claude, ChatGPT, or any other MCP-compatible client) manage one or more Project Zomboid servers: check server status, moderate players, edit server/sandbox configuration, tail the game log, and run raw admin commands - all through natural-language conversation instead of RCON consoles or hand-edited .ini/.lua files.
It works with any Project Zomboid server that has RCON enabled and writes the usual Server/*.ini / Server/*_SandboxVars.lua files - that includes both servers run via the standalone dedicated server and servers hosted in-game (“Host” from the game’s main menu). Both produce similar on-disk layout and RCON interface, so Zed Assistant MCP treats them identically.
It runs as a single Go binary that exposes:
- an OAuth 2.1 authorization server (login + token issuing), so only accounts you approve can connect, and
- an MCP endpoint (
/mcp) that speaks Streamable HTTP and requires a valid bearer token on every request.
The server itself holds no game logic - every tool call is translated into either an RCON command sent to your running Project Zomboid server, or a direct read/write of the server’s own config files and player database on disk.
Table of contents
- How it fits together
- Features
- Available tools
- Requirements
- Installation
- Preparing your Project Zomboid server
- Configuration
- Running the server
- Connecting an AI / MCP client
- Access control model
- Security notes
- Troubleshooting
- License
How it fits together
┌────────────────────────────┐
AI client ────────►│ Zed Assistant MCP │
(Claude, etc.) │ /auth OAuth 2.1 server │
▲ │ /mcp MCP tool endpoint │
│ └─────────────┬──────────────┘
└── OAuth login (browser) ───┘
│ RCON (admin commands)
│ filesystem (ini / lua / sqlite)
▼
┌─────────────────────┐
│ Project Zomboid │
│ server(s) │
│ (dedicated or │
│ in-game hosted) │
└─────────────────────┘
Zed Assistant MCP must run somewhere that has:
Установка
This server does not publish a one-line install command.
Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →