Pumpkin is a Minecraft server implementation written entirely in Rust that aims to let anyone host fast and efficient Java and Bedrock Edition servers, and it is built for server operators and plugin developers who want vanilla-compatible gameplay without the official Java server.

What it is

Pumpkin is a reimplementation of the Minecraft server itself, written from scratch in Rust rather than as a patch on top of the official Java Edition server jar. It supports the latest Java and Bedrock Minecraft server versions and states that it adheres to vanilla game mechanics, so existing players and worlds should behave the way they expect. It lives in the Minecraft server ecosystem, alongside the official Mojang server, Spigot and Paper derivatives, and the proxy tools that front them, but it takes a different route from all of them by replacing the server binary instead of modifying it.

The concrete problem it solves is performance and control under load. The project's stated goals are performance through multi-threading, compatibility with the latest Java and Bedrock versions, security through prevention of known exploits, flexibility through configuration, and extensibility through a plugin foundation. Operators who find that a Java-based server consumes more memory and CPU than their hardware justifies can run Pumpkin instead, and they get a server whose behaviour is largely tunable through a TOML configuration file, including the ability to disable features they do not need.

Key capabilities

• Runs both the Java Edition and the Bedrock Edition of the protocol, with Bedrock marked as work in progress.
• Implements server status and ping, connection encryption, and packet compression.
• Loads, saves, and generates chunks with selectable strategies named Vanilla, Linear, and Pump.
• Provides world features including world loading, world time, world borders, world saving, lighting, entity spawning, scoreboard, player tab-list, bossbar, and liquid physics.
• Handles player features including skins, movement, teleport, animation, inventory, experience, hunger, the off hand, and eating, with advancements marked as work in progress.
• Exposes server administration through Query, RCON, chat, commands, permissions, translations, inventories, and particles.
• Supports BungeeCord, BungeeGuard, and Velocity proxy connections.

Who uses it and how

• Self-hosters running small to medium servers who want a lightweight Rust binary instead of the official Java server, configured through a TOML file.
• Networks that place Pumpkin behind an existing BungeeCord or Velocity proxy, since both are supported for inbound player connections.
• Operators who need remote administration and monitoring, using RCON and Query to integrate the server with existing tooling.
• Admins enforcing moderation and access policy through the built-in permissions system and chat handling.
• Plugin developers, who can build against the plugin API crates pumpkin-plugin-api and pumpkin-plugin-wit, though the plugin hooks themselves are still tracked as an open issue.

Getting started

The README points to the Quick Start guide at https://docs.pumpkinmc.org/#quick-start for getting Pumpkin running. The project also carries the docker topic, and its documentation site at https://pumpkinmc.org/ is the entry point for further material.

How it compares

This registry entry does not list any paid products that Pumpkin replaces, and the README does not name any competing server implementations as alternatives, so Pumpkin stands alone here as a Rust-based Minecraft server rather than as a comparison against specific commercial hosting or server software.

When to use it — and when not to

The README states plainly that Pumpkin is under heavy development, and it links to issue #449 for what remains before the 1.0.0 release. Redstone, chunk generation, combat, entity AI, commands, plugins, and entity mobs, animals, villagers, and bosses are still tracked as open issues or marked work in progress, and the repository carries 452 open issues, so anyone needing complete vanilla parity for a production world should wait or run it only in a test environment. A self-hoster must operate the server process and its world data directly, since Pumpkin ships as a server binary with a TOML configuration file rather than a managed platform.