Raid Shadow Legends MCP Server

What is Raid Shadow Legends MCP Server?

The Raid Shadow Legends MCP Server controls Raid Shadow Legends Tasker automation via a Mission Control Protocol server. It integrates with Tasker on Android using an MQTT broker and a REST API, allowing users to send commands, set automation goals, and monitor game status.

How to use Raid Shadow Legends MCP Server?

Install Node.js 18+, an MQTT broker running on port 9900, and Tasker with the Raid automation project on an Android device. Clone the repository, run npm install, npm run build, and npm start. Change the MQTT broker URL by modifying MQTT_SERVER_URL in src/index.ts and src/RaidShadowLegendsButItsMCP.ts. Use the REST API endpoints (/api/status, /api/command, /api/goal) or MCP tools to interact.

Key features of Raid Shadow Legends MCP Server

• Provides MCP tools: RaidShadowLegendsControl, RaidShadowLegendsStatus, RaidShadowLegendsSetGoal
• REST API for status, commands, and goal setting
• Communicates via MQTT on topics commands/raid, commands/raid/goals, status/raid
• Supports commands like raid_start, clan_boss, raid_auto_toggle, raid_end, raid_lock_toggle
• Requires Tasker project on Android to parse and execute commands
• Publishes status updates (progress, battle count, energy) in JSON format

Use cases of Raid Shadow Legends MCP Server

• Automate campaign battles by sending raid_start with mode and stage via REST or MCP
• Set battle goals (e.g., 20 campaign battles, auto-sell enabled) and monitor progress
• Remotely control Raid Shadow Legends automation from another device or service
• Integrate with home automation or voice assistants to trigger in-game actions

FAQ from Raid Shadow Legends MCP Server

What is required to run the server?

Node.js 18+, an MQTT broker (default port 9900), and Tasker on an Android device with the Raid Shadow Legends automation project installed.

How does the server communicate with Tasker?

It uses an MQTT broker. The server publishes commands to topics like commands/raid and subscribes to status/raid; Tasker must subscribe to commands and publish status updates.

What data does the server expose?

Through the REST API (/api/status) it returns last update time, raid status, progress percentage, battle count, and energy remaining.

What transport protocols does the server support?

REST API (HTTP) and MQTT. MCP tools are also available.

Is there authentication for the API?

The README notes adding authentication as a TODO; currently there is no authentication mentioned.