[General] Get currently selected app/game information including developer_id, app_id, miniapp_id, and app name. CRITICAL: Call this tool FIRST before executing any leaderboard operations (create_leaderboard, list_leaderboards, etc.) to verify that an app has been selected. If no app is selected, guide the user through the selection process using list_developers_and_apps and select_app. Use this for: 1) Checking current selection before leaderboard operations, 2) Building preview links, 3) Verifying cached app. Not for H5 upload workflow.

Check environment configuration and user authentication status. Use this to verify the current TAPTAP_MCP_ENV, signer mode, TAPTAP_MCP_MAC_TOKEN, and TAPTAP_MCP_CLIENT_ID configuration. If the user asks how to switch between production and RND, call get_environment_switch_guide.

[Setup Guide] Explain how to switch this MCP server between production and RND environments from an MCP client configuration. Use this when the user asks to switch environment, use RND, test in RND, configure TAPTAP_MCP_ENV, or asks why RND needs TAPTAP_MCP_CLIENT_ID / TAPTAP_MCP_CLIENT_SECRET. This tool returns client config snippets and agent steps; it does not modify files by itself.

[Auth] Start OAuth 2.0 Device Code Flow to get authorization URL. Use this when: 1) User explicitly wants to authorize, 2) User needs to login or switch account, 3) Token expired or invalid. Returns a QR code URL for user to scan with TapTap App.

[Auth] Complete OAuth authorization after user has scanned QR code. Call this after user confirms they have completed authorization in browser. This tool will poll for the authorization result and save the token.

[General App Management] List developers and apps/games for the current user, including both level games and non-level games. For large accounts, the human-readable response shows a paged preview plus total counts; call again with offset/limit to continue. CRITICAL: Show the returned preview/counts to the user and explicitly ASK them to choose which app to use or provide app_id/name keywords - DO NOT automatically select an app without user confirmation, even if there is only one option. Use this for: 1) Initial exploration of available apps, 2) Switching between apps, 3) General app management (not H5 upload workflow). For H5 game upload, use prepare_h5_upload instead.

[General] Select a specific developer and app to use for subsequent operations. Supports both level games and non-level games. This will cache the selection for all modules (leaderboard, H5, current-app community tools, etc.). IMPORTANT: Only call this tool AFTER the user has explicitly confirmed which app they want to use. DO NOT call this tool automatically without user confirmation. Use this for: 1) General app selection, 2) Switching accounts, 3) After listing with list_developers_and_apps and receiving user confirmation. For H5 upload, you can also pass developerId/appId to prepare_h5_upload directly.

Create a new unverified developer identity on TapTap platform. Use this when user wants to create a new developer account.

Create a new app/game on TapTap platform. The newly created app will be automatically selected - no need to call select_app afterwards. Use this when user wants to create a new app.

Update the app's information on TapTap platform including name, genre, description, icon, banner, screenshots, and more.

Get the review status of an app/game. Use this to check if the app is published, under review, or rejected.

Upload an image to TapTap server and get a URL. Use this to upload icon, banner, or screenshots before calling update_app_info. Accepts either a local file path or base64 encoded image data.

Clear all cached authentication data and app selection. Use this when: 1) MAC Token expired or invalid, 2) Want to switch accounts, 3) Need to reset authentication. This will clear both OAuth token file and app cache.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through: 1) Call list_developers_and_apps, 2) Show list to user and ASK them to choose, 3) Call select_app with user confirmation. Get store overview metrics for the currently selected app, including page views, downloads, reserves, download requests, and daily trend data for an optional date range.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS verify the selected app context. Get review overview metrics for the currently selected app, including rating summary, rating score, positive/neutral/negative review counts, and trend data for an optional date range.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS verify the selected app context. Get community overview metrics for the currently selected app, including topic count, favorite count, page views, feed count, and trend data for an optional date range.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through: 1) Call list_developers_and_apps, 2) Show list to user and ASK them to choose, 3) Call select_app with user confirmation. Get a result-oriented store snapshot for the currently selected app, including app card info, current stats, rating summary, 30-day rating trend, version status, and visibility.

PREREQUISITE: An app MUST be selected first. Read forum contents for the currently selected app only. Use this to inspect the game forum feed before summarizing community topics. This tool is scoped to the selected app and MUST NOT be used for cross-game browsing.

