News ZennoDroid 2.6.1.0 — Public HTTP API and MCP server suite • Ability to set GPU Vendor/Renderer values and noise

[ZennoLab Team]

Full changelog 2.6.1.0


Added:

+ ZennoDroid and ProjectMaker now have a public HTTP API and a set of MCP servers. The product can now be controlled externally — from your own scripts and applications or directly from an AI assistant (Claude Code, Cursor, or any other MCP client): read and edit projects, queue tasks for execution, and control the browser.

• Public REST API (PublicAPI) — over 100 operations under a single contract: working with a project in ProjectMaker (action tree, variables, lists, tables, static data), managing tasks and execution sessions in ZennoDroid, and device information (element tree, installed apps). The contract is described in OpenAPI — you can generate a client for any language from the specification.
• API keys with flexible permissions. Keys are issued in ProjectMaker (Settings → API Keys); for each key, a set of permissions (scopes) and a maximum operation level (tier) is defined — from strict read-only to full control. The key is shown only once at creation; all API authorization errors are returned in a structured format, indicating exactly which permissions were missing.
• MCP servers for AI assistants. Three servers — ProjectMaker (project editing), Android (device information), ZennoDroid (tasks and sessions) — are published as ready-to-use self-contained builds: download, enter your API key, and connect to your LLM client. The assistant's permissions are determined by your key. Servers accept connections only from the local machine.

The product's built-in AI chat runs on this same infrastructure — the same permission model and API, with no hidden privileged channels.

Public servers are in the repository https://github.com/ZennoLab/zennoposter-mcp
Documentation (integrator guide, interactive OpenAPI contract, operations reference, error codes, and versioning policy): https://zennolab.github.io/zennoposter-mcp/ — MCP server releases are also on GitHub.

Important: the ports used in ZennoDroid are shifted +10 from those used in ZennoPoster.

+ Added project save, load, and close tools for ProjectMaker.

• save_project and open_project return a file freshness indicator: fileHash (SHA-256 of the .zp content on disk, calculated after writing), fileSizeBytes, lastWriteTimeUtc. Reopening the same file yields an identical hash — this lets you verify that the file on disk is exactly what you expect.
• get_project_info is supplemented with the hasUnsavedChanges flag and the same fields; the hash is calculated only when there are no unsaved changes.
• close_project closes the open project. By default, a project with unsaved changes will not close: a 409 failed_precondition is returned to prevent silent data loss. To close and discard changes, you must explicitly pass discardUnsavedChanges: true.

+ Improved project structure reading tools.

• get_project_structure returns a graph: nodes (type, label, start point, switch, disabled state, membership in an error branch, groupId/actionId) and edges (OnSuccess/OnError/Default/Case-N, including implicit transitions). The response is three-level — group overview, group slice, or full graph — to avoid bloating the response on large templates.
• find_path(from, to) — the shortest route between two blocks.
• get_action_connections(actionId) — all incoming and outgoing connections and branches for a specific block.

+ Renamed the Appium application package name. The standard name io.appium.uiautomator2.server, by which applications could detect automation, has been changed. The application's standard port, which could also be used for detection, has been changed.

+ Added the Visual_Studio_Project action. Allows using projects created in the Microsoft Visual Studio 2022/2026 environment within a ZennoDroid project.

+ Added the ability to set GPU Vendor/Renderer values and noise in MEmu and LDPlayer emulators so that emulators are not detected as the same device. Values are generated in the profile (GpuVendor, GpuRender).

+ Memu emulator (Android 12) startup speed increased. Fixed the operation of the "Fix build.prop errors" setting.

+ LDPlayer 14 emulator startup speed increased. Fixed various issues on first launch.

+ Added the setting Disable animation.

+ Added GpuVendor and GpuRender fields to the Profile (generated automatically). Values can be used in the GPU Settings action.

+ Increased proxy setup speed in Clash mode. Clash updated to 1.19.31.


Fixed:

* Detailed error output when attempting to launch an app without a start activity.

* Fixed issues with Microsoft Visual Studio integration:

• Fixed an issue where the device screen could "escape" to another window (when two or more Visual Studio projects were open simultaneously).
• Fixed a "No format header found" error when using the slnx format.
• Fixed an issue where the device screen returned to ProjectMaker shifted to a corner (without Dock).
• Fixed an issue where reconnecting to a solution could take 30 seconds.
• Fixed an RPC_E_CALL_REJECTED error when creating a solution.
• Fixed the absence of *.slnx format selection in the solution selection menu.
• Fixed a bug where the startup window appeared when creating a new solution.
• Fixed a solution creation error: "Object reference not set to an instance of an object."

* Fixed GPU spoofing in LDPlayer 9.

* Fixed a bug where the profile was not applied after changing the emulator type in ProjectMaker.

* Fixed conversion to C# for the "Wait for user action" action.
Fixed closing the "Wait for user action" window via MCP.ZennoPoster: POST /sessions/{id}/complete.

* Fixed a ZennoDroid crash when capturing an image in h264 mode.

* Fixed a critical error when launching ProjectMaker ("Object reference not set to an instance of an object").

* Fixed exit via BadEnd when interrupting an instance's execution.


Where to download?

ZennoDroid 2.6.1.0 is already available in your personal account!
You’ll also be prompted to update when launching ProjectMaker.

How to report bugs?

Please report all bugs using our form, along with a detailed description and a reproduction script. This will allow us to quickly diagnose and fix the issue.