Phone Harness MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Phone Harness MCP or direct API to create Android sessions, monitor phone state, manage session lifecycles, and run ADB commands through natural language.

Phone Harness logoPhone Harness
Api Key

Phone Harness is a cloud platform for running managed Android phone sessions. It simplifies Android lifecycle control, session observation, and secure ADB access.

21 Tools

Try Phone Harness now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Phone Harness
Try asking
TOOLS

Supported Tools

Every Phone Harness action and event your agent gets out of the box.

Create API Key

Create an account-wide API bearer key that can manage API keys.

Create Session

Start a temporary or saved Android emulator session and return its admitted session data plus the internally generated idempotency key.

Enable ADB

Enable or re-enable ADB access for a ready Android session and return its current connection endpoint and sensitive unlock code.

End Session

Request that a Phone Harness session end and billing closure be recorded.

Get Account

Get the connected account's identity, balance, Android profile choices, active-session capacity, and whether a new session can be started.

Get ADB

Get the current ADB state for an Android session.

Get API Health

Check public Phone Harness API-process liveness only.

Get Owner Viewer

Create a secret, short-lived capability for interactive owner control of a ready session.

Get Recent History

Return up to 100 finished sessions ordered by creation time descending.

Get Session

Get one session's current lifecycle state, deadline, screen geometry, and ADB details.

Get Snapshot

Download the latest still image from a ready Phone Harness session as a file.

Create View-Only Link

Create a short-lived view-only link for an intended person to watch a live session.

List API Keys

List metadata for the connected account's API keys, including hashes, labels, hints, creation times, and revocation times.

List History

Return one cursor-paginated page of finished-session history in newest-first order, with a next cursor for complete traversal.

List Sessions

List all active account sessions, including provisioning, terminal-error, closing, and cleanup-pending entries.

Recover Create Request

Read the durable receipt for an idempotent session create to resolve an ambiguous create result or confirm asynchronous release cleanup.

Reset ADB Code

Rotate the ADB unlock code for an Android session, invalidate the previous code, and close all existing ADB connections.

Reset Device

Irreversibly erase and reprovision an assigned iPhone, deleting its apps, accounts, and data.

Reset Profile

Irreversibly delete the saved Android profile's apps, logins, and data.

Revoke ADB

Revoke ADB access for an Android session.

Revoke API Key

Idempotently revoke an API key by its hash.

SETUP GUIDE

Connect Phone Harness MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["phone_harness"],
  mcp: true,
});
Create a session scoped to Phone Harness and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Create a cloud Android phone session and return its session ID",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Phone Harness request
SETUP GUIDE

Connect Phone Harness API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["phone_harness"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Phone Harness
3

Run Phone Harness tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Create a cloud Android phone session and return its session ID" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Phone Harness tool calls through the session, and print the final answer

Why Use Composio?

AI Native Phone Harness Integration

  • Supports both Phone Harness MCP and direct API integrations
  • Structured, LLM-friendly schemas for reliable Android session and ADB tool execution
  • Rich coverage for creating, observing, managing, and querying Phone Harness sessions

Managed Auth

  • Securely stores your Phone Harness API key without hard-coding it in agent prompts or application code
  • Central place to manage, scope, and revoke Phone Harness access
  • Per-user and per-environment credentials help keep Android sessions isolated

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve reliability over time
  • Clear inputs and outputs help agents create sessions, inspect phone state, and run ADB commands correctly
  • Comprehensive execution logs show what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC helps control which agents and users can access Phone Harness
  • Scoped, least-privilege access to Android sessions and ADB operations
  • Full audit trail of agent actions to support review and compliance

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

Yes, Phone Harness requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Phone Harness connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Phone Harness account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Phone Harness actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Phone Harness at any time.

When you connect a Phone Harness account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Phone Harness as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Phone Harness. If Phone Harness lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Phone Harness at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Phone Harness connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Phone Harness rejects the old key. Create a new key in Phone Harness and reconnect the account from the Composio dashboard or by asking your agent to reconnect Phone Harness. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Phone Harness use. Paid plans add higher limits and team features. Your Phone Harness plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Phone Harness accounts).

With Composio, you connect Phone Harness once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Phone Harness.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Phone Harness tool your agent needs.Free to start.

Start building