PREREQUISITE: An app MUST be selected first. List reviews for the currently selected app only. Use this before like/reply actions so the user can inspect the review list and confirm the target review_id. Supports sort, pagination, collapsed reviews, and platform filter.

PREREQUISITE: An app MUST be selected first. Like a specific review for the currently selected app. IMPORTANT: Before calling this tool, first identify the target review by calling get_current_app_reviews or by showing the exact review to the user, then ASK for confirmation. DO NOT guess the target review_id. This tool only supports a single review like action.

PREREQUISITE: An app MUST be selected first. Reply to a specific review as the official app identity. CRITICAL: Always make sure the user has reviewed and approved the reply content before calling this tool. The server applies risk grading: LOW can be sent directly, MEDIUM/HIGH usually return a draft and need explicit follow-up confirmation. Only set confirm_high_risk=true after the user explicitly approves sending the risky draft.

⭐ READ THIS FIRST when user wants to integrate/接入/setup/add leaderboard功能. Returns complete step-by-step workflow. CRITICAL: Emphasizes NO SDK installation - tap is global object. Call this BEFORE making any implementation plans.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through: 1) Call list_developers_and_apps, 2) Show list to user and ASK them to choose, 3) Call select_app with user's choice. Create a new leaderboard on TapTap server. Auto-fetches developer_id and app_id from selected app. Returns leaderboard_id for client-side APIs.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through: 1) Call list_developers_and_apps, 2) Show list to user and ASK them to choose, 3) Call select_app with user's choice. List all leaderboards for currently selected app. IMPORTANT: When multiple leaderboards exist, ALWAYS show the complete list to the user and explicitly ASK them which one they want to use - DO NOT automatically choose a leaderboard without user confirmation.

PREREQUISITE: An app MUST be selected first. Publish leaderboard or set to whitelist-only mode. Before calling this tool, ensure an app is selected by calling get_current_app_info. IMPORTANT: If the leaderboard ID is not clear, call list_leaderboards first, show the list to the user, and ASK them which leaderboard they want to publish - DO NOT automatically select a leaderboard.

Get user leaderboard scores. Requires MAC Token authentication.

⭐ USE THIS TOOL FIRST when user asks about vibrate/振动/震动/vibration/haptic feedback/触觉反馈 functionality, wants to integrate/接入/setup/add/使用 vibrate功能, searches for vibrate API documentation/文档/教程/示例, asks how to use vibrate/vibrateShort/vibrateLong, needs vibration code examples/代码示例, or asks about vibration intensity/震动强度/震动类型. Returns complete step-by-step workflow. CRITICAL: Emphasizes NO SDK installation - tap is global object. Call this BEFORE making any implementation plans.

⭐ PRIMARY entry for multiplayer/多人联机/联网游戏.

CORE CONCEPT: Player A does action → sendData() → Other players receive in onDataReceived() → They see it happen.

Returns: Complete guide with code template. Includes: data sync basics, PlayerId usage, sync strategies, protocol guidelines, API-event relationships, built-in debug logger.

🔧 Built-in features:

• MultiplayerManager template (complete, production-ready)

• Debug logger system (on-screen logs, call get_debug_logger for setup)

• Error codes reference (23 error codes)

• Connection keep-alive

• Message size validation (2048 bytes)

Use when: User wants players to play together, sync game data, see each other's actions.

Perfect for ANY creative H5 game. No game-specific logic needed.

Get complete MultiplayerManager.js template (350+ lines).

Core methods:

• 📤 sendData(data) → Send your action to others

• 📥 onDataReceived(data, fromId) → Receive others' actions

• syncPosition(x, y) → Optimized position sync

• init() → Returns playerId (MUST save it!)

• matchRoom() → Match or create room

Features: Built-in rate limiting (10/sec), field compatibility, offline fallback, change detection.

Copy-paste ready. Use for ANY game type.

⚠️ CRITICAL - API-to-Event relationship table.

Shows: Which API call triggers which event, and WHO receives it.

Key relationships AI must understand:

• matchRoom() → You: get roomInfo, Others: get playerEnterRoom event

• sendCustomMessage() → You: NO event, Others: get onCustomMessage event

• updatePlayerCustomProperties() → ALL players (including you): get event

This relationship is hard to show in code template, so use this table when implementing event handlers.

