A general file reader will happily hand an assistant a build directory full of generated code, which is both noise and context you paid for. Restricting to source, Gradle catalogs and the manifest — grouped by directory — means the first read gives a usable map of the project rather than a listing. The exclusions are structural rather than configurable, which is the trade: less to set up, less to adjust.
A narrow filesystem reader scoped to Android codebases. It confirms a directory really is an Android project by checking for gradle files before it will read anything, and it refuses the directories that hold build output and secrets.
- Project validation: a directory is only accepted if the gradle configuration files that mark a real Android project are present
- File browsing that lists Kotlin, KTS and TOML files along with AndroidManifest.xml, grouped by directory
- File reading, one file or several at a time, with the same filtering applied
- Refusal to descend into .gradle, .git and build folders
Python 3.10+ and uv. The client launches it with `uv run --with mcp[cli] mcp run` pointed at the project's main entry point; the uv path must be absolute in most clients. Published on PyPI as filesystem-android, version 0.1.0.