Skip to the content

Modding

Make mods for CursedForge

A mod is a pack of data and art: items, recipes, components and models. CursedForge staff check each mod before world owners can turn it on.

Become a modder

  1. Sign in on the player portal.
  2. Open Modder and apply. Read and sign the Modder Terms and the Modder Agreement.
  3. When staff approve you, the Modder Kit opens: the modding guide, the pack schemas, the base content ids and the example packs.

Connect an AI agent

An approved modder can connect an AI agent (for example Claude Code or Codex) to the CursedForge modder MCP server. The agent can then read the Modder Kit, find the rules of each component and each error, read the example packs, and check a draft pack before you upload it.

The server gives only the public text of the Modder Kit. It cannot read your files, and it does not upload a mod.

  1. On the player portal, open Modder, then Connect an AI agent.
  2. Make a token. Copy it at once: the portal shows it one time only.
  3. Give the token to your agent with one of the examples below.

A token is valid for 180 days. You can have a maximum of 5 active tokens. If your modder role ends, your tokens become invalid.

WARNING: A token is a password. If a different person gets it, that person can use the server in your name. Do not put a token in a file that you share or commit. If you think that a different person has your token, revoke the token on the portal.

Claude Code

Run this command, with your token in place of <your token>:

claude mcp add --transport http cursedforge https://mcp.cursed-forge.com/mcp --header "Authorization: Bearer <your token>"

Codex

Put the token in the environment variable MODDER_MCP_TOKEN. Then add these lines to ~/.codex/config.toml:

[mcp_servers.cursedforge]
url = "https://mcp.cursed-forge.com/mcp"
bearer_token_env_var = "MODDER_MCP_TOKEN"

A different MCP client

Use these three settings:

Transport: streamable HTTP
URL:       https://mcp.cursed-forge.com/mcp
Header:    Authorization: Bearer <your token>

The tools

  • docs_list, docs_read, docs_search: the modding guide and the pack schemas.
  • schema_component, schema_table: the fields, bounds and rule ids of a component or a pack table.
  • rules_lookup: what a rule id of a check means, and how to correct the error.
  • examples: the example packs.
  • pack_check: checks the JSON files of a draft pack with the same loader as the upload.

The Privacy Policy tells you what the server keeps.