MineServer Admin is a control panel for the Minecraft server you already rent. Drop one small plugin into it and run everything from your phone or any browser: console, players, plugins and mods, settings, and who is allowed to touch them. Your server stays exactly where it is.
Your host runs the machine, and it should carry on doing that. Everything else, the part you open every day, moves to a panel built for it.
| The job | Your host's panel | MineServer Admin |
|---|---|---|
| Start a stopped server | Yes. The machine is theirs. | No. A plugin inside the server cannot start one that is off. |
| Change RAM, plan, billing | Yes. That is your account with them. | No, and we never ask for those details. |
| Backups of the machine | Yes, on whatever schedule your plan gives you. | No. The desktop app backs up servers it runs on your own computer. |
| Move Minecraft version | The version installer. On a rented server it is the only thing that can swap the files. | We check every plugin against the new version first, so you know what breaks before you move. Pro |
| Install a plugin | Upload a jar you found yourself. | Search Modrinth filtered to your version and loader, one click. Pro |
| Update a plugin | Check the project page yourself, upload again. | An Update button only when a build exists for your version and loader. Pro |
| A missing dependency | One line in the log after the server skips it. | Named at the top of the list before you restart. Pro |
| Edit a plugin's config | A text box in the file manager. | An editor that checks YAML and JSON as you type. Pro |
| Player history | None. | Everyone who ever joined, playtime, sessions, deaths. |
| A scheduled restart | Blunt, and nobody in the world is warned. | Chat warnings first, Discord alert after. Pro |
| Co-admins | Share the login that is also your billing account. | Operator and viewer roles with an audit log. Pro |
| On a phone | The desktop panel, shrunk. | Overview, Console, Chat and Players laid out for it. |
Nothing is moved and nothing changes about how your server runs. Uninstalling is deleting one file, or typing /msa unpair.
A host's panel gives you a file manager. You work out which build fits your server, download the jar, upload it, then open the config in a text box and hope the indentation is right. MineServer Admin reads the folder instead. It knows what each jar is, whether a build exists for your Minecraft version and your loader, what it needs in order to load, and what is inside its settings files. It works the same on your phone, in a browser and in the desktop app.
Every jar in the folder is identified by its checksum, so the list shows real names, icons and version numbers, including for the plugins you uploaded yourself long before you found us. Anything Modrinth does not recognise is still listed, still has its switch, its settings and its remove button.
A Paper build and a Spigot build of the same release are different files, published minutes apart, and Modrinth lists the newest first whichever it is. We rank the Bukkit family for a Paper server and match the loader tag exactly for Fabric and NeoForge, so what lands in the folder is the file your server can actually load. A plugin or mod with no build for your loader is reported as having none rather than handed to you anyway.
Your server runs Paper.
The Update button appears when a newer build exists for your Minecraft version and your loader, and not before. Nothing here offers you a jar that would fail on start, and nothing quietly moves you onto a build made for different server software. The count of what has an update is at the top of the list.
Each jar says what it needs, in its plugin.yml, its fabric.mod.json or its neoforge.mods.toml, and jars bundled inside other jars count. Anything missing is named at the top of the list. Without that, a plugin whose dependency is absent simply does not load, and the only sign is one line in a start-up log nobody reads.
Open a plugin's settings files from its row: line numbers, search, and colours that tell a key from a value. YAML and JSON are checked as you type, so a stray tab or a missing bracket is caught here instead of stopping the plugin from loading. Save is greyed out while the file is broken. In the desktop app the previous version of the file is kept as a .bak beside it.
Before a version change, ask what happens to everything installed. Each plugin comes back Ready, Update first, No build yet, or Not on Modrinth for the ones that never came from there. If something has no build for the new version, you find out before the world is converted, not after.
MSA Connect is one jar. It goes in the folder your server already loads plugins or mods from, it makes one outbound connection, and it never listens on a port. Nothing to forward, no address to enter, and nothing about how your server runs changes.
Not out yet. These are the steps you will follow the day it is.
Three builds, one file each. Pick the one your server runs.
msaconnect-paper.jarplugins/One file covers every supported Paper version. The name of the file does not matter, the folder does.
msaconnect-fabric.jarmods/The mod reads the server's own classes, and those move between Minecraft versions, so there is a build per version.
msaconnect-neoforge.jarmods/The mod reads the server's own classes, and those move between Minecraft versions, so there is a build per version.
At launch the plugin is on Modrinth, and the Paper build is also on Hangar, and every download here carries its sha256 sum.
Open your host's file manager, go to your server's folder, and upload the jar straight into plugins on Paper, or mods on Fabric and NeoForge. Upload it as it is: do not unzip it.
| Your host's panel | Where the files are | How you restart | Where the console is |
|---|---|---|---|
| Multicraft | Files, then FTP File Access, then your server's folder | Restart, on the server page | The Console tab, in the box at the bottom |
| Pterodactyl | The Files tab | Restart, above the console | The Console tab, in the command box |
| Pelican | The Files tab | Restart, above the console | The Console tab, in the command box |
| Another panel | Your host's own file manager | Your host's own restart button | Your host's own console, if it has one |
The panel asks which panel your host gives you and puts these three steps in that panel's own words, so you are always looking for something that exists.
Restart from your host's panel and wait for the server to finish starting. The console prints one line:
[INFO] MineServer Admin Connect is not paired. Make a code on the website and run /msa pair with it.That line is how you know the jar loaded. The /msa command does not exist until the server has come up once with the file in place.
Open app.mineserveradmin.com, sign in, and press Add a server. The panel shows a code like 63EK-34MC. It lasts ten minutes and works once, so make it after the restart rather than before. Codes never contain 0, 1, I, L or O.
Type this into your host's console, with your own code:
/msa pair 63EK-34MCCase does not matter and the dash is optional. /msa needs an operator: permission level four on Fabric and NeoForge, and the msaconnect.admin permission on Paper, which operators have by default.
Some panels give you a file manager and nothing else. In that case, in your server's folder, make a folder called config, a folder called mineserveradmin inside it, and a file called agent.json inside that, containing exactly this with your own code:
{ "code": "63EK-34MC" }Then restart once more. The plugin redeems the code on the way up and rewrites the same file with the token it was given, so the code is not left lying around. The path is the same on all three builds: config/mineserveradmin/agent.json, in the server folder beside your world, not inside plugins or mods.
The console answers twice:
[INFO] Pairing with the cloud.
[INFO] Paired. Open app.mineserveradmin.com to see this server.The Add a server page opens the server the moment it connects. Its console, chat and players are live, and there is nothing to refresh.
Any time after that, /msa status answers in one sentence:
> msa status
Connected to the cloud as srv_9f3a1c2e.It says Paired as srv_9f3a1c2e but not connected right now. when the connection is down, and Not paired. when it never paired. To undo the whole thing, /msa unpair forgets the token and the server stops talking to us. Delete the jar and the config/mineserveradmin folder and nothing of ours is left.
The jar is in the wrong folder, or the server has not restarted with it in place. Paper loads from plugins, Fabric and NeoForge from mods. Check the file is still there after the restart, then search the start-up log for "MineServer Admin Connect". No line means it never loaded.
Each build is for one loader. The Fabric jar will not load under NeoForge, and neither loads on Paper. The Fabric build also needs Fabric API in the mods folder; without it the loader refuses it by name in the first few lines of the log.
A code lasts ten minutes and works once. Press Add a server again for a fresh one and type it again. A failed attempt leaves nothing behind. You will see "That code has already been used. Make a new one from the website." if you typed one twice, and either "That is not a pairing code. Make a new one from the website." or "That code is not one we gave out. Make a new one from the website." if a character was mistyped. Codes never contain 0, 1, I, L or O, so a character that looks like one of those is something else.
The server could not open an outbound HTTPS connection. A few hosts firewall outbound traffic by default; ask yours to allow an outbound connection to app.mineserveradmin.com on port 443. Nothing inbound is ever needed, no port is forwarded, and the plugin never listens.
That is a Vanilla server, and it loads neither. Switch it to Paper, Fabric or NeoForge with your host, or run the server from the MineServer Admin desktop app, which handles Vanilla itself.
Pairing worked, but the server cannot write in its own folder. Fix the folder permissions in your host's file manager and run /msa pair again with a fresh code.
The jar goes in through your host's file manager, which is a job for a keyboard. Everything after that is a web page you open on whatever is in your hand. Overview, Console, Chat and Players are laid out for a phone. The rest are the desktop layout in a browser window. No app to install; it is a web page. When somebody says the server is lagging, you read the console, run the command and answer them in chat without going to find a laptop.
On a rented server the login that restarts the machine is the login that holds your card. Here, the people who help you run the server get their own way in, with their own limits.
An owner manages the server and who else is on it. An operator runs it day to day: the console, commands, restarts, players, whitelist and settings. A viewer sees everything and cannot type.
A viewer's command is refused on the way through and written down, rather than merely greyed out in the browser. A demotion takes effect on a connection that is already open. The last owner cannot be removed.
Who ran what, when, and from where. Filter it, export it as CSV, and rotate the plugin's token in one click if you ever think it has been seen.
You are putting somebody else's jar on a server you pay for. Here is the whole list, in plain words, rather than a sentence that sounds reassuring.
Console text passes through our servers today, so in principle we can see it. End-to-end encryption between your browser and the plugin is being built next, so that a console line is unreadable to us.
If our panel is down your server carries on. The plugin only passes on the buttons you press, so if it cannot reach us nothing reaches your server, and your host's panel keeps working exactly as it does now. When we come back the plugin reconnects on its own and replays the console lines your browser missed.
Sign in with a link, a passkey or an authenticator app. Passkeys are bound to this site and cannot be phished, and an account with two-factor on cannot be entered by a magic link alone. Every signed-in browser is listed and can be ended. An account with neither a passkey nor an authenticator is only as safe as its mailbox, so add a passkey on the first sign-in.
There is nothing to forward. The token is written to config/mineserveradmin/agent.json on your own server, readable only by the account your server runs as, and it is never printed to the console or the log. Rotate it from Members, or type /msa unpair and the plugin forgets it. Delete the jar and the folder and nothing of ours is left. The source is not public today.
Fourteen screens. Twelve are in both the desktop app and the browser. Backups is the desktop app's, because a plugin inside a server cannot zip the machine it runs on. Members is the browser's, because it is about your account rather than your computer. These are real screens from a build in development, so small things may still move.
Players, TPS, memory and CPU in four instruments, with the last lines of the console beside them. Quick actions for day, night, clear weather, save and an announcement, each one click.
Every line the server prints, with INFO, WARN and ERROR filters, timestamps, pause and copy. Type a command at the bottom and the panel completes it and keeps a history of what you ran. Plugin colours are kept.
Read what people are saying and answer as the server. Joins and leaves show inline, and a badge on the sidebar tells you something was said while you were on another screen.
Who is on, who has op, who is banned, and everyone who ever joined with playtime, sessions, deaths and last seen. Kick, ban, op, teleport or change game mode from the row. Click a name for a profile with stats, inventory, records and advancements.
Players online over time, when people actually play, who plays most, for the last day, week, month or all time. Built from the panel's own log of joins and leaves, with the server's older logs imported once.
Turn the whitelist on, add and remove names, and see who is on it, all while the server runs. No restart and no editing JSON.
Difficulty, game mode, PvP, max players, view distance, the MOTD in colour with a preview, and the server icon. Applied live where the server allows it, otherwise saved and flagged restart required.
Keep inventory, mob griefing, daylight cycle, fire spread, command blocks and the rest, as toggles and numbers with a line on what each one does. Applied live.
Back up the world into the server folder, restore an older one, open the folder, and read the latest log without leaving the app. The server is asked to save first.
The full story is in Plugins and mods above. In short: installed plugins with versions and switches, a Modrinth search filtered to your server, and an editor for their settings files.
Scheduled restarts with chat warnings before they happen, and Discord alerts for starts, stops, crashes, joins and leaves. On the desktop, scheduled backups with a keep count and a second copy folder.
A check from outside tells you whether your address is reachable, so you know whether the problem is the server or the way in. In the desktop app it also shows the three addresses that matter, this computer, your Wi-Fi and the internet, and offers a playit.gg tunnel if you cannot port forward.
A newer Paper build, a newer version of Fabric or NeoForge, or a new Minecraft version, with what it means for your world. Plugins are checked against the new version before you move. On the desktop app the world is backed up and the old server file kept before anything is swapped.
Invite somebody by email and choose what they can do. An operator runs the server day to day; a viewer sees everything and changes nothing. Every action anybody took is in the audit log, with who and when, and the plugin's token can be rotated if you ever think it has been seen.
The desktop app sets up and runs Paper, Vanilla, Fabric and NeoForge on your own machine. It fetches the server software and a matching Java, writes the config, and runs the server as its own process.
Free is the whole panel for one server, forever, with no card and no trial clock. Pro is for the plugin and mod manager, the readiness checks and the automation that runs while you are asleep. It also lifts the one-server limit and adds members with roles. The price is announced at launch.
The whole panel for the server you have: console, chat, players, whitelist, settings, game rules, analytics, network and updates, from wherever you are.
For the server you keep, and the people who help you keep it. Everything in Free, plus the parts that turn a panel into a team's tool.
One plan covers all three ways in: the same account unlocks Pro on your phone, in a browser and in the desktop app. If you stop paying, servers past the free count go read-only until you are within it, and everything else keeps working on Free. Deleting a server deletes its analytics and audit log with it. Your worlds and files are never on our side to begin with: the plugin talks to the panel, and the panel holds no backups.
For running the server day to day, yes. The console, chat, players, whitelist, settings, game rules, plugins and mods, the analytics and who is allowed to touch any of it all move here. Your host's panel keeps the jobs that belong to the machine: starting a stopped server, changing RAM or plan, the machine's own backups, the Minecraft version installer, FTP and billing. Keep both, and stop opening one of them.
If your host lets you upload a file into the plugins or mods folder and restart the server, yes. That covers Multicraft, Pterodactyl and Pelican, and the panels hosts write themselves. The plugin listens on no port and asks for nothing inbound, so there is no firewall rule to request and no port to forward. A few hosts block outbound traffic by default and would need to allow an outbound HTTPS connection.
No. We are a control panel, not a host. Your server stays with the hosting provider you already pay, or on your own computer, and we never run it, move it or hold a copy of it. A small plugin inside the server connects it to the panel, and deleting that one file undoes the whole thing.
Judge it on what it does. The plugin listens on no port, makes one outbound connection, and writes its token to config/mineserveradmin/agent.json, readable only by the account your server runs as and never printed to the console or the log. Every download carries its sha256 sum, so you can check the file you were given is the file we published. The source is not public today, and uninstalling is deleting one file or typing /msa unpair.
Console text passes through our servers, so in principle yes, and we would rather say that than pretend otherwise. We keep the last 500 console lines per server in that server's own room so a browser that joins late has something to read; they never go into a log file or the main database, and they go when the server does. End-to-end encryption between your browser and the plugin is being built next, and once it is on, a console line is unreadable to us.
Your server carries on. The plugin only passes on the buttons you press; if it cannot reach us, nothing reaches your server and nothing happens to it. Your host's panel keeps working exactly as it does now. When we come back the plugin reconnects on its own and replays the console lines your browser missed.
Yes, for one server. Free is the whole panel for that server: console, chat, players, whitelist, settings, game rules, analytics and updates, from your phone, a browser or the desktop app. Passkeys and two-factor are free for everyone. Pro is one small monthly subscription and its price is announced at launch.
Yes, a monthly one, and you can cancel any time. Nothing is deleted when you do: servers past the free count go read-only until you are within it, and everything else keeps working on the free plan. The price is announced at launch.
No. The web panel talks to the plugin inside your server and needs nothing on your computer. The desktop app is for a server on a computer of your own: it sets one up and runs it. Link it to the same account and a server it runs shows up in the browser too.
One Paper build for Paper and Purpur, 1.18.2 and newer, Java 17 or newer. Folia is not supported and Spigot is not on the list. Fabric and NeoForge builds are made for one Minecraft version at a time; 26.2 and 26.3 today. A Vanilla server loads neither plugins nor mods, so run one of those from the desktop app instead.
Any host that lets you upload a file and restart the server: Multicraft, Pterodactyl and Pelican panels, and the panels hosts write themselves. If your host gives you no console, the pairing code goes in a file instead of a command. Nothing about your plan, your RAM or your address has to change.
Yes. Open a plugin's settings files from its row, in an editor with line numbers, search and colours that tell a key from a value. YAML and JSON are checked as you type, and Save stays off while the file is broken. Formats we cannot be certain of are saved exactly as you typed them. The config editor is part of the plugin and mod manager, which is part of Pro.
You sign in with a link sent to your email address, a passkey or an authenticator app, and there is no password to leak. Passkeys are bound to this site and cannot be phished, an account with two-factor on cannot be entered by a magic link alone, and every signed-in browser is listed and can be ended. An account with neither a passkey nor an authenticator is only as safe as its mailbox, so add a passkey on the first sign-in.
No date yet, and nothing is downloadable today. The free plan comes first, then Pro. Leave your email address and you will get one message the day it lands.
One jar in your plugins or mods folder.
One command in the console you already have.
About a minute, and nothing to port forward. Free for one server.