prts-mcp
Related Servers
Alternatives to prts-mcp
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and access Arknights game data including operator information, enemy intelligence, skills, talents, and attributes through PRTS.wiki integration. Provides fuzzy search functionality for operators and enemies with clean Markdown output.9MIT
Related Servers

AmiyaBot MCP Serverofficial
FlicenseNot gradedqualityAmaintenanceProvides MCP server and CLI for querying Arknights game data, including operator skills, glossary, and resource updates.3-- AlicenseAqualityBmaintenanceProvides read-only Arknights intelligence over MCP, enabling structured queries about stages, enemies, operators, and modules with region tagging and evidence-backed analysis. It uses versioned SQLite snapshots and never fetches upstream data at query time.13Apache 2.0
- FlicenseBqualityCmaintenanceA MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!227-
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4320MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides tools to add to, search, and manage a wiki knowledge base, enabling AI chat tools to contribute and retrieve information from the wiki via natural language prompts.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes structured World of Warcraft API data (functions, deprecated replacements, enums, events, widget methods) to AI agents, enabling querying and exploration of WoW API without wiki parsing.19 npm13MIT
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: wiki search/page reading, operator data by type, and story navigation at event/chapter/activity levels. The overlap between read_story and read_activity is clear (single chapter vs full event), and list_story_events vs list_stories is also well separated by level.
Tool names mostly follow clear verb_noun patterns: search_, read_, get_, list_. Minor inconsistencies exist, such as 'search_prts' vs 'read_prts_page' and 'list_story_events' vs 'list_stories', but the overall pattern is readable and predictable.
Nine tools is a reasonable size for this wiki-focused server. The set covers wiki browsing, operator lookups, and story exploration without unnecessary fragmentation.
The story workflow is well covered from event list down to individual dialogue, and operator info is split into useful categories. Minor gaps exist, such as no explicit operator search/list or skill detail tool, but the generic wiki read/search tools provide a workaround.