modrinth-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODRINTH_TOKEN | No | Modrinth Personal Access Token. Required for write actions. | |
| MODRINTH_STAGING | No | Set to 1 to hit https://staging-api.modrinth.com for safe testing. | unset |
| MODRINTH_USER_AGENT | No | Override the User-Agent sent to Modrinth. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| modrinth_whoamiA | Verify the configured Modrinth token and return the authenticated user (username, id, email, role). Use this first to confirm auth works. |
| modrinth_search_projectsA | Search public Modrinth projects. Returns a compact list of hits (slug, title, project_type, downloads, description). |
| modrinth_get_projectA | Get a Modrinth project's metadata by slug or id (title, type, loaders, game_versions, published version ids, status). |
| modrinth_list_project_versionsA | List a project's published versions (version_number, id, type, loaders, game_versions, download url of primary file). |
| modrinth_create_versionA | Publish a NEW version to an existing Modrinth project by uploading one or more built jar files. This is a write action that publishes public content — only call it when the user has explicitly asked to publish. The project must already exist on Modrinth. |
| modrinth_create_projectA | Create a NEW Modrinth project (the initial project page). Created as a DRAFT — nothing is public until you submit it for review on the site or set requested_status. This is a write action; only call it when the user explicitly asks to create a new project. After it exists, publish jars with modrinth_create_version. |
| modrinth_modify_versionA | Edit metadata of an EXISTING published version (name, changelog, version_type, loaders, game_versions, featured). Does not upload files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action and resource: authentication (whoami), search, fetch, list versions, create project, create version, and modify version. No two tools appear to perform the same operation; even search and get are clearly differentiated by result granularity.
All tools follow the consistent modrinth_<verb>_<object> pattern (e.g., modrinth_search_projects, modrinth_create_version). The naming is predictable and grammatically uniform, making it easy for an agent to infer the action and target.
Seven tools is well within the ideal 3–15 range. Each tool serves a clear, non-redundant purpose in the domain of Modrinth project and version management, covering authentication, discovery, publishing, and editing without bloat.
The toolset covers core workflows: authenticate, search, inspect, publish, and update. It lacks project-level updates (e.g., changing project metadata) or deletion, but those are less critical for the common publish-and-iterate cycle. The missing operations are non-blocking for most agent tasks.