DalamudMCP: FFXIV MCP Server for Dalamud

DalamudMCP is a Windows-local Model Context Protocol (MCP) server and Dalamud plugin for Final Fantasy XIV (FFXIV / FF14). It connects MCP-compatible AI clients and a command-line interface to a running game session through a current-user-only local bridge.

日本語: セットアップガイド

[!IMPORTANT] DalamudMCP requires Windows, Final Fantasy XIV, and Dalamud. Observation tools are enabled by default, while actions and unsafe integrations require explicit opt-in from the plugin UI.

Requirements

• Windows with Final Fantasy XIV running through XIVLauncher and Dalamud
• .NET 10 SDK for building and running the CLI from source
• a local Dalamud development installation for building the plugin

Quick Start

Build the plugin and CLI:

.\build\restore.ps1
.\build\build.ps1 -NoRestore

Load src/DalamudMCP.Plugin/bin/Debug/DalamudMCP.dll as a development plugin, then start the stdio MCP server:

dotnet run --project .\src\DalamudMCP.Cli\DalamudMCP.Cli.csproj -- serve mcp

After version 1.1.0 is available on NuGet.org, the CLI can also be run without a permanent installation:

dnx [email protected] --yes serve mcp

For plugin loading, HTTP transport, security settings, and release packaging, see Install And Run.

How It Works

The current codebase is built around:

• one handwritten operation file per tool
• the same operation definition drives both CLI and MCP
• the plugin owns live game execution
• the CLI and MCP layers talk to the plugin over a local named pipe

What You Get

• direct CLI commands such as player context and inventory summary
• MCP over stdio with serve mcp
• MCP over bearer-authenticated local HTTP with serve http
• plugin auto-discovery so normal CLI usage does not need a manual pipe name
• a plugin settings window that shows runtime health and can start the bundled HTTP server
• generic game action execution, Lumina Excel exploration, and plugin lifecycle/package management

Safety Defaults

DalamudMCP is observation-first, but it can expose broad mutation capabilities when the user enables them.

• observation tools are enabled by default
• action tools are default-off until you enable them in the plugin UI
• unsafe integration tools are default-off and hidden behind a separate developer toggle
• an explicit capability policy overrides the legacy toggles and is enforced again for every invocation
• confirm-once policies show the exact arguments in the plugin UI and consume approval after one matching retry
• policies can constrain plugin names, action IDs, jobs, territories, sheets, callgates, targets, result counts, and calls per minute
• denied capabilities are omitted from tools/list