Stratz vs Wynncraft
A side-by-side look at the Stratz and Wynncraft MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Stratz for gaming work as a local process; choose Wynncraft for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Stratz when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_STRATZ_KEY.
Choose Wynncraft when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
combatGlobalLevel, professionsGlobalLevel, guildLevel.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 37/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PLATFORM_STRATZ_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Stratz | View Wynncraft |
Tools & capabilities
Stratz tools
No tool names declared yet. Check the project README from the listing page.
Wynncraft tools 4
combatGlobalLevelprofessionsGlobalLevelguildLevelglobalPlayerContent
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Stratz
{
"mcpServers": {
"stratz": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-stratz"
],
"env": {
"PLATFORM_STRATZ_KEY": "YOUR_PLATFORM_STRATZ_KEY_HERE"
}
}
}
}
Wynncraft
{
"mcpServers": {
"wynncraft": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wynncraft"
]
}
}
}
Frequently asked questions
Stratz is categorized under Gaming and uses a local stdio subprocess. Wynncraft belongs to Gaming and uses a local stdio subprocess. Pick Stratz for gaming work and Wynncraft for gaming.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Stratz has no declared pricing — check the project's own site. Wynncraft has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add stratz and wynncraft as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stratz has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Wynncraft has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.