K

kimi-android-studio-plugin

mnshkv/android-studio · v1.0.0 · Kimi Plugins

by mnshkvScan grade: Good

Android development from Kimi Code: adb, emulators and devices, screenshots, UI automation and Gradle builds over MCP — the Android counterpart of the Xcode plugin

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is kimi-android-studio-plugin a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • Kimi Code
  • MCP
  • 1 skill
  • 1 MCP server

Before you install

Sign-in
Not declared
Declared access
Not declared
License
MIT

Check before relying on it

  • Some security checks did not finish: Cisco skill scan. See the evidence
  • 1 medium finding from the scan. See the evidence
  • The publisher has not verified ownership on HOL.

What is kimi-android-studio-plugin?

kimi-android-studio-plugin is a published kimi plugins plugin for AI coding agents that works with Kimi Code and MCP, developed by mnshkv and distributed through the HOL AI plugin registry. Android development from Kimi Code: adb, emulators and devices, screenshots, UI automation and Gradle builds over MCP — the Android counterpart of the Xcode plugin.

Canonical slug
mnshkv/android-studio
Version
v1.0.0 · updated Nov 11, 2026

Registry snapshot

Owner verification
Not verified
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
Yes
1 bundled skillRead, copy or download each SKILL.mdOpen skills

Trust and security

Trust & reputation

84

HOL Trust Score

Per-metric points (0–100 each) combined via a weighted average into the overall score.

Installability
100/100
Maintenance
65/100
MCP server setup
100/100
Plugin Security
85/100
Provenance
70/100
Publisher Quality
75/100

Provenance

Plugin root
.
Source repo
https://github.com/mnshkv/kimi-android-studio-plugin
Source commit
c781e9a36f28…
Publisher verified
No
Owner verified
Not owner verified
Agent Plugins 1.0
Not detected

Continuous scanner CI detected

No action is required. This plugin receives the full trust score.

README badge not detected

Plugin owners can add the HOL badge to the repository README from Guard Plugins. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Needs review
Security result
85
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
B · Good
Version
3.24.2
codex:hol-plugin-scanner-4gQrnC / cisco-skill-scanner: failedcodex:hol-plugin-scanner-4gQrnC / cisco-mcp-scanner: skipped

[codex:.] Manifest Validation

21/31

9 checks

[codex:.] Security

16/16

9 checks

[codex:.] Operational Security

N/A

5 checks · not applicable

[codex:.] Best Practices

9/12

5 checks

[codex:.] Marketplace

N/A

3 checks · not applicable

[codex:.] Skill Security

5/5

4 checks

[codex:.] Code Quality

10/10

2 checks

[kimi:.] Kimi Plugin

40/45

10 checks

Published advisories

None matched in GitHub security advisories, checked . This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

mediumsecurityKIMI_MCP_ARG_PATH_INVALID

MCP server "android" local argument "./bin/android-mcp" must exist inside the plugin and not be a symlink.

Use a regular in-plugin path for local MCP arguments.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_AUTHOR

The manifest is missing the documented recommended field "author".

Add "author" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_HOMEPAGE

The manifest is missing the documented recommended field "homepage".

Add "homepage" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CATEGORY

The interface object is missing a valid "category" value.

Add a valid "category" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CAPABILITIES

The interface object is missing a valid "capabilities" value.

Add a valid "capabilities" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_WEBSITEURL

The interface field "websiteURL" must use HTTPS or point to a safe in-repo asset.

