How to connect Phone Harness to Claude

Connect Claude Web, Desktop and Cowork to Phone Harness MCP. Create a cloud android phone session, list active phone harness phone sessions, and more using natural language, with authentication handled for you.

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

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Phone Harness account to Claude via Composio Connect, enabling it to create a cloud Android phone session, list active Phone Harness phone sessions, run ADB command on Android session, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Phone Harness with

Connecting Phone Harness to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Phone Harness account

Back in Claude, ask it to connect to Phone Harness or give it any Phone Harness-related task.

For example, ask Claude to:

  • "Create a cloud Android phone session"
  • "List active Phone Harness phone sessions"
  • "Run ADB command on Android session"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Phone Harness account is ready to use.

What is the Phone Harness Claude Connector, and what's possible with it?

The Phone Harness MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Phone Harness account. It provides structured and secure access so your agent can perform Phone Harness operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Phone Harness?

The connector can show as connected, but Claude must use it in each Phone Harness conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Phone Harness again.

2. Why does Claude show an MCP server error before Phone Harness connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Phone Harness.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Phone Harness.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Phone Harness authorization link not work?

The Composio connector is one server. Your Phone Harness account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Phone Harness connection.
  • Composio creates a fresh Phone Harness authorization link.
  • Open that link in your browser and finish the Phone Harness sign-in.

4. Why do Phone Harness actions fail after they worked before?

The Phone Harness connection can expire or lose permission.

  • Ask Claude to inspect the Phone Harness connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Phone Harness account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Phone Harness.
  • If the action still fails with a permission error, check that the connected account has that permission in Phone Harness itself.

5. How do I switch to a different Phone Harness account?

Claude can manage the Phone Harness connection for you.

  • Ask Claude to disconnect or delete the current Phone Harness account.
  • Ask Claude to connect Phone Harness again.
  • Open the new Composio authorization link for Phone Harness.
  • Sign in with the other Phone Harness account in the browser.
  • After the account connects, ask Claude to retry the Phone Harness task.

6. Why is my Phone Harness connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Phone Harness connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Phone Harness tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Phone Harness.
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.

FAQ

Frequently asked questions

With a standalone Phone Harness MCP server, the agents and LLMs can only access a fixed set of Phone Harness tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Phone Harness and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Phone Harness tools.

Yes, absolutely. You can configure which Phone Harness scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Phone Harness data and credentials are handled as safely as possible.

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