Everything here is a Dalamud plugin for Final Fantasy XIV, written by Johnneylee Jack Rollins and open source. Add the repository below to XIVLauncher once, and they install and update like any other plugin. You can also build any of them yourself and skip this page entirely — that path is kept on purpose.
https://spacegho.st/mods/ffxiv/plugins.json
/xlsettings → the Experimental tab./xlplugins → All Plugins → search for the plugin you want → Install.Dalamud will warn you that this is a third-party repository whose plugins nobody but their author has reviewed. That warning is correct, and it is true of every custom repository. Every plugin here is open source and built in public on GitHub Actions: the zip the installer downloads is the one the workflow built from the tagged commit, and you can read both. Install it because you trust the author, not because a page said it was fine.
Live versions come from plugins.json, the same file the installer reads.
Eorzea is a terminal multiplexer.
A real terminal inside the game: a Quake-style dropdown, floating windows, and terminals pinned to panels in the world. It talks to shells on your own machine through ghostty-agent, which you run yourself — the plugin never opens a shell on its own. /term toggles it. With Umbra installed, its toolbar widget shows the agent's status and a popup terminal.
Needs: ghostty-agent running on the machine the game runs on.
Talk to a local AI model in game, with XivMcp's tools.
An in-game chat with a model running on your PC — Ollama, LM Studio, llama.cpp, anything with an OpenAI-compatible API. It sets itself up with a wizard that reads your GPU and recommends models that fit its memory, keeps threads in SQLite, streams replies, and can run a shared benchmark whose results feed the community model leaderboard. Nothing is sent to a cloud, and there is no Python to install.
Needs: a local model server, and XivMcp for in-game tools (below).
About · Source · Releases · Leaderboard
Model Context Protocol server for Final Fantasy XIV.
Exposes game state, game data and opt-in actions to MCP clients — Claude Code, Codex, Almanac — over a loopback HTTP server. Anything that would change your game is approved in game first, one prompt at a time. It has an Umbra toolbar widget too.
Needs: an MCP client on the same machine.
It has a stable release, so it shows under All Plugins straight away. A newer test build is there too, for those who opt in.
Launch Linux desktop apps into the game world.
For the game running under Wine on Linux: lists the host's applications and opens them as panels in the world, through Ghostty's remote windows. An app launcher for Eorzea.
Needs: Ghostty and ghostty-agent, on a Linux host.
It has a stable release, so it shows under All Plugins straight away. A newer test build is there too, for those who opt in.
Your own classic games as game panels, with saves kept in step across your machines.
For the game running under Wine on Linux: /arcade is a wall of the classic games you own, Final Fantasy first, started in RetroArch (or PCSX2 and DuckStation) on the host and shown as panels in the world through Ghostty. Every save lives in one folder that Syncthing copies between your machines. It downloads no games or BIOS files, and cover art only if you turn that on.
Needs: a Linux host, RetroArch and your own game files. Ghostty for panels and Syncthing for save sync are optional.
Light a lantern for your friends: a friend list, 1:1 chat and channels of your own, peer to peer.
Friends by one-time invite, presence and a note you type, 1:1 chat that waits for a friend who is offline, and channels you make, peer to peer over iroh with no Lantern server. An opt-in channel carries the author's signed announcements. Off until you turn it on; nothing from the game is read or sent. With the default relays, n0's relay servers see your IP address and when you are online; "relays off" contacts no third party.
Needs: friends running XivLantern too.
Which way to go, softly: a bead, a trail along the path and a pointing glove.
A softly pulsing bead ahead of you, a trail that follows the walkable path when vnavmesh is installed, and the game's own pointing glove (or, as an option, the Wind-up Cursor minion's model) showing the way to a target, your map flag or your quest's next step. It only points; it never moves your character.
Needs: nothing; vnavmesh, if installed, makes the trail follow the path.
Each plugin has a testing channel: the newest build, cut before a release, for friends who do not mind a rough edge. Opt in per plugin — nothing opts you in globally.
/xlsettings → Experimental → tick Get plugin testing builds, Save and Close./xlplugins → right-click the plugin's entry → tick Receive plugin testing versions, then update the plugin.A testing build is whatever the author last pushed a -test tag for. It is built by the same workflow, from a tagged commit, and it can be worse than the release. Untick the box and reinstall to go back.
Nothing here needs this page or this repository. Every plugin builds from its source checkout with the .NET SDK, and XIVLauncher loads it straight from your build folder — this is how the author runs them, and it is the honest way to read the code before you trust it.
tools/build.sh. Almanac: dotnet build dalamud/Almanac.Dalamud.slnx -c Release. XivMcp, XivDesktop and XivArcade: dotnet build <name>.slnx -c Release. Each README says where the output lands, and each build needs Dalamud's reference assemblies — an XIVLauncher install already has them (Linux ~/.xlcore/dalamud/Hooks/dev/, Windows %APPDATA%\XIVLauncher\addon\Hooks\dev\)./xlsettings → Experimental → Dev Plugin Locations → add the folder holding the built <Name>.dll and its <Name>.json (under Wine, as a Z:\… path) → + → Save and Close./xlplugins → Dev Tools → Installed Dev Plugins → enable it.A dev plugin never auto-updates, which is the point: it is exactly the code in your checkout. If you later want the one-click path, disable the dev plugin first so the two copies cannot fight over the same name.
Umbra.Ghostty and Umbra.XivMcp add a toolbar button and a popup to Umbra. They are Umbra plugins, not Dalamud plugins: Dalamud's installer cannot install them, so a Dalamud plugin repository cannot list them, and this one does not. They ship with their plugin's source (Ghostty's shim/, XivMcp's src/), and you drop the built DLL into Umbra's plugin folder yourself. Each README covers it. Both are optional; the plugins work without Umbra.