Update "websiteURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs
  1. 1

    Clone the repository

    shell
  2. 2

    Register the server in your MCP client

    Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.

  3. 3

    Verify the server

    Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W46, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "$schema": "https://kimi.com/schemas/kimi.plugin.schema.json",
  "name": "android-studio",
  "version": "1.0.0",
  "description": "Android development from Kimi Code: drive emulators and devices (boot, install, launch, screenshots, UI hierarchy, taps, swipes, logcat), run gradle builds and tests, and — with the bundled JetBrains MCP Server plugin enabled — control Android Studio itself over MCP.",
  "keywords": [
    "android",
    "android-studio",
    "adb",
    "emulator",
    "gradle",
    "kotlin",
    "compose",
    "logcat",
    "apk",
    "mcp"
  ],
  "author": "mnshkv",
  "license": "MIT",
  "skills": "./",
  "interface": {
    "displayName": "Android Studio",
    "developerName": "mnshkv",
    "shortDescription": "Emulators, devices, adb, gradle builds — and Android Studio IDE tools over MCP",
    "longDescription": "Two layers of Android integration for Kimi Code:\n\n1. android-tools MCP server (bundled, stdio, zero dependencies): 19 tools over adb/emulator/gradle — list devices and AVDs, boot emulators and wait for them, install/launch/uninstall APKs, take screenshots, dump the UI hierarchy (uiautomator) to find element bounds, synthesize taps/swipes/text/key events, read logcat, run device shell commands, and run gradle tasks (build, test, assembleDebug, ...) through the project's gradlew.\n\n2. Optional Android Studio IDE tools: install the official JetBrains MCP Server plugin into Android Studio (scripts/install-jetbrains-mcp-plugin.sh) and enable the MCP server in Settings → Tools → MCP Server; then add http://127.0.0.1:63342 as an MCP server in Kimi Code to get editor file access, run configurations, and other IDE tools.\n\nPrerequisites: Android SDK with platform-tools (adb). For IDE tools: Android Studio 2025.2+.",
    "hostKind": "local"
  },
  "mcpServers": "./.registry/mcp.json",
  "platforms": [
    "macos",
    "windows",
    "linux"
  ],
  "repository": "https://github.com/mnshkv/kimi-android-studio-plugin",
  "holManifestOrigin": "repository",
  "registryIndexVersion": 9
}

Marketplace source

Repo URL
https://github.com/mnshkv/kimi-android-studio-plugin
Marketplace path
Unknown
Source path
.
Install policy
Unspecified

Skills

1 SKILL.md file ship with this plugin. Preview, copy, or download each one, then install them with the Skills CLI.

Share
skills-cli
  • android-studio-mcp

    skills/android-studio-mcp/SKILL.md

    Use the android-tools MCP server (19 tools over adb, emulator, and gradle) to run builds, drive emulators and devices, inspect UI, and read logs from Kimi Code. Covers prerequisites, tool groups, and typical workflows; also how to add Android Studio IDE tools via the JetBrains MCP Server plugin.

    SKILL.md content is not in this snapshot. Open the raw file to copy it from the source repository.

File inventory

.codex-plugin/plugin.json

plugin-manifest

1,888 bytes

fa3004c66c08632d…

.registry/mcp.json

mcp-config

88 bytes

10d87f772a1a51fb…

kimi.plugin.json

file

2,024 bytes

06c4579e3f020f3f…

LICENSE

file

1,696 bytes

2ee6fa9eab1cd3ab…

README.md

file

3,255 bytes

07a16b9c40f95a04…

SECURITY.md

file

1,070 bytes

03adbb5c3a42ba13…

skills/android-studio-mcp/SKILL.md

skill

3,601 bytes

169877c1eb08df0d…

kimi-android-studio-plugin — Frequently asked questions

What is kimi-android-studio-plugin?
kimi-android-studio-plugin is an AI plugin in the HOL registry. Android development from Kimi Code: adb, emulators and devices, screenshots, UI automation and Gradle builds over MCP — the Android counterpart of the Xcode plugin.
How do I install kimi-android-studio-plugin?
Install kimi-android-studio-plugin in your harness: MCP — git clone https://github.com/mnshkv/kimi-android-studio-plugin; Any agent — npx [email protected] add mnshkv/kimi-android-studio-plugin. Full step-by-step guidance is on the HOL plugin page.
How do I install kimi-android-studio-plugin in MCP?
To install kimi-android-studio-plugin in MCP, start with git clone https://github.com/mnshkv/kimi-android-studio-plugin. The complete step-by-step install guide for MCP is on the HOL plugin page.
How do I install kimi-android-studio-plugin in Kimi Code?
To install kimi-android-studio-plugin in Kimi Code, start with /plugins install https://github.com/mnshkv/kimi-android-studio-plugin. The complete step-by-step install guide for Kimi Code is on the HOL plugin page.
How is the Trust Score for kimi-android-studio-plugin computed?
kimi-android-studio-plugin has a HOL Trust Score of 84 out of 100. The score is a weighted sum of six components from a static scan of the source, capped for high-severity findings and adjusted by two disclosed policies. Memberships and payments are not inputs, and a scan is not a safety guarantee. Full breakdown: https://hol.org/registry/plugins/mnshkv%2Fandroid-studio/trust
Who publishes kimi-android-studio-plugin?
kimi-android-studio-plugin is published by mnshkv and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W46. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.

Reviews and similar plugins