A
Android应用商店部署工具
myalone/hitoshura25_mcp_android_playstore_deploy
Hosted
1 Stars
1.8k 次浏览
transfer
更新于 2026-08-23
该服务暂未提供标准配置，请参考 README 手动接入
可用工具 （9 个）
该服务在 MCP 协议中暴露的工具，AI 可按需调用
analyze_android_project 1 个参数 需填 1 项
必填参数：project_path
generate_keystore 7 个参数 需填 4 项
必填参数：output_path、alias、key_password、store_password
generate_signing_config 2 个参数 需填 1 项
必填参数：project_path
setup_service_account_guide
该工具无需必填参数，直接调用即可
generate_github_workflow 12 个参数 需填 2 项
必填参数：project_path、package_name
validate_github_secrets 4 个参数 需填 3 项
必填参数：repo_owner、repo_name、github_token
create_github_secrets_guide 2 个参数 需填 1 项
必填参数：repo_url
validate_play_store_setup 2 个参数 需填 2 项
必填参数：service_account_json_path、package_name
test_deployment_workflow 6 个参数 需填 5 项
必填参数：project_path、keystore_path、store_password、key_alias、key_password
服务介绍
Android应用商店部署工具 hitoshura25_mcp_android_playstore_deploy
一个帮助开发者设置自动化Google Play商店部署流程的工具，支持项目分析、密钥生成、服务账户配置和GitHub Actions工作流生成。
null## 工具列表 Tool List
本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。
| 工具 Tool | 描述 Description |
|---|---|
| analyze_android_project | Analyze an Android project to understand its configuration and identify requirements for Play Store deployment Args: project_path: Absolute path to the Android project root directory Returns: Result from analyze_android_project |
| generate_keystore | Generate a new Android keystore file for app signing with secure parameters Args: output_path: Absolute path where the keystore will be saved alias: Key alias for the signing key key_password: Password for the signing key store_password: Password for the keystore validity_days: How many days the key should be valid key_size: Key size in bits dname: Distinguished name for the certificate Returns: Result from generate_keystore |
| generate_signing_config | Generate Gradle signing configuration with dual-source support Generates signing configuration that works seamlessly for both local development and CI/CD: - Environment variables (prioritized for CI/CD) - gradle.properties fallback (for local development) - Task-based validation (debug builds always work) Automatically generates gradle.properties.template for easy local setup. Args: project_path: Path to Android project env_var_prefix: Prefix for environment variables (default: "APP_") Example: "APP_" creates APP_SIGNING_KEY_STORE_PATH Use "" for no prefix Returns: Result including gradle_config_kotlin, gradle_properties_template, and setup instructions |
| setup_service_account_guide | Provide interactive step-by-step guide for setting up Google Play Service Account Returns: Result from setup_service_account_guide |
| generate_github_workflow | Generate a complete GitHub Actions workflow file for Play Store deployment Args: project_path: Path to Android project package_name: Android app package name track: Play Store release track (internal, alpha, beta, production) trigger_strategy: How to trigger the workflow (manual, branch, tag) branch_name: Branch name to trigger on if trigger_strategy is branch app_module_path: Path to app module relative to project root java_version: Java/JDK version to use for builds enforce_proguard: If True, ensure isMinifyEnabled=true in build.gradle.kts (default: True) mapping_file_path: Override default ProGuard mapping file path include_release_notes: Include release notes directory (default: True) release_notes_directory: Path to release notes directory (default: distribution/whatsnew) env_var_prefix: Prefix for environment variables (default: "APP_") Example: "APP_" creates APP_SIGNING_KEY_STORE_PATH Use "" for no prefix Returns: Result from generate_github_workflow |
| validate_github_secrets | Validate that required GitHub Secrets are configured (checks existence only) Args: repo_owner: GitHub repository owner username or organization repo_name: GitHub repository name github_token: GitHub Personal Access Token with repo scope required_secrets: List of secret names to check for Returns: Result from validate_github_secrets |
| create_github_secrets_guide | Generate a comprehensive guide for creating all required GitHub Secrets Args: repo_url: GitHub repository URL keystore_path: Optional path to keystore for encoding instructions Returns: Result from create_github_secrets_guide |
| validate_play_store_setup | Validate that Play Store app and API access are properly configured using service account Args: service_account_json_path: Path to service account JSON file package_name: Android app package name to validate Returns: Result from validate_play_store_setup |
| test_deployment_workflow | Test the deployment workflow locally without uploading to Play Store Args: project_path: Path to Android project keystore_path: Path to keystore file store_password: Keystore password key_alias: Key alias key_password: Key password dry_run: If true, skip actual Play Store upload Returns: Result from test_deployment_workflow |
检查服务 ## Inspector
工具在线测试： https://mcp.xiaobenyang.com/inspector/1777419073082371
Online Tool test https://mcp.xiaobenyang.com/inspector/1777419073082371
服务配置 MCP Server Config
如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?
访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY
Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.
SSE
{
"mcpServers": {
"Android应用商店部署工具": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "sse",
"url": "https://mcp.xiaobenyang.com/1777419073082371/sse"
}
}
}
STREAMABLE HTTP
{
"mcpServers": {
"Android应用商店部署工具": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "streamable_http",
"url": "https://mcp.xiaobenyang.com/1777419073082371/mcp"
}
}
}
STDIO
{
"mcpServers": {
"Android应用商店部署工具": {
"command": "npx",
"args": [
"-y",
"xiaobenyang-mcp"
],
"env": {
"XBY_APIKEY": "<YOUR_XBY_APIKEY>",
"mcpId": "1777419073082371",
},
"transport": "stdio"
}
}
}
