MCrosAPI
Running a busy Minecraft server often means juggling a growing stack of plugins, each with its own commands, permissions, and configuration quirks. MCrosAPI was built to solve exactly that problem. It is the shared API layer for the MCros ecosystem, acting as a single control point that other MCros plugins plug into. Instead of memorizing a dozen different command structures, server operators get one consistent interface for managing registered plugins, checking access, and pulling information about the whole collection.
What MCrosAPI Actually Does
At its core, MCrosAPI provides a common command interface for controlling registered plugins. It also lets you check whether a specific plugin is available to a player and retrieves information about the broader MCros plugin collection. All registration and access data is stored in SQLite, which keeps things lightweight and portable across server restarts. The plugin also supports localized messages, so you can run it in English or Russian without editing source files.
Because it is a shared layer rather than a standalone gameplay plugin, MCrosAPI works quietly in the background. Other MCros plugins register themselves with it, and from that point on, the API handles access checks and exposes the core command group those plugins rely on.
Supported Versions and Loaders
MCrosAPI is designed for modern Minecraft Java Edition servers and fits neatly into the plugin-based server ecosystem. It targets current release branches of the game and is built to run alongside the popular plugin loaders that server owners already use. If you are running a recent server build, you should have no trouble dropping MCrosAPI into your plugins folder and letting the rest of the MCros family hook into it.
Before you commit, always confirm that your server software version matches what the plugin expects, since API layers are sensitive to platform changes between major updates.
Core Commands You Will Use
The command group is accessed through /mcros and requires the mcrosapi.admin permission or operator status. Tab completion is available for every supported subcommand, which makes discovery painless even for new admins.
- /mcros all_plugins — displays the registered MCros plugins along with their current configuration groups.
- /mcros can_use <plugin> — checks whether the specified plugin is allowed for use and enables access when it is not yet allowed.
- /mcros authregister — shows information about the authentication and registration plugin.
- /mcros lobbyset — shows information about the lobby, spawn, hub, and warp management plugin.
- /mcros autominer — shows information about the automated mining plugin.
- /mcros help — displays the complete help for the command group.
The can_use action deserves special attention. It is intended for quickly allowing a registered plugin to be used by the server or by an individual player. That makes it a fast troubleshooting tool when a player reports that a feature is not working, or when you want to grant access on the fly without digging through permission files.
How to Install MCrosAPI
Installation is straightforward and follows the standard pattern for server-side plugins. Here is the short version of how to install it:
- Stop your Minecraft server completely before making changes.
- Place the MCrosAPI plugin file into your server's plugins directory.
- Start the server and let the plugin generate its SQLite database and configuration files.
- Confirm the command group is active by running /mcros help in-game or from the console.
- Grant the mcrosapi.admin permission to the staff members who need it.
Once installed, other MCros plugins will detect the API layer automatically and register themselves. If you are managing a larger network, keeping a consistent version across every server prevents mismatched registration data.
For administrators who prefer a hands-off approach, the foxygame.net launcher can handle the whole setup for you: it lists MCrosAPI in its add-on catalog and installs it with a single click, so your plugin folder stays organized without manual file transfers. That same launcher also keeps MCrosAPI updated automatically, which matters because API layers need to stay aligned with the plugins that depend on them.
Why It Belongs on Your Server
MCrosAPI is not the flashiest plugin you will ever add, and that is precisely the point. It is infrastructure. By centralizing registration, access checks, and plugin metadata into one SQLite-backed layer, it removes friction from every MCros plugin that comes after it. Admins get predictable commands, players get faster access resolution, and localization support means the interface reads naturally whether your community speaks English or Russian.
If you are building out an MCros-based setup, start here. Download MCrosAPI for Minecraft, verify your server version, and let the API layer do the quiet work that keeps everything else running smoothly.