# 3aKHP/prts-mcp [Health: Active]

**Category:** 🎮 Gaming  
**Repository:** https://github.com/3aKHP/prts-mcp  
**GitHub Stars:** 14  
**npm Downloads (last month):** 485  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/3akhp-prts-mcp

## Description
MCP Server for Arknights, querying the PRTS Wiki API and serving auto-synced operator archives and voice lines from game data. Designed for fan-creation (同人創作) AI agents. Python (stdio/Docker) and TypeScript (Streamable HTTP) implementations.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "prts-mcp": {
    "command": "npx",
    "args": ["-y","prts-mcp@3.1.1"],
    "env": {
      "PRTS_TRANSPORT": "",
      "IMAGES_ENABLED": "",
      "LOCAL_IMAGE": ""
    }
  }
}
```

**Requires environment variables:** `PRTS_TRANSPORT`, `IMAGES_ENABLED`, `LOCAL_IMAGE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What 3aKHP/prts-mcp MCP server does

3aKHP/prts-mcp MCP server provides Arknights reference data to AI agents through the Model Context Protocol. It combines requests to the PRTS Wiki MediaWiki API with locally synchronized game data, covering lore, operator records, dialogue, combat information, and item data. The project is suited to the 🎮 Gaming category and specifically targets fan-creation workflows.

Wiki-oriented tools can search for articles, read pages, and request structured fields from top-level templates. Operator tools retrieve archives, Chinese voice lines, profiles, talents, base skills, combat skill levels, stat panels, memoir links, and available artwork or skins. Story tools list events and chapters, summarize chapters, read dialogue, search lines with filters, and identify speakers or character appearances.

## How it works

The current stable 3.x line is implemented in Rust and handles MCP protocol traffic, wiki requests, and game-data queries in one native binary. The npm packages act as launch bridges to that binary. Clients can communicate through stdio when they start the process locally, or through Streamable HTTP when the server runs as a service. The main npm entry point defaults to HTTP on port 3000 and exposes `/mcp` plus a `/health` endpoint; setting `PRTS_TRANSPORT=stdio` selects subprocess-friendly stdio mode.

The 24-tool release includes search and retrieval operations for enemies, stages, items, operators, stories, and wiki pages. Full-text searches support domains such as operators, enemies, stages, items, building skills, and skills. Story searches can filter by character, line type, event, and surrounding context. Artwork retrieval uses MediaWiki by default, with local AKDP assets available when `LOCAL_IMAGE=true`.

## Setup and configuration

3aKHP/prts-mcp can be installed from npm with Node.js 22 or newer and npm 10 or newer, run from a Docker image, downloaded as a prebuilt native archive, or built from source with Rust and a C compiler. The standard npm command starts HTTP mode; a stdio environment setting is needed for local clients that spawn the server. Docker defaults to stdio, but accepts `PRTS_TRANSPORT=http` for HTTP deployment and can mount `/data` for persistent data.

Prebuilt archives are available for Linux x64 and ARM64 with glibc 2.28 or newer, Windows x64, and macOS x64 or ARM64 on macOS 14 or newer. Source or archive layouts must preserve the `bin/` and `data/` directories. Existing 2.x command names remain available through the compatibility package, while 2.8.x can be selected with its documented npm tag or Docker image.

## Limitations and notes

3aKHP/prts-mcp expects operator names in Chinese for operator archive, voice-line, and basic-information queries. Image support is optional: setting `IMAGES_ENABLED=false` removes `operator_artwork`, reducing the tool count from 24 to 23. The prebuilt native archives do not support Linux musl or Alpine, nor CPU architectures outside those listed by the project. The README identifies Claude Desktop, Claude Code, Roo Code, and Codex as clients with configuration guidance; Chatbox is also named as an MCP-compatible client.

The project is licensed under MIT. Stable 3.x and the maintained 2.x lines expose different implementation and command details, so deployments pinned to older releases should follow the matching documentation rather than assuming current defaults.

_Full upstream README: https://allmcps.com/mcp/3akhp-prts-mcp/readme_