アイリ Android

Created By
LemonNekoGHa year ago
Allow LLM to use Android Device
Overview

What is Airi Android?

Airi Android is a MCP server that allows LLM (Large Language Model) to interact with Android devices. It is a child project of the main Airi project.

How to use Airi Android?

To use Airi Android, you can set it up using Docker by configuring the MCP server with the provided JSON configuration. You also need to install the necessary development environment and connect your Android device.

Key features of Airi Android?

  • Enables LLM to control and interact with Android devices.
  • Supports Docker for easy deployment.
  • Provides a development environment setup guide.

Use cases of Airi Android?

  1. Automating tasks on Android devices using LLM.
  2. Developing applications that require interaction with Android hardware.
  3. Testing and debugging Android applications in a controlled environment.

FAQ from Airi Android?

  • What is the purpose of Airi Android?

Airi Android allows LLM to utilize Android devices for various applications and tasks.

  • Is Airi Android easy to set up?

Yes! Airi Android provides a detailed setup guide for both Docker and development environments.

  • What programming language is used in Airi Android?

Airi Android is developed using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
LemonNekoGH
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago