Install Universal Modder in Cursor

Quick install

Choose Universal Modder in Cursor Marketplace, or clone the repository:

git clone https://github.com/rehan-remade/universal-modder
cd universal-modder

Open the cloned universal-modder folder in Cursor.

Before you start

Use an installed, authenticated Cursor environment with Git and Python available to its terminal. Review the shared requirements for um, ffmpeg and optional Blender work. Your Cursor account and the optional fal service have separate costs.

Cursor supports a marketplace route and a clone route. The steps below follow the clone, so you can inspect every discovery file the agent loads.

Step-by-step install

Step 1: Clone into a workspace you own

Run the quick-install commands in a directory where you keep development projects. Git creates a new universal-modder subfolder. If that folder already exists, inspect it before cloning again; do not overwrite an existing mod project.

Step 2: Open the repository root

Use Cursor's folder-opening control to select the clone itself. Opening only an examples subfolder can put the repository's agent instructions and MCP settings outside the project context.

The relevant files are:

Step 3: Review tools and restart the agent

Review the workspace trust prompt and the MCP configuration. Begin a new agent conversation after enabling the integration. Ask it which mod-any-game skill it can see and where that skill came from.

Asset tools can remain unused while you build with placeholder art. If you enable fal, pass your key through the appropriate local environment or protected tool settings. The installation overview explains the common key setup.

Step 4: Check the CLI in Cursor's terminal

um --help
um --version

If um is unavailable, install it with the standalone CLI route, open a fresh terminal and repeat the checks. A clone provides the wrapper, but the actual shell still needs a way to resolve it.

Check that it works

Ask the agent to report the loaded skill's source, the real CLI help output and the optional MCP connection state. Check a second terminal only if you intend to use um outside Cursor as well. Skill discovery, terminal PATH and a working fal connection are separate checks.

Your first prompt

Use the mod-any-game workflow for my installed Terraria game.
Read the relevant field notes and identify tModLoader, the game version
and the save folder. Plan a single weapon using placeholder art first.
Write the files you expect to change and how I can restore the original setup.

Continue with the Universal Modder tutorial once the plan matches your installation. The examples are useful references for loader APIs and asset pipelines.

Common errors in Cursor

• No skills found: confirm that Cursor opened the repository root and that .agents/skills exists. Start a fresh agent conversation after changing project settings.
• fal is absent or disconnected: inspect .cursor/mcp.json and the tool's status. Confirm the key is available to the process only if you intend to generate assets.
• um cannot be found: use PATH diagnosis; installing a Python package in an unrelated terminal can leave Cursor's environment unchanged.
• Clone fails: run git --version and check the destination directory. Preserve the exact authentication or network error if Git itself works.

Uninstall

For a marketplace installation, remove Universal Modder through Cursor's plugin controls. For the clone route, close the folder and preserve any mod source, notes and backups before removing that clone. Remove only integration entries you copied into another workspace; keep unrelated MCP servers and skills.

A separately installed um remains until you use its tool-manager uninstall command.

Other agents

Compare Claude Code, Codex, Gemini CLI, VS Code / Copilot and OpenCode. The installation overview keeps all six agents and the skills-only route together.