Awesome Mineflayer MCP vs Wynncraft
A side-by-side look at the Awesome Mineflayer MCP 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 Awesome Mineflayer MCP 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 Awesome Mineflayer MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
connect_bot, connect_default, disconnect_bot.
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 | 53/100 · Good | 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 | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 80 | 4 |
| Full listing | View Awesome Mineflayer MCP | View Wynncraft |
Tools & capabilities
Awesome Mineflayer MCP tools 80
connect_botconnect_defaultdisconnect_botreconnect_botrespawnget_connection_statusget_default_accountget_observationget_stateget_inventorylist_playerslist_entities- +68 more on 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.
Awesome Mineflayer MCP
{
"mcpServers": {
"awesome-mineflayer-mcp": {
"command": "npx",
"args": [
"-y",
"awesome-mineflayer-mcp"
]
}
}
}
Wynncraft
{
"mcpServers": {
"wynncraft": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wynncraft"
]
}
}
}
Frequently asked questions
Awesome Mineflayer MCP is categorized under Gaming and uses a local stdio subprocess. Wynncraft belongs to Gaming and uses a local stdio subprocess. Pick Awesome Mineflayer MCP 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.
Awesome Mineflayer MCP 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 awesome-mineflayer-mcp and wynncraft as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Awesome Mineflayer MCP has a quality signal of 53/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Wynncraft has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.