Server data from the Official MCP Registry
One MCP server for mod platforms and local modding diagnostics. No data kept.
One MCP server for mod platforms and local modding diagnostics. No data kept.
Valid MCP server (1 strong, 3 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
14 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-171county-modwrench": {
"args": [
"-y",
"@modwrench/cli"
],
"command": "npx"
}
}
}From the project's GitHub README.
One wrench. Every mod platform. No data kept.
ModWrench is a Model Context Protocol (MCP) server that lets your AI assistant talk to mod platforms on your behalf. Discover mods, read changelogs, check versions, browse by tag, manage your modding workflow — from inside Claude Desktop, Claude Code, Cursor, ChatGPT, or any MCP-compatible client.
ModWrench is a bridge. It holds nothing about you. Your API keys live in your OS keychain. Your conversations stay in your AI client. Nothing is logged, nothing is sent anywhere except the platforms you're already using.
Built by a tinkerer who didn't see this coming. The modding community deserves better tooling than what the platforms ship by default — so here's a wrench.
ModWrench bridges four of the biggest modding platforms on Earth, plus a local workbench for diagnostics:
Each capability is a separate MCP package (@modwrench/nexus, @modwrench/modio, @modwrench/thunderstore, @modwrench/modrinth, @modwrench/workbench). Install one, some, or all — same wrench, your choice of attachments. The CLI meta-server (@modwrench/cli) composes whichever you've configured into a single MCP entry.
Nexus + mod.io (platform tools — read-only API clients):
Thunderstore (platform tools — read-only public API, no auth required):
thunderstore_list_communities / thunderstore_get_community — discover the 270+ games on Thunderstorethunderstore_list_mods / thunderstore_get_mod — browse and inspect mods in a communitythunderstore_search_mods — substring search by namethunderstore_mod_versions — full version history with downloads + dependenciesthunderstore_top_mods — highest-rated mods in a communityModrinth (platform tools — read-only public API, no auth required):
modrinth_search — full-text search with facets (project_type, loader, game_version, category)modrinth_get_project — single mod/modpack/plugin/datapack/resourcepack/shader by ID or slugmodrinth_get_versions / modrinth_get_version — version history + specific-version detailsmodrinth_list_categories / modrinth_list_loaders / modrinth_list_game_versions — taxonomy lookups for filteringWorkbench (local diagnostics — no credentials required, except mw_query_mod_metadata):
mw_detect_environment — find the user's games, mod managers, mod loaders, Proton versionsmw_read_load_order — normalize the load order across MO2 / r2modman / Vortex (best-effort)mw_parse_crashlog — structured parse of Crash Logger SSE, Buffout 4, NetScriptFramework, BepInEx, and Minecraft crash-reportsmw_query_mod_metadata — cross-platform mod lookup with mandatory attribution preservedmw_check_known_conflicts — pairwise conflict checks against LOOT + community databaseThe LLM picks the right tool based on what you ask. You don't have to remember which tool does what — just talk.
You: What are the best lighting overhauls on Skyrim SE that don't require ENB?
Claude: [calls nexus_search_mods, filters by category and ENB-free flag,
checks changelogs for recent updates]
Claude: Three solid options updated in the last year:
1. Lux (by LordValeryon) — 4.8k endorsements, 1.2M downloads, last
updated March 2026. ENB-optional. Works with most weather mods.
2. ELE-LITE (by JawZ) — 2.1k endorsements, completely standalone,
low performance hit. Best for older systems.
3. Lanterns of Skyrim II (by mannygt) — adds world lighting via
placed lanterns rather than reworking interior lighting. Pairs
well with either of the above.
All three are free and CC-licensed. Original authors retain
attribution and rights.
The conversation is the interface. Tool names are internal.
These are not promises. They are constraints baked into the code. PRs that violate them will not be merged.
You'll need Node.js 20+ and an MCP-compatible client.
ModWrench is published on npm as @modwrench/cli. The command below pulls the current public package and starts the stdio MCP server.
Add this to your MCP config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows, equivalent path on Linux):
{
"mcpServers": {
"modwrench": {
"command": "npx",
"args": ["-y", "@modwrench/cli"]
}
}
}
Restart your client. Run modwrench auth login nexus and modwrench auth login modio in a terminal once to set up your API keys. Tokens go straight to your keychain — ModWrench never sees them as files.
Add to .cursor/mcp.json or your client's equivalent:
{
"mcpServers": {
"modwrench": {
"command": "npx",
"args": ["-y", "@modwrench/cli"]
}
}
}
ChatGPT requires a remote MCP server (Streamable HTTP transport) rather than the stdio path the clients above use. ModWrench now includes @modwrench/remote, a first remote-safe MVP for public read-only tools: Modrinth + Thunderstore. It does not expose Nexus/mod.io credentials or local workbench filesystem tools.
From source:
npm run build --workspace @modwrench/remote
npm run start --workspace @modwrench/remote
Connect remote-capable clients to /mcp on the hosted server, for example https://your-host.example/mcp. See docs/remote-deployment.md for scope, host settings, and what remains before credentialed remote tools are safe.
npm install -g @modwrench/cli
modwrench --version
modwrench auth login nexus
modwrench auth login modio
Nexus Mods: Settings → API Access → generate a personal key. Free tier supports the full read API at reasonable rate limits. Premium accounts get higher limits.
mod.io: Account settings → API Access → generate a key. Free for all read operations.
ModWrench never asks for your password. Only for the API keys, which you can revoke from each platform any time without uninstalling ModWrench.
ModWrench is structured around several growing waves of capability. v1 and v2 are shipped. The next waves add smarter catalogs, local toolchain awareness, and creator-side publishing.
mod.io + Nexus Mods. 12 Nexus tools + 11 mod.io tools — 23 total, exposed through one MCP entry via @modwrench/cli (or as two isolated processes if you prefer). Read-side coverage of discovery, search, metadata, changelogs, archive previews, and reverse-lookup-by-hash on the Nexus side; popular/trending/dependencies/tags on the mod.io side. OAuth shipped on both platforms (read scopes only); writes deferred until the v3 publishing phase.
Five atomic tools (@modwrench/workbench) that compose under LLM reasoning into a conversational diagnostic experience. All read-only:
mw_detect_environment — detect OS, Steam Deck status, Steam libraries, mod-friendly games (Skyrim SE/LE/VR, Fallout 3/NV/4/4VR, Starfield, Oblivion, Lethal Company, Valheim, R.E.P.O., Risk of Rain 2, Dyson Sphere Program, BONEWORKS, Sims 4), mod managers (Vortex / MO2 / r2modman / CurseForge App), mod loaders (SKSE / F4SE / SFSE / NVSE / FOSE / OBSE / BepInEx 5 / BepInEx 6 IL2CPP / MelonLoader), and Proton versions on Linuxmw_read_load_order — normalize the user's installed mod list across managers. MO2 (full: modlist.txt + plugins.txt + active-profile discovery from ModOrganizer.ini) and r2modman (full: mods.yml with author + version preserved) are first-class; Vortex is best-effort folder scan, with an honest warning field because its LevelDB state isn't parsed yetmw_parse_crashlog — structured parsing (no diagnosis — that's the LLM's job) of Crash Logger SSE, Buffout 4, NetScriptFramework, BepInEx exception traces, and Minecraft crash-reports. Extracts exception type/address, call stack, registers, loaded plugins, and FormID-based suspected refsmw_query_mod_metadata — normalized cross-platform mod lookup with mandatory attribution (author + sourcePlatform + pageUrl on every result). Nexus + mod.io live today; Thunderstore + CurseForge planned for v3+mw_check_known_conflicts — pairwise conflict checks against LOOT's live masterlist (Bethesda games) and ModWrench's bundled community-curated database (data/conflicts/<gameId>.json — see packages/workbench/data/conflicts/README.md for the contribution schema)The LLM orchestrates these into the compound experience: "My Skyrim keeps crashing on the bridge to Whiterun" → detect environment, read load order, parse the crashlog, look up suspect plugins on Nexus, cross-reference against LOOT's masterlist, return a diagnosis with attribution preserved end-to-end.
The wiring-prompt's sixth tool (mw_explain) was intentionally not built — the LLM formats responses natively and the wiring prompt explicitly marks it optional.
The next workbench layer connects ModWrench to the tools serious modders already keep open. These start read-only wherever possible: detect installed tools, parse their project/profile state, surface clear next steps, and only write when a toolchain has a safe, explicit confirmation path.
Bethesda toolchain:
Unity / BepInEx toolchain:
REDengine toolchain:
Cyberpunk 2077 is the lead target for this lane. The Witcher side is worth exploring after Cyberpunk workflows are proven, but the first pass stays cheap to prototype and easy to back out of if the maintenance cost gets weird.
The creator side. One mod definition fans out across platforms in a single conversational command. Permission discipline is non-negotiable: a mod flagged "no asset reuse" on its source platform never gets republished elsewhere by ModWrench.
Initial targets:
As the platform count grows, the tool catalog gets large. ModWrench's answer: boot-time auto-activation of platforms based on what's actually installed on the user's machine, plus an mw_activate_platform meta-tool for runtime opt-in. A Skyrim modder sees ~18 tools sized for their setup; a Lethal Company modder sees ~16 sized for theirs — not the union of every platform ModWrench could ever support.
One MCP entry, personalized catalog per user. Full architecture spec: docs/dynamic-catalog-architecture.md.
ModWrench is built in TypeScript on Node.js. It runs natively on Linux and Steam Deck Desktop Mode with no Windows-specific dependencies. v2's environment detection (mw_detect_environment) explicitly handles Proton prefix paths and flags Steam Deck Game Mode limitations.
If you mod on Linux or Steam Deck, ModWrench is for you. File issues with Linux-specific behavior — those are a priority, not an edge case.
ModWrench is built openly and runs on community input. The non-negotiables (above) are firm. Everything else is open for discussion.
The fastest ways to contribute right now:
data/conflicts/<gameId>.json is the file that powers mw_check_known_conflicts. PRs welcome with sources cited.packages/core/src/detect/ is where the patterns live.@modwrench/<platform>). The shape is documented in docs/adding-a-platform.md.License: Apache 2.0. Contributors retain copyright. ModWrench uses the Developer Certificate of Origin (DCO) — sign off your commits with git commit -s and you're done. No CLA, no paperwork. See CONTRIBUTING.md for details.
Code of conduct: Be a wrench, not a hammer. Modders have been burned by enough hammers.
ModWrench exists because of decades of work by mod authors who shared their craft for free, and because of the platforms that hosted that work even when the economics were marginal.
Particular gratitude to:
If you build mods, you make the world more interesting. ModWrench's only job is to get out of your way.
ModWrench is early. v1 shipped (Nexus + mod.io + Thunderstore platforms, 30 read-only tools). v2 shipped (workbench — local diagnostics, 5 tools, 55 tests). v2.5 (dynamic catalog) and v3 (multi-platform publishing) are designed but not yet built. See ROADMAP.md for what's coming. The roadmap is genuine intent, not a marketing document — but software is software and timelines slip.
Try it. Break it. Tell me. That's the whole loop.
ModWrench — built by Sean (and the AI assistants he was modding with at the time).
Apache 2.0 license, no telemetry, no lock-in.
Project home: github.com/171county/modwrench. Published in the MCP Registry as io.github.171county/modwrench.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.