nightbreak-forge

endpoint

https://forge.nightbreak.io/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is nightbreak-forge live?

Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.

Is nightbreak-forge free to use?

Yes — the hub reached it with no key and no payment.

What tools does nightbreak-forge have?

10 tools: search_plugin_source, fetch_plugin_source_file, validate_lua_power_draft, search_wiki, fetch_wiki_page, get_config_schema, validate_config_files, list_config_types, ….

Is nightbreak-forge safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_config_types open 57m ago

  The config file types Forge knows for the released plugins, with each type's plugin, label, server path, format and wiki page. Pass a type to get_config_schema or as the path when validating.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "plugin": {
        "type": "string",
        "description": "Optional plugin id to filter by, such as \"elitemobs\", \"betterstructures\" or \"fmm\"."
      }
    }
  }

  arguments 9 lines copy
• get_authoring_notes open 57m ago

  Where each config type's files go and the plugin rules Forge's own assistant follows: per-type notes, the newer plugins' knowledge, boss movement and combat AI, and the Lua hook quick reference. Read it once before writing files.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_local_lua_reference open 57m ago

  Read the current Nightbreak Forge local Lua validator/editor reference. Use this to see which hooks, fields, methods, exact values, and handle helpers the editor currently knows about. **Pass `script_type` matching the file you are working on:** `"lua-power"` (default, EliteMobs boss powers — includes context handles, `em`, and exact values), `"fmm-script"` (FMM props), or `"npc-script"` (EliteMobs NPC scripts in `npc_scripts/`), or `"mind-behavior"` (EliteMobs Mind AI programs in `behaviors/`, selected by a boss's `behavior` field), `"fmm-pet-behavior"` (FreeMinecraftModels pet behavior modules in `pet_behaviors/`, id `fmm:pet/<file name>`; loaded from FMM 2.13.0), or `"em-enchantment-script"` / `"fmm-enchantment-script"` (the Lua effect of an EliteMobs or FreeMinecraftModels enchantment in `enchantments/`). Each returns that script type's own hooks and `context.*` namespaces — the boss reference does NOT contain NPC, FMM, Mind or enchantment APIs, so query the matching type.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "properties": {
      "scope": {
        "type": "string",
        "description": "Optional scope. For lua-power: \"hooks\", \"context\", \"boss\", \"player\", \"event\", \"script\", \"handles\", \"em\", or \"values\". For fmm-script/npc-script: \"hooks\", \"context\", or a context namespace name (e.g. \"npc\", \"player\", \"prop\", \"projectile\")."
      },
      "script_type": {
        "enum": [
          "lua-power",
          "npc-script",
          "mind-behavior",
          "em-enchantment-script",
          "fmm-script",
          "fmm-enchantment-script",
          "fmm-pet-behavior"
        ],
        "type": "string",
        "description": "Which script type's reference to return. Defaults to \"lua-power\"."
      }
    }
  }

  arguments 22 lines copy
• search_plugin_source unknown never probed

  Search the EliteMobs, MagmaCore, BetterStructures, FreeMinecraftModels, CannonRTP and ResurrectionChest source code for a query. By default searches every mirrored repo by file content (grep). MagmaCore contains shared core functionality (Lua engine, base entity tables, scripting helpers) used by every plugin — always check it for hooks, helpers, or context methods that feel like they should be common across plugins. FreeMinecraftModels (freeminecraftmodels) has its own LuaItemTable / LuaPropTable and prop-specific hooks. Use this BEFORE answering plugin-specific questions or generating Lua/YAML files.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "mode": {
        "enum": [
          "content",
          "path"
        ],
        "type": "string",
        "description": "\"content\" (default) greps file contents; \"path\" matches file paths."
      },
      "query": {
        "type": "string",
        "description": "Text or regex to grep for. Symbol names, hook names, error messages."
      },
      "repos": {
        "type": "array",
        "items": {
          "enum": [
            "elitemobs",
            "magmacore",
            "betterstructures",
            "freeminecraftmodels",
            "cannonrtp",
            "resurrectionchest"
          ],
          "type": "string"
        },
        "description": "Optional. Defaults to every mirrored repo."
      },
      "max_results": {
        "type": "number",
        "description": "Default 20."
      },
      "path_prefix": {
        "type": "string",
        "description": "Optional. Restrict to a subdirectory like \"src/main/java/\"."
      }
    }
  }

  arguments 43 lines copy
• fetch_plugin_source_file unknown never probed

  Fetch a file from a mirrored plugin source repo. Optional line slicing for large files.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132

  {
    "type": "object",
    "required": [
      "repo",
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "description": "Repo-relative path, e.g. \"src/main/java/com/magmaguy/elitemobs/powers/lua/LuaPowerRuntime.java\"."
      },
      "repo": {
        "enum": [
          "elitemobs",
          "magmacore",
          "betterstructures",
          "freeminecraftmodels",
          "cannonrtp",
          "resurrectionchest"
        ],
        "type": "string"
      },
      "line_end": {
        "type": "number",
        "description": "Optional. Read up to and including this line."
      },
      "line_start": {
        "type": "number",
        "description": "Optional. Read from this line (1-indexed)."
      }
    }
  }

  arguments 32 lines copy
