Friends-List Join for Your Minecraft Server

How to make your own server show up in Minecraft's Worlds tab, the way a friend's game does, so Xbox, iPad and phone players tap it instead of typing an address. Xbox players can't add a custom server at all, which is the main reason to do this. This is how we set up ours, written so you can build the same thing.

How it works

You make a throwaway Microsoft account that does nothing but sit online. A small program, MCXboxBroadcast, signs in as that account and tells Xbox Live it is hosting a world, using your server's name. Anyone friends with that account sees the world in their Worlds tab under Friends. When they tap it, Xbox Live passes the join to the bot, the bot points it at your server, and the player's device then connects straight to your server. No relay sits in the middle, and nobody types an IP or port.

player taps "Your Server" in Worlds
   -> Xbox Live -> bot account (MCXboxBroadcast)
   -> bot hands the join to Geyser on your server
   -> player's device connects directly to your server, UDP 19132

Why a throwaway account: the bot's own README says it "emulate[s] some features of a client which may or may not be against TOS" and suggests an alt account "in case the account is banned." If Microsoft ever bans anything, it's that account and not yours or your kids'.

What you need

PieceWhat it is, and where to get it
A Java serverPaper (we run 26.3). Any always-on machine that can run Java 25.
GeyserPlugin that lets Bedrock players (Xbox, iPad, phones, Windows) join a Java server. geysermc.org/download, the Spigot/Paper build.
FloodgatePlugin that lets those Bedrock players in without a paid Java account. Same download page.
MCXboxBroadcastThe bot. github.com/MCXboxBroadcast/Broadcaster, Releases. It comes as a Geyser extension or a standalone jar; we run the standalone jar (Java 17 or newer).
A throwaway Microsoft accountFree, made at signup.live.com. Its gamertag is public, so give it one that carries no family names, place or machine names.
A DNS name for your home IPOnly for joins from outside your house. A free dynamic DNS name such as yourname.duckdns.org, kept up to date by your router or a small updater.
One port forwardOnly for joins from outside: UDP 19132 on your router, to the server machine.

Bedrock is the regular Minecraft on Xbox, iPad, iPhone, Android and Windows. Java Edition players can't use this route; they join by address as usual.

Setup, in order

  1. Run Paper with Geyser and Floodgate

    Put Geyser-Spigot.jar and floodgate-spigot.jar in Paper's plugins folder and start the server once so Geyser writes its config. Then edit plugins/Geyser-Spigot/config.yml. Ours, with placeholders:

    bedrock:
      address: 0.0.0.0
      port: 19132
      transport: nethernet
      advertise-addresses:
      - yourname.duckdns.org
      stun-discovery: false

    transport: nethernet is the step Geyser's setup page now lists for current Bedrock versions. Leave address at 0.0.0.0; Geyser's docs say NetherNet does not work bound to 127.0.0.1. advertise-addresses is where joining players are told to connect. List your LAN address too if you want home players to skip the internet round trip. Restart the server.

  2. Open the firewall on the server machine

    Allow inbound UDP 19132 to Java. TCP 19132 only needs to be reachable from your own network.

  3. Make the throwaway account

    Create the Microsoft account, sign in to Minecraft or the Xbox app with it once so it gets a gamertag, and write the gamertag down. Keep its password somewhere safe. You'll need it again whenever the bot's sign-in expires.

  4. Start the bot and sign it in

    Put MCXboxBroadcastStandalone.jar in its own folder on the server machine and run it:

    java -Xmx256m -jar MCXboxBroadcastStandalone.jar

    On first start it prints a code. Open microsoft.com/link in a browser, enter the code, and sign in as the throwaway account. The bot keeps its sign-in token in a cache folder next to the jar, so treat that folder like a password. Stop the bot once it has written config.yml.

  5. Point the bot at your server

    In the bot's config.yml, set the target server to the same machine, 127.0.0.1 port 19132. Then the settings we changed:

    host-name: Your Server        # the name players see
    world-name: Your World
    max-players: 6
    auto-friend: false            # see "Who gets in" below
    initial-invite: false         # no invite pop-up on new friends
    # friend expiry:
      enabled: false              # else idle friends get dropped

    Turn friend expiry off. With it on, a player who hasn't joined for a while is unfriended and the server silently disappears from their Worlds tab.

  6. Run the bot as a service

    It has to start at boot and restart if it exits. We use a Windows scheduled task (at startup, restart on failure); on Linux, a systemd unit does the same job. We also restart it when its log says no more signals arrive. That line means the bot lost its Xbox connection and stays running but deaf, and nobody can join until it restarts. It happened to us once and the server sat invisible for about 40 hours.

  7. For joins from outside your house

    Forward UDP 19132 on your router to the server machine, and keep your dynamic DNS name current. Geyser looks up advertise-addresses when it starts, so after your home IP changes, outside joins fail until the next restart. A nightly restart covers it.

    Geyser's port forwarding guide says to forward TCP and UDP 19132. That is for players adding your server by address. For friends-list joins the handshake goes through Xbox Live, so we forward only UDP and keep TCP closed to the internet. A phone on mobile data with no VPN joined ours that way.

Who gets in

Only accounts that are friends with the bot, plus friends of anyone already on the server, see your world. With auto-friend: true the bot accepts every friend request, so anyone who finds the gamertag gets in. We keep it off. To let someone in, they send the bot a friend request from Minecraft (Play, Friends, Add Friend, search the gamertag), and you accept that one request, for example by signing in to the Xbox app as the bot account. We patched our bot to accept only gamertags we put on a list, which is extra work you can skip.

For a child account, the parent must allow "Add friends" and "Join multiplayer games" in Xbox Family Settings. An Xbox also needs Game Pass Essential for online play.

If you want to limit who can actually play, and not just who can see it, turn on Paper's whitelist as well.

Test it

When it breaks

What you seeFix
Server missing from everyone's Worlds tabCheck the bot is running and logging Updated session!. If it's running but silent, restart it (the deaf-bot case above).
Bot log asks for a microsoft.com/link codeIts sign-in expired. Enter the code and sign in as the throwaway account again.
Shows up but won't connect, only from outsideYour home IP changed, or the forward is gone. Restart the server so Geyser re-reads the DNS name, and check the router rule.
Missing for one player onlyThey aren't the bot's friend (or expiry dropped them), or their account's Family Settings block multiplayer.
"Outdated server"Players' devices updated before Geyser did. Update Geyser and Floodgate. We check for new builds twice a day and swap them in when nobody is on.

Limits and risks

Sources, checked 2026-11-18