Skip to main content
Glama

MB2-MCP

Turn your AI coding agent into a Mount & Blade II: Bannerlord modding partner.

English · 简体中文 · Tool reference

Node.js MCP Bannerlord Platform Tools License: MIT


Introduction

MB2-MCP is an MCP server that gives Claude Code, Codex, DeepSeek Harness and other MCP clients the view of a Bannerlord install that an experienced modder has, plus safe tools to change it. You ask in plain language; the agent searches, writes, patches and validates, then shows you what changed.

"Make a mod called RoyalArmory with a sword based on the imperial spatha, worth 5000 denars." "Raise one-handed skill of every Vlandian cavalry troop above level 26 by 20 — patch it, don't override." "Translate MyMod into Simplified Chinese." "In the open editor scene, put three barrels on the ground in a row next to the gate and take a screenshot."

How it works:

  • Files — module XML, scenes and prefabs are edited with an offset-preserving XML scanner (only the touched characters change), and every write is journaled with a backup.

  • Validation and XSLT run on the .NET Framework through Windows PowerShell: the same System.Xml classes the game uses.

  • Live editing goes through a small bridge module that the server compiles on your machine against your game's editor assemblies, with the C# compiler that ships with Windows. It runs only inside the Modding Kit, listens on 127.0.0.1 and requires a random token.

Requirements: Windows 10/11 · Node.js 18+ · Bannerlord (tested with 1.4.8; 1.2+ expected to work) · optional Mount & Blade II: Bannerlord – Modding Kit (Steam → Library → Tools) for the live editor.

Related MCP server: forge-x-reforger-mcp

What it can do

Know your install

  • Detects the game (Steam/Epic/GOG/Xbox) and indexes every module (official, Workshop and your own) in about a second.

  • Search objects by id, name (Chinese names too) or attributes, find reverse references, show load order and dependencies.

Edit game data safely

  • Create modules; write, clone and change items, troops, heroes, clans, kingdoms, settlements and cultures. Files are registered in SubModule.xml automatically; indentation, comments and encodings (UTF-8/UTF-16) are preserved.

  • Change vanilla or other mods without copying them, with XSLT patches (the mechanism the official naval DLC uses), previewed with the game's own XslCompiledTransform and XSD validation.

  • Validate like the game: XSD schemas, XSLT compilation, dependencies, DLLs, duplicate ids, broken references, unregistered files.

  • Localization: find untranslatable text, assign {=ids}, list untranslated strings, write Languages/<lang>/ files with placeholder checks.

Scenes and prefabs (files, no game needed)

  • List, filter and edit scene.xscene entities: add prefabs or meshes in rows, move/rotate (degrees)/scale, tags, script variables, scene levels, duplicate, delete; create scenes from templates; environment and atmosphere; the saved editor camera; save entities as prefabs.

  • Catch what crashes the editor on load: siege spawners with custom names, a camera saved looking straight down, GI flagged without bake data.

Assets

  • Copy FBX meshes and textures into AssetSources with checks (FBX version, texture size, naming), and search the resource tables of all .tpac packages (~90k names).

  • Check converted packages the way the editor loads them (sub-meshes without a material, names corrupted by the importer, collision shapes without their mesh) and refuse to launch the editor with packages that would freeze it.