Use when: Implementing multiplayer logic, debugging "why no event triggered?"

⚠️ CRITICAL - Communication protocol template to ensure consistency.

PURPOSE: Prevent AI from using different protocols for different features.

COMMON MISTAKE (AI often does this):

• Feature 1: { type: 'click', x, y }

• Feature 2: { action: 'move', pos: {x, y} } ❌ Inconsistent!

SOLUTION: Define protocol ONCE at project start, reuse for ALL features:

• All messages: { type: string, ...data }

• Consistent structure across all game features

Use when: Starting multiplayer implementation, adding new interaction types.

This is a MAJOR source of bugs - keep protocol consistent!

🟡 Get extended APIs quick reference: createRoom, getRoomList, joinRoom, kickRoomPlayer, disconnect, updatePlayerCustomStatus. ONLY use when user explicitly requests room list UI, custom room creation, friend invitation, or player kick functionality. These are OPTIONAL.

🔑 Get Player ID usage guide: how to get local player ID from connect(), check "is this me?", handle field name differences (fromPlayerId/playerId/id). Use when implementing player identification logic or debugging player-related issues.

🎮 Get synchronization strategy guide for joystick/WASD controls and click-based movement. Includes timer-based sync pattern (100ms interval) and change detection. Use when implementing position synchronization or continuous input handling.

📄 Generate MULTIPLAYER_GUIDE.md for user project root. Creates persistent reference with API rate limits, playerId rules, data structures. Enables context persistence across conversations. Use at project start.

📊 Get complete API return value structures and event callback data structures. Includes all core APIs (connect, matchRoom, sendCustomMessage, etc) and events (playerEnterRoom, onCustomMessage, etc). Use when implementing API calls to avoid guessing data structures.

🎯 One-click: Generate complete multiplayer files ready to save.

Generates:

1. js/MultiplayerManager.js (complete template with comments)

2. MULTIPLAYER_GUIDE.md (quick reference for project)

Returns: File paths and contents, ready to save.

Use when: User wants quick setup, or says "generate multiplayer code/生成多人联机代码".

🔍 Diagnose common multiplayer issues.

Use when user reports:

• Players not visible / 看不到其他玩家

• Position not syncing / 位置不同步

• Connection failed / 连接失败

• Data not received / 收不到数据

Returns: Checklist with solutions for each issue.

✅ Check multiplayer code before deployment.

Detects:

• Missing rate limiting

• Wrong field names (playerId vs id)

• Missing playerId save

• Uninitialized remote players

• Protocol inconsistency

Use when: Before finalizing code, or when debugging.

🔧 Get on-screen debug logger / 屏幕日志系统 / 调试日志工具.

CALL THIS WHEN user says:

• "添加日志工具" / "add logger" / "add debug tool"

• "屏幕日志" / "screen log" / "on-screen log"

• "看不到日志" / "can't see logs" / "无法查看控制台"

• "移动端调试" / "mobile debug" / "手机测试"

• "调试工具" / "debug tool" / "debugging"

• "显示日志在屏幕上" / "show logs on screen"

Features:

• 右下角绿色小圆点 → 点击显示日志面板

• 日志分级 (log/warn/error)，自动去重

• 支持复制日志，自动拦截 console

• 移动端友好，非程序员也能用

Returns: DebugLogger setup guide + usage. AI can copy files from /Volumes/Q/MiniGame/Mcp/Tank/DebugLogger to project.

Perfect for: H5 games, mobile testing, non-technical users.

