LibreAI / AI Agents / lamda
// agents · firerpa/lamda

lamda

FIRERPA / LAMDA — full-stack Android device control: remote desktop, automation, MITM, Frida and MCP.

★ 8.6k stars⑂ 1.2k forksMITupdated 2026-09
▦ visual — this project's README ships no embeddable screenshot,
so here's a placeholder. The guide below is complete regardless.
// project facts

Project facts

lamda is an open-source ai agents project by firerpa (firerpa/lamda on GitHub). It has 8,553 GitHub stars and 1,155 forks, is released under the MIT license, and was last updated on GitHub on 27 September 2026.

Repository
firerpa/lamda
GitHub stars
8,553
Forks
1,155
License
MIT
Last updated on GitHub
27 September 2026
Category
AI Agents
Listing
Full install guide
Official site
Official site
// how it works

How it works

  1. Clarify your goal

    Decide your use case — device farm, automation, traffic analysis or reverse engineering — and prepare the Android devices (root is optional) you will enrol.

  2. Get the project

    Clone firerpa/lamda from GitHub (or use the install path in the run steps below) and skim its README for the parts relevant to your goal.

  3. Install and configure

    Deploy the FIRERPA server on each device per the project documentation, then install the Python client library on your PC to orchestrate them.

  4. Run your first task

    Open the browser-based remote desktop for one device, run a simple UI automation action through the client, and confirm the fleet view sees the device.

// features

Why people love it

Remote desktop and streaming

Browser-based remote control with MJPEG and H.264 (up to 60fps), WebRTC with STUN/TURN, multi-user access, clipboard, audio and file browsing over a single port.

Full UI automation

Selector-based automation with child/sibling chaining, UI Watchers for popups, OCR and on-device image matching, multi-touch recording and replay — plus virtual displays that run automation without disturbing the main screen.

One-click MITM capture

Automatic CA install and proxy setup, per-app capture, live request/response editing and QUIC downgrade, all API-driven alongside mitmproxy-compatible tooling.

Built-in Frida

Frida is bundled with hiding patches, persistent scripts with hot reload, and RPC mapped to Python methods and HTTP JSON-RPC — no separate frida-server.

Networking toolkit

HTTP/HTTPS/SOCKS5/Shadowsocks per-app proxying, a device HTTP bridge, built-in OpenVPN and frp clients, and mDNS fleet discovery.

Fleet and agent ready

Distributed multi-device management with 160+ APIs, plus MCP/Agent support so AI agents can drive devices through the same platform.

Advertisement
// run it

Run it yourself

  1. Clone the repository

    Get the source from the official GitHub repository for lamda.

    git clone https://github.com/firerpa/lamda.git
    cd lamda
  2. Get the platform

    Clone the repository and follow the deployment documentation for installing the FIRERPA server on your Android device.

    git clone https://github.com/firerpa/lamda.git
    cd lamda  # then follow the deployment docs — see README
  3. Connect from Python

    Install and use the Python client library per the docs to connect to a device and run your first automation call.

    # Install the Python client per the project docs, connect to the device, then call the device API — see README
// use cases

What you can build

Advertisement
// faq

Questions, answered

Who maintains lamda?

firerpa, through the firerpa/lamda repository, with the product site at device-farm.com.

Is lamda free to use?

Yes — the project is open source under the MIT license as recorded for this listing. You can use, modify and distribute it under the MIT terms.

Does lamda need a paid API key?

The platform itself is open source and needs no paid key; AI/MCP agent features use whatever model you connect, with your own credentials.

How does FIRERPA compare to stitching together Appium, mitmproxy and frida-server?

That stack works but means separate tools, configs and failure modes. FIRERPA positions itself as one server and one API covering automation, capture, Frida and fleet ops — built specifically for multi-device, long-running production use.

How do I get started with lamda?

Clone the repository (or use the documented installer), follow the install and configure steps on this page, and run the smallest real task first — open the browser-based remote desktop for one device, run a simple UI automation action through the client, and confirm the fleet view sees the device.

// keep exploring

Similar tools

AI Agents

google_workspace_mcp

Control Gmail, Calendar, Docs, Sheets, Drive and more from AI — a full Google Workspace MCP server.

★ 3.3k starsMIT
View guide →
AI Agents

agent-device

Mobile app automation and verification built for AI coding agents — CLI, MCP server, and Node API

★ 4.9k starsMIT
View guide →
AI Agents

mcphub

Self-hosted MCP gateway and control plane — connect, control and operate all your MCP servers from one place

★ 2.5k starsApache-2.0
View guide →
Agents

fulling

AI full-stack engineer agent built on Next.js, Claude, and Kubernetes.

★ 2.4k starsMIT
View guide →
AI Agents

ha-mcp

The unofficial Home Assistant MCP server — control and automate your smart home from any AI assistant.

★ 5.0k starsMIT
View guide →
AI Agents

playwright-mcp

Microsoft's Playwright-powered MCP server for browser automation.

★ 37.9k starsApache-2.0
View guide →
// alternatives

Alternatives in AI Agents

The most-starred other AI Agents projects in the LibreAI catalogue — the realistic shortlist if lamda is not the right fit.

Get lamda

Free and open — grab the source, star the repo, and start creating.