Skip to main content
AGI Agentic Phone MCP is a three-piece system. Understanding who does what makes every other page in these docs click into place.

​
The three pieces

Your AI client

Any MCP client. It decides what to do, calls tools, and interprets results. It never touches the phone directly.

AGI cloud MCP server

https://api.agi.tech/v1/mcp. Authenticates you, queues tasks, dispatches them to your devices, and relays progress back.

AGI Android app

The agent itself. It executes tasks on-device using Android’s accessibility APIs - real apps, real UI - and streams progress back.

​
The asynchronous execution model

Phone tasks take seconds to minutes - far too long for a blocking API call. So execution is split:
  1. Your client calls phone_run_task. The server queues the task and returns a task_id immediately.
  2. The phone picks the task up and executes it, streaming progress back.
  3. Your client waits on phone_task_monitor, which returns as soon as something actionable happens - completion, a pause, or a request for user input. If nothing happens within its timeout it returns monitor_timed_out: true, and you simply call it again.
This start/monitor split is the single most important pattern in the API. The full loop, including every outcome, is covered in Task lifecycle.

​
Why on-device execution matters

The agent operates the phone the way a person does - through the screen, via Android’s accessibility APIs:
  • Real apps, not APIs. Anything installable is automatable; no per-app integration is required.
  • Visible execution. Every action happens on the phone’s screen while you watch. There is no hidden browser or virtual machine.
  • Native trust boundaries. App logins, payment sheets, and permission dialogs stay on the device, where the user handles them - the agent hands control back rather than working around them.

​
Where MCP fits

The Model Context Protocol is the connector standard that makes the client side universal. The server speaks MCP 2024-11-05 over Streamable HTTP or SSE, with OAuth 2.1 or API-key auth. Any compliant client gets the same tools by calling tools/list - nothing is hardcoded per client. Setup for each client lives on the Connect your AI client page; protocol and auth details are in the API reference.

​
Next

Devices & Sessions

How work is organized across phones and workflows

Task Lifecycle

The state machine every task moves through