lolkda/dsh-dexsql-mcp

Connects DexSQL to DSH through the official MCP client plugin, with the DexSQL binaries for six platforms shipped inside the npm package.

Once connected, the tools appear as mcpdexsql*: open_dataset, list_datasets and close_dataset, then list_tables, describe_table and query, plus decode, get_manifest, get_manifest_components, list_resource_files, read_resource and query_resources. The README's typical first call is open_dataset on an absolute APK or DEX path and then query against the returned dataset_id. Shipping the binaries inside the tarball means the Android reverse-engineering side works on a clean machine with no separate toolchain.

Files & Data ★ 1
View on GitHub ↗

Install

dsh plugin --profile web add @lolkda/dsh-dexsql-mcp

The install the README describes as the only one needed; the scoped package resolves on the public registry and its registry metadata points back at this repository. The published package contains the bundle configuration, a small launcher and the DexSQL binaries, so no global dexsql on PATH and no runtime download are required; the git checkout is configuration-only and marked private.

Compatibility

Requires DSH 0.2.1-rc.2 or later plus @deepseek-ai/dsh-mcp-client, since the bundle registers the server through that Host plugin. The default row in cordis.patch.yml starts the bundled launcher with a 300000 ms tool-call timeout and failOnStartupError: true, which makes a broken binary visible instead of silently dropping the tools. Overriding that row lets you point at an external dexsql instead of the bundled one.

Details

Alternatives

omdsh-dev/dsh-tool-csv · omdsh-dev/dsh-tool-schema · omdsh-dev/dsh-tool-markdown

More plugins in Files & Data

Browse more in Files & Data

Guides for Files & Data plugins