ExileAPI Plugin Dev MCP
The ExileAPI Plugin Dev MCP server provides a bounded development workflow for creating, building, and inspecting ExileAPI plugins. It discovers local ExileAPI references and source-plugin symlinks, scaffolds new Git-based plugin projects, and prepares them for in-game Build/Reload. Build errors are accessible via a bounded read of Errors.txt. Runtime status can be monitored through a read-only status file written by the ExileAPI bridge. Game state is inspected through manual bridge snapshots: you can inspect snapshot structure, read specific dot-paths, list known successful paths, and manage capture profiles for targeted or refined captures. Plugin example discovery searches local C# examples and provides an exApiTools catalogue link. Finally, ExileAPI core snapshot analysis allows listing, header-only inspection, path filtering, and bounded member reading from .exapisnap files without loading multi-gigabyte contents into memory.
Creates and manages independent Git repositories for ExileAPI plugins, linking them into the ExileAPI source tree for version control.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ExileAPI Plugin Dev MCP create a new plugin named MyPlugin and link it into the source tree"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ExileAPI Plugin Dev MCP
An MCP server that gives coding agents a bounded development workflow for ExileAPI plugins. The repository also contains a disabled-by-default ExileAPI companion plugin reserved for a future read-only telemetry bridge.
Scope
Detect local ExileAPI compiler references.
Create an independent Git repository under
~/ExileApiPlugins/<PluginName>and link it intoPlugins/Source/<PluginName>.Prepare the linked source tree for ExileAPI's in-game Build/Reload action.
Read the resulting bounded
Errors.txtoutput.
It deliberately does not expose DevTree's dynamic C# evaluator, read or write process memory, or send game input. The current companion plugin has no IPC surface; a future runtime bridge must be separately reviewed and read-only.
Related MCP server: mcdev-mcp
Local development
python3 -m venv .venv
.venv/bin/pip install -e .
.venv/bin/exileapi-plugin-devController-side verification
The collection-index path resolver is covered by a game-independent .NET test project:
"${DOTNET_ROOT:-$HOME/.dotnet}/dotnet" test \
tests/ExileApiPluginDevBridge.Core.Tests/ExileApiPluginDevBridge.Core.Tests.csprojA full bridge build additionally needs the matching ExileCore.dll and GameOffsets.dll directory:
"${DOTNET_ROOT:-$HOME/.dotnet}/dotnet" build ExileApiPluginDevBridge.csproj \
-p:EnableWindowsTargeting=true \
-p:exapiPackage=/path/to/pinned/exileapi-runtimeThe main bridge project explicitly excludes tests/**/*.cs so ExileAPI's source compiler does not compile xUnit sources or nested test build artifacts.
The repository is linked into ExileAPI source plugins at:
~/ExileApi-Compiled/Plugins/Source/ExileApiPluginDev -> ~/ExileApiPlugins/ExileApiPluginDev
ExileAPI owns compilation and reload. Use its in-game Build/Reload button after source changes; no Linux build worker is required.
Errors.txt may be retained after a successful build, so the MCP also reports its modification time.
The enabled bridge writes a small read-only runtime-status.json after successful initialisation and area changes. Its default path matches the existing Z: mount used by ExileAPI on this machine; it can be changed in the plugin settings.
For larger diagnostics, use Capture snapshot in the bridge's ExileAPI menu. It writes game-snapshot.json only when pressed. Defaults are: depth 6, 500 total nodes, 100 collection entries per node, 512 characters per string, and no memory addresses. read_game_snapshot reads the frozen result through MCP.
Finding an unknown live-game struct
Do not add properties or profiles to the bridge merely because an agent does not yet know the required object path. Use the MCP scan loop instead:
begin_game_struct_scan(goal, roots)prepares one shallow Discovery capture for one to three plausible DevTree roots.Let the bridge execute the request, then use
inspect_game_snapshotandread_game_snapshot_pathto examine only relevant paths.continue_game_struct_scan(goal)follows at most threedepth_limit/node_limitbranches with another shallow capture.Repeat until the exact property is evidenced. Only then use a deep
Targetedcapture.
This keeps snapshots small and makes a bridge change an evidence-based exception rather than the normal way to discover data.
ExileAPI core snapshots
list_core_snapshots, inspect_core_snapshot, find_core_snapshot_paths, and read_core_snapshot_member work with ExileAPI's snapshots/*.exapisnap files. The indexer reads 512-byte TAR headers and seeks over member bodies; it never extracts or feeds a multi-gigabyte snapshot to the model. find_core_snapshot_paths supports required and excluded path terms; read a member only after narrowing it through the indexed path list.
Available Tools
19 toolsdiscover_environmentC
Report local ExileAPI references and the source-plugin link used by ExileAPI Build/Reload.
Inputs: exileapi_root. Returns: result
find_core_snapshot_pathsA
Return only indexed snapshot paths matching all include terms and none of the excluded terms.
Inputs: include_terms (required), snapshot_name (required), limit, exclude_terms. Returns: result
find_plugin_examplesB
Find relevant local ExileAPI C# examples and return the exApiTools plugin catalogue link.
Inputs: query (required), max_results. Returns: result
inspect_core_snapshotC
Build/read a header-only snapshot index and return a bounded table of matching archive paths.
Inputs: snapshot_name (required), limit, query, path_prefix. Returns: result
inspect_game_snapshotB
Return a bounded table of bridge snapshot paths, types, list sizes, and truncation markers.
Inputs: query, max_entries. Returns: result
list_core_snapshotsA
List ExileAPI's .exapisnap files without reading their multi-gigabyte contents.
Inputs: no named parameters. Returns: result
list_game_snapshot_path_profilesA
List reusable target-path profiles saved for the current ExileCore build.
Inputs: no named parameters. Returns: result
list_known_game_snapshot_pathsB
List successful bridge snapshot paths remembered locally for the current ExileCore build.
Inputs: query. Returns: result
prepare_game_snapshot_captureC
Prepare a bounded bridge capture profile; the user must still press Capture snapshot in-game.
Inputs: profile (required), conditions, custom_sections. Returns: result
prepare_game_snapshot_path_profileA
Prepare a deep targeted capture from a saved path profile, optionally waiting for simple bridge conditions.
Inputs: name (required), conditions. Returns: result
prepare_reloadA
Check that the linked ExileAPI source plugin is ready for an in-game Build/Reload.
Inputs: no named parameters. Returns: result
read_core_snapshot_memberA
Read a bounded byte range from one exact, indexed regular-file path in an ExileAPI snapshot.
Inputs: path (required), snapshot_name (required), max_bytes. Returns: result
read_game_snapshotC
Read a manually captured, read-only ExileAPI game snapshot or one shortcut section.
Inputs: section, max_characters. Returns: result
read_game_snapshot_pathB
Read one exact, safe dot path from the latest bridge snapshot and remember it for this ExileAPI version.
Inputs: path (required), max_characters. Returns: result
read_last_build_errorsA
Read the newest bounded portion of ExileAPI's Errors.txt after an in-game build.
Inputs: max_lines. Returns: result
read_runtime_statusA
Read the read-only status file written by the enabled ExileAPI bridge after Build/Reload.
Inputs: no named parameters. Returns: result
refine_game_snapshot_captureB
Find node-limited paths in the latest bridge snapshot and prepare a deep, targeted follow-up capture.
Inputs: max_targets. Returns: result
save_game_snapshot_path_profileB
Save safe target paths from the latest snapshot as a reusable profile for the current ExileCore build.
Inputs: name (required), paths. Returns: result
scaffold_pluginA
Create a local Git repository and ExileAPI source symlink for a new source-only plugin.
Inputs: description (required), plugin_name (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Most tools target distinct resources and actions, but some pairs like read_game_snapshot vs read_game_snapshot_path or prepare_game_snapshot_capture vs prepare_game_snapshot_path_profile require careful reading of descriptions to avoid misselection. Overall, the boundaries are clear enough for an agent.
All tool names follow a verb_noun snake_case pattern, which is consistent in style. However, the verb set is varied (prepare, list, inspect, read, save, refine, find, discover, scaffold), and some verbs like 'prepare' and 'read' repeat across multiple tools, introducing minor ambiguity.
With 19 tools, the server is on the heavier side but still within a reasonable range for a complex domain like ExileAPI plugin development, which involves snapshots, builds, and profiles. The count is not excessive given the breadth of features.
The tool set covers core workflows: environment discovery, scaffolding, build/reload status, snapshot inspection (both game and core), path profiles, and example lookup. Minor gaps exist, such as no delete operation for saved path profiles, but the surface is largely complete for read-oriented development support.
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
ArcAgent MCP server for bounty discovery, workspace execution, and verified coding submissions.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA unified MCP server with composable tools for GitHub operations, file management, shell execution, kanban boards, Discord messaging, and package management. Features role-based security, HTTP/stdio transports, and a web-based development UI.GPL 3.0
- AlicenseAqualityCmaintenanceAn MCP server that empowers AI coding agents to work effectively with Minecraft mod development, providing static analysis of decompiled source code and runtime interaction with a running Minecraft instance.3192 npm18MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that helps AI agents inspect Minecraft project evidence (crash logs, mod files, datapacks) before writing development code.2-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes a verified manifest of a repository's development commands, allowing AI coding agents to instantly learn the correct dev loop without trial-and-error.5 npmMIT