• validate_lua_power_draft unknown never probed

  Validate a draft Lua script against the local Nightbreak Forge Lua validator. Use this before finalizing generated Lua files to catch unknown helpers, invalid fields, or malformed file structure. **IMPORTANT: pass `script_type` matching the file you are generating.** Use `"lua-power"` (default) for EliteMobs custom-boss Lua powers (files in `powers/`), `"fmm-script"` for FreeMinecraftModels prop scripts (files in `scripts/`), `"npc-script"` for EliteMobs NPC scripts (files in `npc_scripts/`), `"mind-behavior"` for Mind programs and modules (files in `behaviors/`), `"fmm-pet-behavior"` (FreeMinecraftModels pet behavior modules in `pet_behaviors/`, id `fmm:pet/<file name>`; loaded from FMM 2.13.0), or `"em-enchantment-script"` / `"fmm-enchantment-script"` for EliteMobs or FreeMinecraftModels enchantment scripts (files in `enchantments/`). They have different valid hook names and context namespaces — passing the wrong type produces false-positive errors (e.g. `on_right_click` is valid for `fmm-script`, `on_npc_interact` for `npc-script`, but both are rejected for `lua-power`).

  mcp-tool

  1234567891011121314151617181920212223242526272829

  {
    "type": "object",
    "required": [
      "content"
    ],
    "properties": {
      "path": {
        "type": "string",
        "description": "Optional path such as \"powers/example.lua\" or \"scripts/fireball_wand.lua\" for reporting context."
      },
      "content": {
        "type": "string",
        "description": "Full Lua script file content to validate."
      },
      "script_type": {
        "enum": [
          "lua-power",
          "npc-script",
          "mind-behavior",
          "em-enchantment-script",
          "fmm-script",
          "fmm-enchantment-script",
          "fmm-pet-behavior"
        ],
        "type": "string",
        "description": "Which validator ruleset to apply. `\"lua-power\"` for EliteMobs boss powers, `\"fmm-script\"` for FMM prop scripts, `\"npc-script\"` for EliteMobs NPC scripts, `\"mind-behavior\"` for behaviors/ programs and modules, `\"fmm-pet-behavior\"` (FreeMinecraftModels pet behavior modules in `pet_behaviors/`, id `fmm:pet/<file name>`; loaded from FMM 2.13.0). Defaults to `\"lua-power\"`."
      }
    }
  }

  arguments 29 lines copy
• search_wiki unknown never probed

  Search the Nightbreak wiki for relevant pages and snippets. Matching is by word and case-insensitive, ranked by title, page name and body. Each result has a `page` value to pass to fetch_wiki_page. Use for high-level docs, examples, and tutorials — not for symbol verification (use search_plugin_source for that).

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Keywords to search for, such as \"lua power files\", \"creating bosses\", or \"elitescript bridge\"."
      },
      "max_results": {
        "type": "number",
        "description": "Maximum number of results to return. Defaults to 10."
      }
    }
  }

  arguments 16 lines copy
• fetch_wiki_page unknown never probed

  Fetch and extract readable content from a specific Nightbreak wiki page such as "EliteMobs/lua_getting_started". Page names change as the wiki grows: take them from search_wiki results. A missing page returns `suggestions` with the closest existing pages.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "description": "Wiki page path relative to the site root, for example \"EliteMobs/lua_getting_started\" or \"EliteMobs/creating_bosses\"."
      }
    }
  }

  arguments 12 lines copy
• get_config_schema unknown never probed

  One config type's fields as Forge edits and validates them: key, value type, default, whether it is required, description and allowed values. Long option lists are shortened; pass field to get one field with all its options.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "type"
    ],
    "properties": {
      "type": {
        "type": "string",
        "description": "A type from list_config_types, such as \"custom-boss\" or \"fmm-pet\"."
      },
      "field": {
        "type": "string",
        "description": "Optional field key; returns only that field, with every allowed value."
      }
    }
  }

  arguments 16 lines copy
• validate_config_files unknown never probed

  Validate plugin config files (YAML and Lua) with Forge's validator: required fields, allowed values, plugin rules, Lua analysis, and references between the files you send (a boss's powers, a dungeon's bosses). Send each file with its server path, such as "plugins/EliteMobs/custombosses/frost_king.yml", so Forge can tell its type. A reference to a file you did not send is reported as not found in the workspace, which here means this call's files. Up to 50 files per call. Nothing is stored.

  mcp-tool

  1234567891011121314151617181920212223242526272829

  {
    "type": "object",
    "required": [
      "files"
    ],
    "properties": {
      "files": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "path",
            "content"
          ],
          "properties": {
            "path": {
              "type": "string",
              "description": "Server path or plugin-relative path, such as \"plugins/EliteMobs/powers/frost_nova.lua\"."
            },
            "content": {
              "type": "string",
              "description": "The full file content."
            }
          }
        },
        "description": "The files to check together."
      }
    }
  }

  arguments 29 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.