Conversation
Owner
|
Sorry, but at the moment we are not planning to integrate MCP or skills. ASC is currently provided as a minimal suite containing only core functionality, available for all third parties to use freely. Adding MCP could restrict the freedom of other projects that integrate DroidASC into their pipelines. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Droid ASC can now be used directly by MCP clients such as Codex over stdio, exposing class decompilation, class listing, manifest decoding, and cross-DEX reference search without launching a separate CLI process for each request.
The server returns structured results with timing, counts, and truncation metadata, validates paths and query parameters, marks all tools read-only, and caches repeated class/manifest queries using file metadata. This also adds the
droidasc-mcpconsole entry point, MCP SDK dependency, Codex registration instructions, and MCP protocol tests.Validation:
python tests/run_tests.py --require-decompiler— 69 tests passed.python -m compileall -q droidasc tests/test_mcp_server.pyandgit diff --checkpassed.droidasc-mcpwithpython -m pip install -e .and verified stdio initialization/tool discovery with the official MCP client.list_classescall against a generated DEX fixture.codex mcp add/get; the registration was removed afterward. A full model-drivencodex execattempt launched the server but did not complete because that session stalled during unrelated existing MCP/model initialization, so no end-to-end Codex model success is claimed.