I would like to suggest adding an Environment / Side Compatibility field to the CurseForge API for Minecraft mods.

Currently, the API provides useful information such as Minecraft versions, mod loaders, files, dependencies, categories, and descriptions, but there is no reliable structured field that tells API users whether a mod supports the client, server, or both environments.

This makes it difficult for server management tools, launchers, modpack managers, and automated installers to determine whether a mod should be installed on a dedicated Minecraft server.

It would be very useful if mod authors could specify the supported environment for their projects or individual files.

For example:

{
  "environment": {
    "client": "required",
    "server": "required"
  }
}

Possible values could include:

• required

• optional

• unsupported

• unknown

This would allow the API to represent common situations such as:

Client-only mod

{
  "client": "required",
  "server": "unsupported"
}

Server-only mod

{
  "client": "unsupported",
  "server": "required"
}

Required on both client and server

{
  "client": "required",
  "server": "required"
}

Server supported, but optional on the client

{
  "client": "optional",
  "server": "required"
}

Ideally, this information would be available through the CurseForge API on the project level and/or file level, because environment requirements may differ between versions or files.

This feature would greatly benefit:

• Minecraft server management panels

• Launchers

• Modpack installers

• Dedicated server installers

• Automated mod compatibility analysis

Without a structured environment field, third-party applications currently have to infer server compatibility from descriptions, filenames, external databases, or manual user verification, which is often inaccurate.

Adding this information to the API would make automated Minecraft mod and server management significantly more reliable.