ExileAPI Plugin Dev MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_environmentC | Report local ExileAPI references and the source-plugin link used by ExileAPI Build/Reload. |
| scaffold_pluginA | Create a local Git repository and ExileAPI source symlink for a new source-only plugin. |
| prepare_reloadA | Check that the linked ExileAPI source plugin is ready for an in-game Build/Reload. |
| read_last_build_errorsA | Read the newest bounded portion of ExileAPI's Errors.txt after an in-game build. |
| read_runtime_statusA | Read the read-only status file written by the enabled ExileAPI bridge after Build/Reload. |
| inspect_game_snapshotB | Return a bounded table of bridge snapshot paths, types, list sizes, and truncation markers. |
| read_game_snapshot_pathB | Read one exact, safe dot path from the latest bridge snapshot and remember it for this ExileAPI version. |
| list_known_game_snapshot_pathsB | List successful bridge snapshot paths remembered locally for the current ExileCore build. |
| read_game_snapshotC | Read a manually captured, read-only ExileAPI game snapshot or one shortcut section. |
| prepare_game_snapshot_captureC | Prepare a bounded bridge capture profile; the user must still press Capture snapshot in-game. |
| save_game_snapshot_path_profileB | Save safe target paths from the latest snapshot as a reusable profile for the current ExileCore build. |
| list_game_snapshot_path_profilesA | List reusable target-path profiles saved for the current ExileCore build. |
| prepare_game_snapshot_path_profileA | Prepare a deep targeted capture from a saved path profile, optionally waiting for simple bridge conditions. |
| refine_game_snapshot_captureB | Find node-limited paths in the latest bridge snapshot and prepare a deep, targeted follow-up capture. |
| find_plugin_examplesB | Find relevant local ExileAPI C# examples and return the exApiTools plugin catalogue link. |
| list_core_snapshotsA | List ExileAPI's .exapisnap files without reading their multi-gigabyte contents. |
| inspect_core_snapshotC | Build/read a header-only snapshot index and return a bounded table of matching archive paths. |
| find_core_snapshot_pathsA | Return only indexed snapshot paths matching all include terms and none of the excluded terms. |
| read_core_snapshot_memberA | Read a bounded byte range from one exact, indexed regular-file path in an ExileAPI snapshot. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.