AkaPhone

ai.akaphonePublished by akaphone.aiOfficial publisherv1.1.3Updated Oct 29, 2026

Cloud Android phones for AI agents: tap, type, screenshot, install APKs, run plain-English tasks.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

AkaPhone gives an AI assistant cloud-hosted Android phones to control: tapping, typing, screenshots, APK installs and plain-English tasks.

What you can do
  • Control cloud Android phones: tap, type and take screenshots on a remote device.
  • Install APKs onto the phone.
  • Run plain-English tasks that the service carries out on the device.
When to use it
Useful when an assistant needs to operate Android apps or a mobile UI that has no API, such as testing an app, walking through a mobile flow, or automating repetitive phone tasks in the cloud.
Requirements
A remote MCP endpoint at app.akaphone.ai over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
The assistant can act on a real cloud phone: taps, typing and APK installs change device state, and installed apps may be untrusted. OAuth grants access to an AkaPhone account, and device activity and task content are handled by that third-party service. Check what the account or plan costs before use.

Installation

In SourceWeft

  1. Open AkaPhone in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.akaphone%2Fakaphone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "akaphone": {
      "type": "http",
      "url": "https://app.akaphone.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.3LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.