⭐ READ THIS FIRST when user wants to integrate/接入/setup/add share功能. Returns complete step-by-step workflow for TapTap Share API. CRITICAL: Emphasizes NO SDK installation - tap is global object. Use this BEFORE making any implementation plans. Covers: 1) Server-side template creation workflow, 2) Client-side API usage (tap.showShareboard, tap.onShareMessage), 3) Template code mapping, 4) Audit status checking.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through: 1) Call list_developers_and_apps, 2) Show list to user and ASK them to choose, 3) Call select_app with user's choice. Create a new share template on TapTap server for minigame sharing feature. Auto-fetches developer_id and app_id from selected app. Returns template_code which is used in client-side tap.showShareboard() API. IMPORTANT: contents field has strict 21 UTF-8 character limit (including spaces and punctuation). Template needs audit approval (status=1) before use.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through: 1) Call list_developers_and_apps, 2) Show list to user and ASK them to choose, 3) Call select_app with user's choice. List all share templates for currently selected app. Auto-fetches developer_id and app_id. Shows template status (0=pending, 1=approved, 2=rejected, 3=audit error). IMPORTANT: When multiple templates exist, ALWAYS show the complete list to the user and explicitly ASK them which one they want to use - DO NOT automatically choose a template without user confirmation. NOTE: To modify or delete templates, please use TapTap Developer Center (https://developer.taptap.cn).

PREREQUISITE: An app MUST be selected first. Before calling this tool, ensure an app is selected by calling get_current_app_info. IMPORTANT: If the template_code is not clear, call list_share_templates first, show the list to the user, and ASK them which template they want to query - DO NOT automatically select a template. Get detailed information about a specific share template by template_code. Use this to: 1) Check audit status before using template in client, 2) Get template_code details for tap.showShareboard() API, 3) View audit reason if rejected, 4) Verify template is approved (status=1) before implementation. Returns full template info including status, contents, remark, and audit_reason. NOTE: To modify or delete templates, please use TapTap Developer Center (https://developer.taptap.cn).

[Documentation] Search Share API documentation by keyword. Use this when: 1) User asks about share API usage, 2) Need to find specific API documentation (tap.showShareboard, tap.onShareMessage, etc.), 3) Looking for code examples or integration guides. Returns relevant documentation snippets and suggestions.

Get complete Cloud Save integration workflow guide for TapTap Minigame and H5 games.

This tool provides:

• Complete workflow for saving and loading game data to/from cloud

• File system operations (writeFile, readFile) for local storage

• Cloud archive operations (create, update, delete, list)

• Error codes and troubleshooting guide

• Best practices and code examples

Use this tool when user asks about:

• How to implement cloud save in their game

• How to save/load game progress to cloud

• Cloud save architecture and workflow

• File system operations for save data

⭐ READ THIS FIRST when user mentions anything about ads/广告/advertising/ad integration/接入广告/monetization/变现/rewarded video/激励视频/interstitial/插屏/banner.

Returns the complete step-by-step ads integration workflow. Call this BEFORE making any implementation plans or writing any ad code.

CRITICAL: For ANY ads-related request, this workflow MUST be followed. The workflow will guide you through:

1. App selection check

2. Ads SDK status verification (MANDATORY before any integration)

3. Integration code generation (only when status conditions are met)

This tool has NO prerequisites - call it immediately when ads topic comes up.

[Step 2 of Ads Workflow] Check ads SDK activation status and cache ad space ID.

PREREQUISITE: An app MUST be selected first. Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected. If not, guide user through app selection process.

When to call this tool:

• First time: when no ads status exists in local cache

• Refresh: when user explicitly asks to re-check status (e.g. after activating ads in developer console)

DO NOT auto-poll - only call when user requests or when no cached status exists.

This tool queries the server, updates local cache, and returns:

• Business status: 0=未开通 | 1=已生效 | 2=账号已被封禁

• Ad space ID (space_id) - cached when status is "已生效"

• Guidance URL for activation (if needed)

CRITICAL - Dual condition for proceeding to Step 3: Both conditions MUST be met simultaneously:

1. Status must be "已生效" (status === 1)

2. space_id must be valid (non-empty string) If status is 1 but space_id is empty → server-side issue, tell user to retry later.

Status 0: Tell user they can say "重新检查广告状态" to refresh after completing activation. Status 3 (已封禁): DO NOT proceed with any integration steps. Immediately inform user.

[Step 3 of Ads Workflow] Get complete ads integration code guide with actual ad space ID.

PREREQUISITES (both MUST be met before calling):

1. check_ads_status has been called and returned status "已生效" (1)

2. A valid space_id was cached by check_ads_status

If either condition is not met, this tool will return an error with guidance.

This tool reads the cached space_id and generates:

• Complete AdManager.js utility class (full source code with YOUR ad space_id)

• Core focus: Rewarded Video ads (激励视频) - init() + onReward() + showRewardedVideo()

• Optional: Interstitial and Banner ads examples

• Code examples for all common scenarios

CRITICAL:

• NO Promise style, follows demo callback pattern

• Provides onReward() callback interface for reward logic

• DO NOT search the web - all information is provided by this tool