Skip to main content
Glama
ExileAPI Plugin Dev MCP

ExileAPI Plugin Dev MCP

by YunaAUbot

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 into Plugins/Source/<PluginName>.

  • Prepare the linked source tree for ExileAPI's in-game Build/Reload action.

  • Read the resulting bounded Errors.txt output.

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-dev

Controller-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.csproj

A 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-runtime

The 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:

  1. begin_game_struct_scan(goal, roots) prepares one shallow Discovery capture for one to three plausible DevTree roots.

  2. Let the bridge execute the request, then use inspect_game_snapshot and read_game_snapshot_path to examine only relevant paths.

  3. continue_game_struct_scan(goal) follows at most three depth_limit/node_limit branches with another shallow capture.

  4. Repeat until the exact property is evidenced. Only then use a deep Targeted capture.

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 tools
discover_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

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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
    • A
      license
      A
      quality
      C
      maintenance
      An 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.
      31
      92 npm
      18
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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 npm
      MIT