vsmoddb-mcp
Related Servers
Alternatives to vsmoddb-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables managing quest-log ideas, statuses, and mission log directly from MCP clients, allowing project tracking and updates without going through git/GitHub.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Discord using personal user tokens instead of bot applications, allowing for seamless message management and server exploration. It provides tools for reading history, sending messages, and searching across channels and DMs directly through MCP-compatible clients.10MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for the CivNode 'slow web' social platform that enables interaction with monuments, forums, and creative writing. It allows users to manage their profiles, send private or anonymous messages, and engage with the community's unique social features.-
- AlicenseBqualityBmaintenanceLets MCP clients browse vanilla data, add or override table rows, edit asset properties, check Blueprint symbols, and validate mods before packaging.21MIT
- AlicenseAqualityAmaintenanceExposes Obsidian-style Markdown vaults to MCP clients, enabling reading, writing, searching, and version-controlled editing of notes with automatic git snapshots and restore.1424 npm1MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to explore a local War Selection installation by reading mod code, game JSON data, logs, and Lua API indexes, while also linting mods, parsing Lua log errors, diffing mod and game versions, generating scaffolds, and watching logs in real time.26MIT
TDQS
Scored across 15 tools
Each tool targets a clearly distinct resource or action: session status, mod listing/retrieval/update, tags, releases, comments, and notifications. Potential overlaps like update_mod replacing tags versus add_mod_tags for incremental changes are explicitly clarified in the descriptions. An agent can reliably select the correct tool.
All tools use snake_case, and the vast majority follow a verb_noun or verb_noun_modifier pattern (list_my_mods, update_release, mark_notifications_read). Minor deviations like moddb_status (noun-first) and reply_to_comment (prepositional) are still readable and predictable.
15 tools sits at the upper end of the ideal 3-15 range, and every tool earns its place across authentication, mod management, tags, releases, comments, and notifications. There are no redundant or trivial tools.
Core lifecycle coverage is strong: mods (list/get/update), releases (upload/update/retract), comments (list/reply/edit/delete), notifications (list/mark read), and tags (list/add). Missing create_mod and a dedicated remove_mod_tags tool, and top-level comment creation is not clearly supported, but agents can work around most of these gaps.