Back to search
mod-mcps
MCP serverGitHub
Unified MCP server and client for automating video game mod creation and maintenance across Nexus Mods, ModDB, and extensible hosting sites.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/msk-one--mod-mcps)HTML
<a href="/listings/msk-one--mod-mcps"><img src="/api/listings/msk-one--mod-mcps/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Build & Test
dotnet build ModMcp.slnx -c Release dotnet test ModMcp.slnx -c Release
2. Run the MCP Client CLI (`stdio` mode — spawns server automatically)
# Protocol handshake, tool/resource/prompt check, sites & auth status dotnet run --project src/ModMcp.Client -c Release -- doctor # Inspect capabilities and per-site actions dotnet run --project src/ModMcp.Client -c Release -- sites dotnet run --project src/ModMcp.Client -c Release -- actions nexusmods dotnet run --project src/ModMcp.Client -c Release -- actions moddb # Plan sync from a unified manifest dotnet run --project src/ModMcp.Client -c Release -- plan --manifest examples/mod-manifest.example.json # Dry-run multi-site publish (pass --live to execute live API upload / write staging kits) dotnet run --project src/ModMcp.Client -c Release -- publish --manifest examples/mod-manifest.example.json --sites nexusmods,moddb
3. Run the MCP Server over Streamable HTTP
dotnet run --project src/ModMcp.Server -c Release -- --transport http --host 127.0.0.1 --port 8080 # Connect the MCP Client over Streamable HTTP: dotnet run --project src/ModMcp.Client -c Release -- --url http://127.0.0.1:8080/mcp doctor
---
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 98 lines
- # ModMCP — Unified Mod Hosting MCP Server & Client
- **One MCP interface to automate creating, publishing, and maintaining video game mods across mod hosting sites** — built in **.NET 10 (C#)** using the official `ModelContextProtocol` SDK (`stdio` + `Streamable HTTP`).
- Designed for **Claude Code**, **Antigravity**, **Cursor**, **Claude Desktop**, and direct **CLI / CI** automation.
- ---
- ## Architecture Highlights
- - **Unified Cross-Site Tools** (`list_sites`, `validate_auth`, `get_mod`, `list_mod_files`, `create_mod`, `publish_release`, `update_changelog`, `plan_sync`) operating on a single cross-platform `mod-manifest.json`.
- - **Per-Site Specific Actions** (`list_site_actions`, `run_site_action`) allowing each site adapter to expose platform-unique features without polluting the shared tool surface.
- - **Explicit Capability Matrix** — every adapter declares what it can execute via live API vs. deterministic **Release Staging Kits** (BBCode conversion, SHA-256 verification, form field payloads, and direct web submission links).
- - **Safe-by-Default Authoring** — all mutating tools default to `dry_run=true` unless explicitly overridden.
- - **Pluggable Adapter Registry (`IModSiteAdapter`)** — v1 ships with **Nexus Mods** (`nexusmods`) and **ModDB** (`moddb`); adding Modrinth, mod.io, CurseForge, Thunderstore, or GameBanana requires implementing a single `IModSiteAdapter` class.
- ---
- ## Site Capabilities (v1)
- | Site | Adapter ID | Read Mod & Files | Create Mod Page | Upload / Push Versions | Changelogs | Per-Site Actions |
- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
- | **Nexus Mods** | `nexusmods` | Official REST v1 + GraphQL v2 + REST v3 | Staged BBCode Kit (`/mods/add`) | **Official API v3** (`<= 100 MiB` single + `> 100 MiB` multipart S3/R2 presigned upload, `finalise`, polling, `POST /mod-files`, `POST /mod-files/{id}/versions`) | **Official API v3** (`POST /mods/{id}/changelogs`) | `upload_blob`, `create_mod_file`, `push_file_version`, `update_mod_file`, `add_changelog`, `list_game_dlcs`, `get_mod_graphql`, `prepare_mod_page_kit` |
- | **ModDB** | `moddb` | Public HTML + official RSS feeds (respects `robots.txt`; never bypasses CAPTCHA/anti-bot gates) | Staged BBCode Kit (`/mods/add`) | Staged Release Kit (`.modmcp/staging/moddb/{version}/` + `/addfile` deep link) | Staged BBCode News Kit (`/news/add`) | `parse_mod_page`, `list_rss_updates`, `prepare_release_kit`, `validate_archive` |
- ---
- ## Quick Start
- ### 1. Build & Test
- ```bash
- dotnet build ModMcp.slnx -c Release
- dotnet test ModMcp.slnx -c Release
- ```
- ### 2. Run the MCP Client CLI (`stdio` mode — spawns server automatically)
- ```bash
- # Protocol handshake, tool/resource/prompt check, sites & auth status
- dotnet run --project src/ModMcp.Client -c Release -- doctor
- # Inspect capabilities and per-site actions
- dotnet run --project src/ModMcp.Client -c Release -- sites
- dotnet run --project src/ModMcp.Client -c Release -- actions nexusmods
- dotnet run --project src/ModMcp.Client -c Release -- actions moddb
- # Plan sync from a unified manifest
- dotnet run --project src/ModMcp.Client -c Release -- plan --manifest examples/mod-manifest.example.json
- # Dry-run multi-site publish (pass --live to execute live API upload / write staging kits)
- dotnet run --project src/ModMcp.Client -c Release -- publish --manifest examples/mod-manifest.example.json --sites nexusmods,moddb
- ```
- ### 3. Run the MCP Server over Streamable HTTP
- ```bash
- dotnet run --project src/ModMcp.Server -c Release -- --transport http --host 127.0.0.1 --port 8080
- # Connect the MCP Client over Streamable HTTP:
- dotnet run --project src/ModMcp.Client -c Release -- --url http://127.0.0.1:8080/mcp doctor
- ```
- ---
- ## Connecting to AI Surfaces
- ### Claude Code
- ```bash
- claude mcp add mod-mcp \
- -e NEXUSMODS_API_KEY="$NEXUSMODS_API_KEY" \
- -e MODMCP_DEFAULT_DRY_RUN="true" \
- -- dotnet /home/obmp/mod-mcps/src/ModMcp.Server/bin/Release/net10.0/mod-mcp-server.dll --transport stdio
- ```
- Or copy [`examples/claude-code.mcp.json`](examples/claude-code.mcp.json) to `.mcp.json`.
- ### Antigravity
- Merge [`examples/antigravity.mcp.json`](examples/antigravity.mcp.json) into `~/.gemini/antigravity/mcp_config.json`, or generate it via:
- ```bash
- dotnet run --project src/ModMcp.Client -c Release -- init-config --surface antigravity
- ```
- ### Cursor / Claude Desktop
- Generate ready-to-paste JSON via:
- ```bash
- dotnet run --project src/ModMcp.Client -c Release -- init-config --surface cursor
- dotnet run --project src/ModMcp.Client -c Release -- init-config --surface claude-desktop
- ```
- ---
- ## Environment Variables
- | Variable | Description |
- | :--- | :--- |
- | `NEXUSMODS_API_KEY` | Personal API key from Nexus Mods account settings (`apikey` header). Never echoed in logs or tool outputs. |
- | `MODMCP_DEFAULT_DRY_RUN` | Defaults to `true`. Set to `false` only if you want write tools to execute live without passing `dry_run=false`. |
- | `MODMCP_SITES` | Optional comma-separated filter of enabled site adapters (e.g. `nexusmods,moddb`). |
- | `MODMCP_TRANSPORT` | `stdio` (default) or `http`. |
- | `NEXUSMODS_API_BASE` | Optional override for Nexus Mods v3 base URL (default `https://api.nexusmods.com/v3`). |
- | `MODDB_BASE_URL` | Optional override for ModDB base URL (default `https://www.moddb.com`). |
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.