Live scene editor (Modding Kit + bridge)

  • Launch the Modding Kit with your module and enter the scene editor; the startup prompts that block it (module-metadata warnings, the crash watchdog's collect necessary files?, Always Ignore?, the shader-cache notice) are answered for 10 minutes — always the choice that sends and changes nothing.

  • editor_status explains a stuck editor: message boxes (also those Windows shows for the game, and the editor's own Qt dialogs with their buttons), a frozen window, crash-watchdog dumps, engine warnings, which scene file is open and whether changes made through the server are unsaved.

  • In the open scene: list, select, spawn (rows, snap to ground), move, rotate, scale, rename, tag, show/hide, duplicate and delete entities; raycast and ground height; console commands with the engine log they produced; the editor's scene check; screenshots of the editor window (viewport and UI) that the agent can look at.

  • Answer dialogs with explicit buttons in any Windows language (button="No" presses 否(N)).

Play mode, walk tests and navigation (new in 0.3.0, experimental: built on the game's own APIs, not yet tested in a running editor)

  • editor_play starts and stops the editor's play mode on a saved scene; live scene edits are refused while it runs.

  • mission action=walk lets the player walk a route with the game's AI movement on the navigation mesh (never teleported) and reports each leg as reached, stuck or timed out, with a JSON position trace; objects / use / dismount / teleport (labelled as positioning).

  • navmesh_query asks the engine's path finder: the face under a point, whether two points connect and how long the path is.

  • editor_camera reads and moves the viewport camera; editor_command action=perf samples frame times; action=fill_dialog fills an editor dialog's fields, check boxes and list selections without pressing anything.

Safe by default

  • Official and Workshop modules are never written. Every file change has a backup: edit_history, undo_edit.

  • Launching and quitting the game always need an explicit call (quit also confirm=true).

Privacy

  • No built-in telemetry. The editor bridge uses 127.0.0.1. read_logs restricts reads to game log folders, but module path checks are not a sandbox: junctions and symbolic links can lead outside a module. Only inspect modules and linked folders you trust.

  • Tool output shows your home folder as %USERPROFILE% and your user and computer names as <user> / <computer>; paths sent back with %USERPROFILE% still work (MB2_REDACT=0 turns this off). Everything else the agent reads — mod files, game logs, screenshots — reaches the model provider of your MCP client, like any tool output. Debug logs and image contents are not fully redacted; review them before sharing.

  • Screenshots without path=…png use temporary files that are removed after a successful capture. Failures can leave raw capture files behind. Screen-copy masking is best-effort and can miss other programs' frozen windows; keep private windows out of view. editor_command action=cleanup deletes screenshots, walk traces and logs from Documents\Mount and Blade II Bannerlord\MB2MCP; forget_history deletes edit backups. These cleanup actions can currently delete server-owned records even in read-only mode.

All 43 tools with their parameters: docs/TOOLS.md.

What it can't do

  • Open another scene, reload it, or save it in the editor.

    • Why: the engine offers no call for it — neither the editor's managed API (MBEditor) nor the native console's scene., editor. and resource. commands open or save a scene. The editor's toolbar buttons expose no names to accessibility tools, so the server would have to click by screen position, which is too risky for your scene. Open and save in the editor (Ctrl+S); editor_status shows the file and whether changes made through the server are unsaved.

  • Convert new assets the first time (FBX/textures → .tpac).

    • Why: only the Resource Browser's Import new asset (with its FBX Import Settings) does it; no engine call or console command converts new sources, and reimport_assets only re-converts sources imported before. asset_import prepares and checks the files, asset_status verifies the result.

  • Edit the navigation mesh.

    • Why: the engine's navigation calls are meant for missions (switching face groups on and off at runtime) and cannot add, move or save faces; saving goes through the editor's NavigationMeshInspector, and navmesh.bin is an undocumented compressed format. navmesh_query can inspect it.

  • Paint terrain or flora, or edit materials, shaders and textures.

    • Why: these are native editor tools with no engine call that modules could use. Static flora and other props can still be placed as entities.

  • Change script variables of a live entity.

    • Why: the engine exposes no supported call for the editor's script inspector that MB2-MCP could rely on. File mode writes them into scene.xscene; reopen the scene to see them.

  • Turn the live editor camera or read its field of view.

    • Why: the engine only reports the last rendered camera frame and can move the camera's position. scene_edit action=focus zooms toward an entity, and scene_settings editor_camera sets the camera saved with the scene.

  • Run a light bake as a tracked job (progress, cancel, result).

    • Why: baking runs through console commands that only answer "Done". The tools return what the engine logged meanwhile and explain known messages such as No border probes can be found; a "Done" is not proof that GI data exists.

  • Play unsaved changes.

    • Why: the test mission editor_play starts loads the scene by name from its saved file, so it refuses while changes made through the server are newer than the file.

  • Undo live editor changes.

    • Why: they are made through engine calls, outside the editor's undo history, and undo_edit covers files only. Save or discard them in the editor.

  • Modify official or Workshop modules.

    • Why: by design, to protect your install. Patch them with XSLT from your own module instead.

  • Choose a button for you in editor dialogs or after a crash.

    • Why: editor dialogs can save or discard scenes, and crash prompts end a process; only startup prompts with a harmless answer are automatic. Everything else needs an explicit button.

  • Test NPC behaviour, battles or sieges.

    • Why: the tools drive one player agent (walk, use, position). AI and combat need a real game test.

  • Run XSD/XSLT or the live editor outside Windows.

    • Why: they need the .NET Framework and the Windows-only Modding Kit; browsing and file editing work everywhere.

How to configure

Build once and check your setup:

git clone <this repository> MB2-MCP
cd MB2-MCP
npm install
npm run build
node dist/index.js doctor     # game, index, schemas, .NET, Modding Kit
node dist/index.js config     # prints the blocks below with your real paths

The examples use the server name bannerlord; tools then appear as mcp__bannerlord__<tool>. Replace the paths with yours (node dist/index.js config claude|codex|dsh prints them ready to paste).

Claude Code

claude mcp add bannerlord --scope user -e MB2_GAME_DIR="D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord" -- "C:\Program Files\nodejs\node.exe" D:\MB2-MCP\dist\index.js

Or a project-scoped .mcp.json in your mod folder (example). Check with claude mcp list.

Codex

Codex CLI, the desktop app and the IDE extension share ~/.codex/config.toml (example):

[mcp_servers.bannerlord]
command = 'C:\Program Files\nodejs\node.exe'
args = ['D:\MB2-MCP\dist\index.js']
startup_timeout_sec = 30
tool_timeout_sec = 300
default_tools_approval_mode = "writes"   # read-only tools are annotated, so only edits ask

[mcp_servers.bannerlord.env]
MB2_GAME_DIR = 'D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord'

Or: codex mcp add bannerlord --env MB2_GAME_DIR="…" -- "C:\Program Files\nodejs\node.exe" D:\MB2-MCP\dist\index.js.

DeepSeek Harness

Merge into ~/.dsh/cordis.patch.yml (all profiles) or ~/.dsh/profiles/<profile>/cordis.patch.yml (example); dsh reloads it automatically:

- insert:
    - id: mcp-bannerlord
      name: '@deepseek-ai/dsh-mcp-client'
      config:
        serverName: bannerlord
        transport: stdio
        command: 'C:\Program Files\nodejs\node.exe'
        args: ['D:\MB2-MCP\dist\index.js']
        env:
          MB2_GAME_DIR: 'D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord'
        toolCallTimeoutMs: 300000

Other MCP clients (Cursor, Cline, Windsurf, Cherry Studio, …): node dist/index.js config json prints a generic mcpServers block.

Options (environment variables)

Variable

Meaning

MB2_GAME_DIR

Game folder (auto-detected otherwise)

MB2_MODULE_DIRS

Extra folders with your own modules (writable), ;-separated — link them into <game>/Modules for the game to load them

MB2_TOOLSETS

Tool groups to expose: core,edit,l10n,scene,assets,editor,logs (default all; fewer tools for small context windows)

MB2_WORKSHOP=0

Do not index Steam Workshop modules

MB2_READONLY=1

Disable module edits; cleanup actions can still delete server-owned records

MB2_DATA_DIR

History and backups (default %LOCALAPPDATA%\mb2-mcp)

MB2_MAX_OUTPUT

Max characters per tool result (default 40000)

MB2_POWERSHELL

Path to Windows PowerShell for XSD/XSLT

MB2_DEBUG=1

Log tool timings to stderr

MB2_REDACT=0

Show the real home folder, user and computer names in tool output (default: masked)

Before publishing a fork, run npm run privacy: it checks every file git and npm would publish for your home folder, user and computer names, e-mail addresses, keys and tokens, and the private terms you list in %USERPROFILE%\.mb2-mcp\privacy-terms.txt (kept outside the repository). Publish with git or npm pack, not by zipping the folder. Also run npm pack --dry-run --ignore-scripts separately and review its file list: the privacy checker can currently omit npm package files if that command fails. A clean source scan does not remove the runtime limitations described above.

Live editor (optional)

  1. Install the Modding Kit (Steam → Library → Tools).

  2. Ask the agent to run editor_bridge_install while the game is closed. Run it again after game updates, and when editor_status says the bridge is outdated after an MB2-MCP update; restart your MCP client so it loads the new server.

  3. editor_launch modules=["MyMod"] starts the editor; poll editor_status until it reports edit mode ON (1–5 minutes).

Long-running tools (launching, editor_play start, mission walk) wait up to two minutes by default. Keep the tool timeout at 300 s as in the examples, or pass wait_seconds=0 and poll.


License

Released under the MIT License. See third-party notices for upstream acknowledgements and licenses.

Not affiliated with or endorsed by TaleWorlds Entertainment. Thanks to TaleWorlds for Bannerlord and its modding tools, and to BannerlordSceneToolkit for showing which editor APIs exist.

Available Tools

43 tools
asset_importImport asset sourcesA

Copies FBX meshes and textures (png/tga/dds/tif/psd/bmp/jpg) into /AssetSources (the folder the Modding Kit editor imports from), checks them (FBX version, texture size, naming) and creates Assets/. Copying is not converting: new files become Assets/*.tpac only through the editor's Resource Browser → Import new asset; the result says what to do next, in which order (materials before FBX, with an editor restart in between) and whether the running editor has the module loaded. Folders are expanded (top level).

Inputs: files (required), module (required), reimport, overwrite, +2 more.

asset_statusAsset import statusA
Read-only

Compares a module's AssetSources with the editor's imported packages (Assets/*.tpac): imported, pending (copied but never converted), stale (source changed after import) and orphaned packages, plus the meshes/materials/textures/physics shapes each package contains. Checks the packages like the editor will when loading them: sub-meshes without a material or with an unknown one, resource names corrupted with control characters, physics shapes without their mesh.

Inputs: module (required), details.

clone_objectCopy an object into your moduleA
Destructive

Copies an existing object (usually vanilla) into a writable module under a new id, optionally changing attributes — the fastest way to make a new weapon/troop/hero/culture based on an existing one. With new_id omitted the copy keeps the id and fully overrides the original. A plain 'name' gets a fresh {=id}.

Inputs: module (required), source (required), set, file, +3 more.

create_moduleCreate a new mod moduleA

Scaffolds a new module folder with SubModule.xml (dependencies on the installed official modules) and ModuleData/. Optional C# project (Source/.csproj + SubModule.cs that builds into bin/Win64_Shipping_Client). Default location: /Modules.

Inputs: module_id (required), name, version, category, +3 more.

delete_objectDelete an object from your moduleA
Destructive

Removes an object definition from a writable module's XML (all definitions of that id in the module).

Inputs: ref (required), module (required).

describe_schemaDescribe XML schemaA
Read-only

Explains which elements/attributes are valid, from the game's own XSD files (XmlSchemas folder) plus real values observed in official data. Use before writing XML. No args: list XmlName ids. xml_id only: root and object elements. element (+path for nested ones, e.g. element=Weapon path=Item/ItemComponent/Weapon): attributes with types/enums and children.

Inputs: path, xml_id, element, observed.

edit_historyList edits made by this serverB
Read-only

Lists recent changes made through this MCP server (every write is journaled with a backup), newest first.

Inputs: limit, module.

editor_bridge_installInstall the editor bridgeA
Destructive

Compiles the MB2-MCP editor bridge (a small C# module) against your installed game with the Windows .NET compiler and installs it as Modules/MB2MCP.EditorBridge. Inside the Modding Kit editor it lets the live tools (scene_* live=true, editor_command) inspect and edit the open scene. Re-run after game updates.

Inputs: force.

editor_cameraRead or move the editor cameraA
Destructive

The live viewport camera (needs the bridge): get (position, view direction, pitch and heading of the last rendered frame — also in play mode), set (move the editor camera to a position, keeping its direction), move (by a delta). The engine offers no call to turn the live editor camera: scene_edit action=focus zooms toward an entity keeping the direction, and scene_settings editor_camera sets the saved camera used when the scene is opened.

Inputs: delta, action, position.

editor_commandRun an editor actionA

Live actions in the running Modding Kit editor (needs the bridge): console (run a developer console command), list_commands (console commands by prefix; entries ending in '.' are groups such as 'scene.', 'resource.', 'prefab.' — list them with that prefix), check_scene (editor's scene problem check), reimport_assets (re-converts changed sources of earlier imports — new files need the Resource Browser's Import new asset), raycast (from/to or a position straight down → hit point), ground_height, warning (show a message in the editor), enter_editor (from the main menu), ping, quit (confirm=true; closes the game without saving). Also without the bridge: screenshot (captures the game window and returns the image; when the game is frozen or has no window yet, the message box blocking it), dialogs (the game's message boxes such as 'RGL WARNING', prompts Windows shows for it, the scene editor's modal Qt dialogs such as 'Do you want to save the scene?' with their texts, fields and buttons, and its other open windows), dismiss_dialogs (press OK, or button, on them; editor dialogs and file dialogs only with a named button) and fill_dialog (type into an editor dialog's input fields, set its check boxes and select a list/tree item — by label or #n — then read everything back; it never presses a button). With the bridge also: perf (frame times over seconds: average, percentiles, fps, plus the engine's main/renderer fps). cleanup deletes the screenshots, walk traces and dialog/bridge logs this server left in the bridge folder.

Inputs: action (required), to, from, path, +13 more.

editor_launchStart the Modding Kit editorA

Starts the Modding Kit build (bin/Win64_Shipping_wEditor/Bannerlord.exe) with the official singleplayer modules, the given modules and the editor bridge, and (open_editor=true) enters the scene editor automatically (with an empty scene; open yours in the editor). Loading usually takes 1–5 minutes; poll editor_status until it reports 'edit mode ON'. While it loads, 'RGL WARNING' message boxes about other mods' SubModule.xml entries (common with Workshop mods made for launcher extensions) are answered automatically with OK, together with the two prompts that follow each of them (the crash watchdog's 'collect necessary files?' → No, nothing is collected or uploaded; 'Always Ignore?' → Cancel, no setting changes) and the shader-cache notices ('Mod change detected').

Inputs: force, modules, open_editor, decline_safe_mode, +2 more.

editor_playPlay the scene from the editorA
Destructive

Play mode of the Modding Kit editor (needs the bridge). start plays the open scene with the editor's test mission — the same managed entry the editor's Play button reaches; the player spawns at spawnpoint_player_test or spawnpoint_player — and waits until the player is there. It loads the scene's SAVED file: save first (start refuses when changes made through this server are newer than the file). stop returns to the editor exactly like the leave key does in play mode, and waits for it. status / missions report. While playing, live scene_* commands are refused (they act on the edited scene); use mission, navmesh_query and editor_command screenshot.

Inputs: scene, action, levels, mission, +2 more.

editor_statusModding Kit editor statusA
Read-only

Shows whether the Modding Kit (scene editor) is installed, whether the MB2-MCP editor bridge module is installed and current, which Bannerlord processes run, message boxes that block the game (e.g. 'RGL WARNING', 'Safe Mode') and — if the bridge is connected — the editor state, open scene, entity and selection counts.

Inputs: no named parameters.

edit_submoduleEdit SubModule.xmlA
Destructive

Edits a writable module's SubModule.xml in place (formatting preserved): name/version/url/category, add or remove dependencies, register or unregister ModuleData XML files, add or remove DLL SubModule entries.

Inputs: module (required), url, name, add_dll, +7 more.

find_referencesFind referencesA
Read-only

Lists objects that reference a given object (e.g. which troops carry Item.x, which troops upgrade into NPCCharacter.y, which settlements belong to Faction.z). Accepts 'Prefix.id' or a bare id.

Inputs: ref (required), limit, module.

forget_historyDelete the edit historyA
Destructive

Deletes this server's edit journal and the file backups it keeps for undo_edit (in MB2_DATA_DIR, default %LOCALAPPDATA%\mb2-mcp\history): all of it, or only edits older than older_than_days. Forgotten edits can no longer be undone. Needs confirm=true. (Screenshots and traces in the bridge folder: editor_command action=cleanup.)

Inputs: confirm, older_than_days.

game_infoBannerlord environment overviewA
Read-only

Start here. Shows the detected Mount & Blade II: Bannerlord install, game version, module folders, which modules are writable, the launcher's enabled mods, index/validation status and the recommended editing workflow.

Inputs: no named parameters.

get_objectRead an object's XMLA
Read-only

Returns the XML of a game object, e.g. ref='Item.empire_sword_1_t2', 'NPCCharacter.imperial_recruit', 'Culture.empire' or a bare id. Shows which module's definition wins (load order), other definitions, XSLT patches that touch it and the absolute file path.

Inputs: ref (required), lang, module, all_definitions.

l10n_scanScan localizable stringsA
Destructive

Scans a module's XML data, GUI prefabs and C# code (Source/ or code_dir) for {=id}Text strings. Reports texts without ids, empty ids, ids reused with different texts, ids colliding with other modules, and translation coverage per language. fix_missing_ids / fix_conflicts rewrite the module's XML with fresh unique ids.

Inputs: module (required), code_dir, include_code, fix_conflicts, +1 more.

l10n_setWrite translationsA
Destructive

Writes translations for one language into the module's ModuleData/Languages// files (creates language_data.xml and _strings.xml when missing; existing ids are updated in place). Warns when {PLACEHOLDERS} differ from the source text.

Inputs: module (required), language (required), file, remove, +3 more.

l10n_statusList strings to translateA
Read-only

Lists a module's strings for one language as JSON lines {"id","text"[,"tr"]}: untranslated (default), translated, all, or stale (translations whose id no longer exists). Strings already translated by the game/other modules (same id and text) are skipped. Translate them and send the result to l10n_set.

Inputs: module (required), language (required), show, limit, +3 more.

list_modulesList modulesA
Read-only

Lists installed modules (official, Steam Workshop, your own) with id, version, flags (official / writable / workshop / enabled in launcher) and folder. filter: all | official | mods | writable | workshop | enabled.

Inputs: query, filter.

list_typesList data typesA
Read-only

Summarizes game data by XmlName id (Items, NPCCharacters, SPCultures, Factions, Kingdoms, Settlements, partyTemplates, …) with the object tags and counts per module. Use it to learn what exists before searching.

Inputs: module.

missionAct in the running missionA
Destructive

In play mode (editor_play) or another running mission (needs the bridge): status (player position, direction, mission state); objects (usable objects near the player — doors, chairs, passages, ladders… — and whether the player can use them); dismount (the editor's test mission spawns a horseman); walk (the player walks a route with the game's own AI movement on the navigation mesh, never teleported, and each leg reports reached / stuck / timed out with the closest approach; the position trace is saved as JSON — evidence that a route can be walked, or where it is blocked); walk_status / walk_stop; teleport (positioning before a test, reported as such — not evidence of a walkable route); use (use an object within reach, the same callback as the interaction key); stop_using.

Inputs: tag, speed, action, entity, +12 more.

module_infoModule detailsA
Read-only

Details of one module: SubModule.xml fields, dependencies (installed versions), DLL entries, every registration with its resolved files and object counts, XSLT patches, unregistered files and language files.

Inputs: module (required).

prefab_createCreate a prefabA
Destructive

Saves a prefab into /Prefabs/_prefabs.xml from a scene entity (from_scene + entity; its position is reset to the origin) or from <game_entity> XML. The editor loads module prefabs at startup (restart it to see new ones).

Inputs: name (required), module (required), xml, entity, +3 more.

read_logsRead game logsA
Read-only

Reads Bannerlord's logs to debug a mod: rgl_log_*.txt (main log), rgl_log_errors_*.txt, launcher and crash files under ProgramData and Documents. action=list shows recent files; action=read (default) shows the tail of the latest log or matches of grep / errors_only.

Inputs: file, grep, tail, action, +2 more.

scene_createCreate a sceneA

Creates SceneObj// in a writable module: a copy of an existing scene (template=…, any module; terrain/navmesh files are copied, name and unique token renewed) or a minimal empty scene like the editor's New Scene (envmap probe + ground plane, terrain off).

Inputs: name (required), module (required), template.

scene_editEdit scene entitiesA
Destructive

Adds, updates, deletes or duplicates entities. File mode edits scene.xscene of a writable module (formatting preserved, undoable). live=true edits the scene open in the Modding Kit editor through the bridge (then save with Ctrl+S in the editor); live also supports select, focus and snap_to_ground. add: place a prefab (prefab=…) or a mesh (mesh=…, physics=bo_…) or raw <game_entity> XML, count+offset make rows. update: position/move_by, rotation/rotate_by (degrees unless rotation_unit=rad), scale, name (exact for every target unless number_names), add_tags/remove_tags, attributes, script+variables, levels (file mode). Live targets: #handles from scene_entities live (valid until the scene is reopened) or names (child entities included). Siege spawner names are protected: the editor derives their prefab from the name.

Inputs: action (required), xml, live, mesh, +26 more.

scene_entitiesList or inspect scene entitiesA
Read-only

Lists entities of a scene file with handles ([12], [12/0] for children), name, prefab, mesh, position, rotation (degrees), scale, tags and scripts; filters by name/prefab/tag/script/mesh or distance. entity=<handle|name> returns the entity's XML. live=true lists the scene open in the Modding Kit editor (#handles are session ids for scene_edit live=true).

Inputs: tag, live, mesh, name, +11 more.

scene_infoScene overview and checksA
Read-only

Overview of a scene file: header, environment/atmosphere settings, terrain, entity/prefab/script/tag statistics, spawn points, bounding box, where the game references it, and checks (unknown prefabs/meshes/physics shapes, XML errors). live=true reports the scene currently open in the Modding Kit editor instead (needs the editor bridge).

Inputs: live, check, scene, module.

scene_listList scenesA
Read-only

Lists scenes (SceneObj//scene.xscene) of all or selected modules with size, date and whether terrain/navmesh data exists.

Inputs: limit, query, module.

scene_settingsScene environment & atmosphereA
Destructive

Reads or changes a scene's <environment_properties> (e.g. atmosphere_name, is_indoors, water_level, physics_world_min, gi_data_exists), its atmosphere.xml values (time_of_day, color_grade_name, season, fog_density, sun_altitude, …), its level definitions (base, siege, civilian… — entities join them with scene_edit levels) and the editor camera saved in <editor_data>. Without changes it lists the current values.

Inputs: scene (required), module, add_levels, atmosphere, +4 more.

search_objectsSearch game objectsA
Read-only

Searches every module's XML objects (items, troops, heroes, clans, kingdoms, settlements, cultures, crafting pieces, party templates, strings, …) by id / name and attribute filters. Chinese queries also match the 简体中文 names. Returns 'Tag.id "Name" — module file:line | key attributes'.

Inputs: lang, type, limit, query, +3 more.

set_attributesChange attributes of your objectA
Destructive

Changes attributes of an object that lives in a writable module, editing the file in place. Use path to reach nested elements (mini XPath): ItemComponent/Weapon, skills/skill[@id='OneHanded'], Equipments/EquipmentRoster[1]/equipment[@slot='Item0']. For objects owned by other modules use xslt_patch.

Inputs: ref (required), module (required), all, set, +3 more.

undo_editUndo an editA
Destructive

Reverts one change made through this server (default: the most recent not yet undone, optionally of one module), restoring backed-up files and deleting files it created. Refuses if the files changed afterwards unless force=true.

Inputs: seq, force, module.

validate_moduleValidate a moduleA
Read-only

Checks a module like the game would: SubModule.xml (ids, versions, dependencies, DLLs), every registered XML (exists, well-formed, game XSD), XSLT compiles, duplicate ids, unresolved references (Item.x, NPCCharacter.x …) against its dependencies, unregistered files, and localization (missing/conflicting {=ids}, translation coverage).

Inputs: module (required), xsd, l10n, refs.

write_objectCreate or replace objects (XML)A
Destructive

Writes one or more objects (e.g. , , , , , , , ) into a writable module. Replaces an object with the same tag+id in that module, otherwise appends it to the module's file for that data type (creating ModuleData/_.xml and registering it in SubModule.xml). Runs the game's XSD check afterwards.

Inputs: xml (required), module (required), file, mode, +2 more.

xslt_patchPatch another module's object (XSLT)A
Destructive

Changes an object owned by vanilla or another mod without copying it, by adding a rule to your module's XSLT (ModuleData/XSLT/_.xslt, registered automatically — the same mechanism the official DLC uses). One call per target node; repeated calls merge. Operations: set attributes, remove attributes, remove the node, replace it, append child XML, or clear the rule. Shows a before/after diff computed with the game's XSLT engine.

Inputs: module (required), target (required), set, path, +8 more.

xslt_previewPreview XSLT patchesA
Read-only

Runs the game's merge + XSLT pipeline (System.Xml XslCompiledTransform, like the game) for a module and shows before/after diffs of every object its XSLT rules target (or only targets). Also reveals XSLT errors that would break loading.

Inputs: module (required), xml_id, targets, game_type.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 43 tools

    Disambiguation4/5

    Tools generally target distinct resources and actions (modules, XML objects, scenes, assets, editor, history), and the descriptions clarify boundaries. However, with 43 tools there is some potential overlap between editor_command, editor_play, mission, and navmesh_query, and between scene_info, scene_entities, and scene_settings, which could cause occasional misselection.

    Naming Consistency4/5

    All names use snake_case, with domain prefixes (scene_, prefab_, asset_, editor_, l10n_) for related groups. The pattern is not strictly verb_noun throughout (e.g., module_info vs list_modules), but it is consistent and readable.

    Tool Count2/5

    43 tools is well above the 25-tool threshold for 'too many', even for a complex domain. While many tools earn their place, the set is heavy and could be consolidated.

    Completeness5/5

    The surface covers the full modding lifecycle: discovery, module/XML editing, XSLT patching, localization, scene/prefab editing, asset import, editor integration, play-testing, and history/undo. No obvious critical gaps for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search, browse, and manage mods across Nexus Mods, mod.io, Thunderstore, and Modrinth, as well as perform local diagnostics like detecting games and parsing crash logs.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to develop Banner of the Maid mods by reading and modifying game data (characters, items, weapons, skills, dialogue, saves, portraits) and to perform live in-game verification via launching the game, taking screenshots, and clicking by coordinates.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 10 tools that let AI agents search Nexus Mods, inspect locally installed game modules, populate and fix translation flags, generate and translate templates with Microsoft/Google/DeepLX engines, and build external translation modules. Two of the tools write to disk, rewriting ModuleData XML files and creating sibling translation directories under the game's Modules folder.
      103 npm
      2
      MIT