modrinth-mcp

An MCP server that wraps the Modrinth API so an AI agent (Claude Code, Claude Desktop, Cursor, …) can search projects, read project/version metadata, and publish Minecraft mods — create projects and upload built jars as new versions.

Tools

Read-only tools work without a token. Anything that writes needs a Modrinth Personal Access Token.

Related MCP server: ModWrench MCP Server

Getting a token

Create a PAT at https://modrinth.com/settings/pats with these scopes:

• Read projects

• Read versions

• Create versions

• Write versions

Set it as the MODRINTH_TOKEN environment variable.

Install

As a Claude Code plugin

/plugin marketplace add justinscott12/modrinth-mcp
/plugin install modrinth-mcp@justinscott12

You'll be prompted for your Modrinth token when enabling the plugin. It runs the published npm package under the hood via npx.

As an MCP server (any client)

Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "modrinth": {
      "command": "npx",
      "args": ["-y", "@justinscott12/modrinth-mcp"],
      "env": {
        "MODRINTH_TOKEN": "your-modrinth-pat"
      }
    }
  }
}

Or in Claude Code directly:

claude mcp add modrinth --env MODRINTH_TOKEN=your-modrinth-pat -- npx -y @justinscott12/modrinth-mcp

Environment variables

Example flow

1. modrinth_whoami — confirm auth works.

2. modrinth_create_project — create the project page (created as a draft).

3. modrinth_create_version — upload your built jar(s) with the target game_versions and loaders.

4. Submit the project for review on the Modrinth site when ready.

Note: create_version and create_project publish public content. Only call them when you actually intend to publish.

Development

npm install
MODRINTH_STAGING=1 MODRINTH_TOKEN=your-staging-pat npm start

The server speaks MCP over stdio. stdout is reserved for the protocol; logs go to stderr.

License

MIT