Skip to main content
Glama
Abiotic Factor Mod Editor MCP server

Abiotic Factor Mod Editor MCP server

Abiotic Factor Mod Editor MCP server

Make Abiotic Factor mods by describing them.

Tell your AI assistant "make the Crafting Bench cost 1 duct tape", and it makes the change in the official Mod Editor, checks it, and starts the game inside the editor so you can try it. You don't need to know Unreal Engine.

Getting started

You'll need:

  • A Windows PC with the Abiotic Factor Mod Editor installed (it's free on the Epic Games Launcher)

  • An AI app that supports MCP, such as Claude Code, Claude Desktop, Codex or Cursor

1. Install it. Open PowerShell, paste this and press Enter:

irm https://raw.githubusercontent.com/JupiterianSoul/Abiotic-Factor-Mod-Editor-MCP-server/main/install.ps1 | iex

This also needs Python. If you don't have it, the installer will try to add it for you. If you use Claude Code, you're all set. For other apps, the installer prints what to paste into their settings.

2. Open the Mod Editor (close it first if it's already open), then open a mod or create one in the Mod Browser. Log in to mod.io when it asks, if you plan to upload later.

3. Start a new chat in your AI app and say what you want.

Related MCP server: mcreator-mcp

Things you can ask for

  • "Make the Crafting Bench cost 1 duct tape, then test it."

  • "Make the security pistol do double damage."

  • "Add a stronger version of the knife that I can craft."

  • "What does my mod change compared to the normal game?"

  • "Undo that."

It works best for changes to the game's data, like recipes, items, weapons and enemies. It can also build simple Blueprint logic. For a new look, you'll need to bring your own 3D models or textures.

Testing your mod

Say "test it". The AI saves your mod, checks it for problems, loads the game's map and starts playing inside the editor, usually in a minute or two. Then you just try your change. Press Esc when you're done.

This is a good test of whether your mod works, but it isn't quite the real game. To try it in the real game, upload it privately to mod.io and install it from the game's mod menu.

Uploading your mod

When you're happy with it, say "help me upload this". The AI checks your mod, makes a listing image if you need one, and tells you what to click. It never uploads anything by itself, and your mod stays private until you decide otherwise.

After you upload, mod.io packages your mod on its servers, which can take a while. If an upload fails, ask the AI why. The editor's error messages are often vague, but it can usually find the real reason.

Good to know

  • This is an early version. It has been tested in the editor with a recipe mod, but no mod made with it has been uploaded or played in the real game yet. You may run into bugs.

  • Your mods are backed up when you ask. Say "back up my mod" before big changes. Backups go in abf-mod-backups in your user folder.

  • It can't change the base game's files. Like any mod, your changes live in your own mod.

  • You still create new mods yourself. Making a new mod project in the Mod Browser takes a few clicks. The AI can tell you what to click.

  • Keep an eye on what it does. The AI can run code inside the editor, so read what it's about to do when your app asks for permission.

  • The installer adds a small startup file to Documents\UnrealEngine\Python. It only does something in the Mod Editor.

Removing it

Paste this into PowerShell, then delete the abf-mod-editor-mcp folder in your user folder:

python "$env:USERPROFILE\abf-mod-editor-mcp\install.py" --uninstall

Your mods aren't touched.

Credits

Built on abf-mod-editor-mcp by theelites11gamer. Thanks also to the Abiotic Factor modding community for their guides.

This is an unofficial fan project, not affiliated with Deep Field Games, Playstack or mod.io.

Want to see how it works or help out? See the technical details. MIT licensed, see LICENSE.

Available Tools

21 tools
check_blueprint_symbolA

Check a class or function against Deep Field's Blueprint filter.

Check before generating Blueprint logic and never use a blocked symbol. Example: class_path="/Script/Engine.GameplayStatics", function="GetPlayerController".

Inputs: class_path (required), function.

clone_rowC

Copy a vanilla row into a new row asset in the active mod, as a starting point.

Inputs: table (required), source_row (required), new_row_name (required), source_table (required), +2 more.

create_modC

Create a mod project from a template, if the editor exposes templates to scripting.

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

duplicate_assetB

Copy an asset into the active mod. The destination must be inside that mod.

Inputs: source (required), destination (required).

editor_statusA

Report whether the Mod Editor is connected, its version and the open mod.

Inputs: no named parameters.

get_logC

Tail the editor log, with auth codes and API keys removed.

Inputs: lines, contains.

list_assetsC

List assets under a content path, such as /Game/Blueprints/Items or /MyMod.

Inputs: path (required), limit, recursive.

list_datatablesB

List DataTable assets, optionally filtered by path substring.

Inputs: query.

list_modsA

List local mod projects (works without the editor open).

Inputs: no named parameters.

list_row_asset_typesA

List row asset classes a mod can create, such as RecipeModRowAsset.

Inputs: no named parameters.

list_templatesB

List mod templates the editor exposes to scripting.

Inputs: no named parameters.

open_mod_panelA

Open the editor's Mod Management Tool. It presses nothing and uploads nothing.

Inputs: no named parameters.

package_modA

Save and validate the active mod, open the upload panel, and explain the next step.

Packaging happens inside the editor's upload flow, so this stops before it. It never creates a mod.io page or uploads anything.

Inputs: no named parameters.

read_assetB

Read an asset's properties as JSON. DataTables return their rows.

Inputs: path (required).

read_datatableC

Read rows from a DataTable. Pass row names, or page with offset and limit.

Inputs: path (required), rows, limit, offset.

run_pythonA

Run Python inside the editor, with unreal imported, and return its output.

This is an escape hatch and is not limited to the active mod. Use it for inspection and for gaps in the other tools. Do not use it to bypass the write guards, delete assets, or upload to mod.io without the user asking.

Inputs: code (required).

save_allB

Save every changed asset in the active mod.

Inputs: no named parameters.

search_assetsC

Find assets under a path by package path substring and/or exact class name.

Inputs: path, limit, query, asset_class.

set_propertiesC

Set properties on an asset in the active mod. Call save_all afterwards.

Inputs: path (required), properties (required).

upsert_datatable_rowsA

Create or update rows in the active mod. Call save_all afterwards.

Mods add one asset per row, stored at //DataTables//<row_name>. Each entry is {"row_name": str, "override_existing_row": bool, "values": {...}}, with values in the snake_case form that read_asset returns.

Fields left out of a new row keep struct defaults, not vanilla values. To change part of a vanilla row, use clone_row with override_existing_row=True and the same row name, then set only what differs. When a row refers to another row in this mod, use <mod_prefix>_<row_name> (see editor_status).

Inputs: rows (required), table (required), row_asset_class (required).

validate_modB

Run the editor's asset validators over the active mod.

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially the write-path tools (upsert_datatable_rows, clone_row, duplicate_asset, set_properties). There is some overlap between list_datatables and list_assets/search_assets, and between read_asset and read_datatable, though descriptions mostly clarify the boundaries.

    Naming Consistency4/5

    The set predominantly follows a snake_case verb_noun convention (list_assets, read_asset, create_mod, validate_mod). Minor deviations like editor_status (noun phrase) and verb-only names save_all/package_mod are readable but slightly inconsistent.

    Tool Count3/5

    At 21 tools, the surface is on the heavy side for a mod editor, falling into the 16-25 borderline zone. Most tools appear purposeful, but some listing/reading variants could potentially be consolidated.

    Completeness3/5

    Core workflows are covered: listing, reading, writing datatable rows, cloning, duplicating, saving, validating, packaging, and a Python escape hatch. However, there are notable gaps around deletion/removal of rows or assets, and no explicit mod metadata editing beyond creation.

    Related MCP Connectors

    Related MCP Servers