Filesystem Android

You can run a Claude MCP server that securely exposes Android project files to AI assistants. It validates Android projects by checking for Gradle configuration, lets you browse Kotlin, Kotlin Script, TOML, and AndroidManifest.xml files by directory, and provides read access with appropriate filtering while preventing access to sensitive folders.

How to use

Connect your MCP client to the Android source code server to start browsing Android projects. The server validates project directories to ensure they contain essential Gradle configuration, then lists and reads files in a secure, read-only manner. You can navigate directories to find Kotlin files, Kotlin Script files, TOML files, and AndroidManifest.xml, and you can open individual files or groups of files for inspection. Access to directories such as .gradle, .git, and build folders is blocked to protect sensitive information.

How to install

Prerequisites you need before starting: curl, a compatible shell, Python, and the UV toolchain. You will also need network access to install dependencies and run the MCP server.

Install the UV tool if it is not already present. Run the following command in your terminal to fetch and install UV:

curl -LsSf https://astral.sh/uv/install.sh | sh

Set up a Python virtual environment with UV and install the necessary dependencies from the lockfile. Run these commands in sequence:

uv venv
uv pip install -r uv.lock

Configure the MCP server for Android source code by using the following MCP configuration snippet. This defines a local (stdio) server that runs UV with a specific command and arguments to start the Android filesystem reader:

{
  "mcpServers": {
    "android_source": {
      "type": "stdio",
      "command": "/path/to/uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "mcp",
        "run",
        "./filesystem_android/main.py"
      ],
      "env": []
    }
  }
}

Additional notes

Security and access controls are designed to keep sensitive Android project materials safe. Only files that are validated as part of an Android project will be accessible. Directories such as .gradle, .git, and build outputs are blocked to prevent leakage of internal metadata or artifacts.

Configuration and security considerations

The server checks for essential Gradle configuration files to determine if a directory is a valid Android project before exposing its contents. This helps ensure that only legitimate Android project workspaces are browsed. If you need to adjust which directories are readable, you should modify the server’s validation logic and the file-filtering rules accordingly, while maintaining safeguards against exposing sensitive folders.

Available tools

Project Validation

Ensures a directory is a valid Android project by checking for Gradle configuration files.

File Browsing

Lists Kotlin, Kotlin Script (KTS), TOML files, and AndroidManifest.xml grouped by directory to help you locate source and config files.

File Reading

Provides secure access to read individual or multiple files with appropriate filtering to prevent exposure of sensitive data.

Security

Prevents access to sensitive directories like .gradle, .git and build folders to protect project integrity.