# How to connect Phone Harness to Claude ```json { "title": "How to connect Phone Harness to Claude", "toolkit": "Phone Harness", "toolkit_slug": "phone_harness", "framework": "Claude Cowork", "framework_slug": "claude-cowork", "url": "https://composio.dev/toolkits/phone_harness/framework/claude-cowork", "markdown_url": "https://composio.dev/toolkits/phone_harness/framework/claude-cowork.md", "updated_at": "2026-11-06T05:31:55.873Z" } ``` ## 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 - [ChatGPT](https://composio.dev/toolkits/phone_harness/framework/chatgpt) - [Hermes](https://composio.dev/toolkits/phone_harness/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/phone_harness/framework/atomic-agent) ## Connect Phone Harness to Claude Cowork ### 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](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp) ### Add manually In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top. Click Add custom connector and paste in the Composio MCP server URL: ```bash https://connect.composio.dev/mcp ``` ## What is the Phone Harness MCP server, 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `PHONE_HARNESS_CREATE_API_KEY` | Create API Key | Create an account-wide API bearer key that can manage API keys. The raw key is shown only once; store it securely and never log it. | | `PHONE_HARNESS_CREATE_SESSION` | Create Session | Start a temporary or saved Android emulator session and return its admitted session data plus the internally generated idempotency key. If the initial POST has an ambiguous transport failure, this action recovers or safely replays that same keyed request once. A provisioning result is not ready; poll PHONE_HARNESS_GET_SESSION until state is ready or terminal error. | | `PHONE_HARNESS_ENABLE_ADB` | Enable ADB | Enable or re-enable ADB access for a ready Android session and return its current connection endpoint and sensitive unlock code. Repeated calls are idempotent. | | `PHONE_HARNESS_END_SESSION` | End Session | Request that a Phone Harness session end and billing closure be recorded. A cleanup_pending result is asynchronous and continues to consume capacity; use the durable create receipt to confirm cleanup_complete. Repeating cleanup after the session is gone can return session_not_found; that outcome does not prove release or cleanup, even on a repeated call. | | `PHONE_HARNESS_GET_ACCOUNT` | Get Account | Get the connected account's identity, balance, Android profile choices, active-session capacity, and whether a new session can be started. | | `PHONE_HARNESS_GET_ADB` | Get ADB | Get the current ADB state for an Android session. Returns exactly a disabled result or the enabled connection endpoint and sensitive unlock credential. | | `PHONE_HARNESS_GET_HEALTH` | Get API Health | Check public Phone Harness API-process liveness only. This does not certify phone availability, credits, capacity, video, or successful provisioning. | | `PHONE_HARNESS_GET_OWNER_VIEWER` | Get Owner Viewer | Create a secret, short-lived capability for interactive owner control of a ready session. Embedding is restricted to the configured Phone Harness dashboard origin, not arbitrary third-party origins. Reconnecting does not extend the phone deadline. Return it only for secure handoff to the intended account owner; never log, persist, or publish it. | | `PHONE_HARNESS_GET_RECENT_HISTORY` | Get Recent History | Return up to 100 finished sessions ordered by creation time descending. Use LIST_HISTORY instead when complete cursor-based traversal is needed. | | `PHONE_HARNESS_GET_SESSION` | Get Session | Get one session's current lifecycle state, deadline, screen geometry, and ADB details. Use it to poll provisioning; state=error is a terminal startup failure, not success. | | `PHONE_HARNESS_GET_SNAPSHOT` | Get Snapshot | Download the latest still image from a ready Phone Harness session as a file. The image is PNG or JPEG. A no-frame-yet response is retryable after the session is ready and has rendered a frame. | | `PHONE_HARNESS_GET_VIEWER` | Create View-Only Link | Create a short-lived view-only link for an intended person to watch a live session. Return the link for secure handoff; it grants no interactive owner control and must not be logged or published. | | `PHONE_HARNESS_LIST_API_KEYS` | List API Keys | List metadata for the connected account's API keys, including hashes, labels, hints, creation times, and revocation times. This action never returns raw bearer keys. | | `PHONE_HARNESS_LIST_HISTORY` | List History | Return one cursor-paginated page of finished-session history in newest-first order, with a next cursor for complete traversal. | | `PHONE_HARNESS_LIST_SESSIONS` | List Sessions | List all active account sessions, including provisioning, terminal-error, closing, and cleanup-pending entries. | | `PHONE_HARNESS_RECOVER_CREATE_REQUEST` | Recover Create Request | Read the durable receipt for an idempotent session create to resolve an ambiguous create result or confirm asynchronous release cleanup. | | `PHONE_HARNESS_RESET_ADB_CODE` | Reset ADB Code | Rotate the ADB unlock code for an Android session, invalidate the previous code, and close all existing ADB connections. Returns sensitive replacement connection details that must be used for subsequent connections. | | `PHONE_HARNESS_RESET_DEVICE` | Reset Device | Irreversibly erase and reprovision an assigned iPhone, deleting its apps, accounts, and data. The reset takes a few minutes; poll PHONE_HARNESS_GET_ACCOUNT until the device state is available before starting it again. Phone Harness refuses the reset while a session holds the device. | | `PHONE_HARNESS_RESET_PROFILE` | Reset Profile | Irreversibly delete the saved Android profile's apps, logins, and data. The next session using its profile ID starts with a fresh phone. Phone Harness refuses the reset while a live session holds the profile phone. | | `PHONE_HARNESS_REVOKE_ADB` | Revoke ADB | Revoke ADB access for an Android session. This changes only ADB access: the phone session remains active and session billing continues unaffected. | | `PHONE_HARNESS_REVOKE_API_KEY` | Revoke API Key | Idempotently revoke an API key by its hash. Identifier existence is not proven by a successful response, and active phone sessions are unaffected. Do not revoke the key used by the current connection if continued Phone Harness access is needed. | ## Supported Triggers None listed. ## 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. ## Creating MCP Server - Stand-alone vs Composio SDK The Phone Harness MCP server connects Claude Web, Desktop, and Cowork to your Phone Harness account through Composio. Once connected, Claude can use the available Phone Harness tools and triggers to complete tasks on your behalf. ## Complete Code None listed. ## How to build Phone Harness MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/phone_harness/framework/chatgpt) - [Hermes](https://composio.dev/toolkits/phone_harness/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/phone_harness/framework/atomic-agent) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anakin](https://composio.dev/toolkits/anakin_io) - Anakin is a web automation platform offering scraping, crawling, search, and browser automation. Use it to extract structured data, automate site tasks, and monitor web changes reliably. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Authyo](https://composio.dev/toolkits/authyo) - Authyo is a REST API service for passwordless authentication, OTP verification, session management, and transactional notifications. Use it to add secure login flows and user verification without building auth infrastructure from scratch. - [AWS Marketplace MCP](https://composio.dev/toolkits/aws_marketplace_mcp) - AWS Marketplace MCP provides MCP access to AWS Marketplace's cloud software, data, and services catalog. Use it to discover, compare, and evaluate 30K+ AWS Marketplace listings faster. - [Azure Monitor Activity Log](https://composio.dev/toolkits/azure_monitor_activity_log) - Azure Monitor Activity Log is Azure's service that records management and control-plane events for a subscription. Use it to audit changes, troubleshoot issues, and track resource operations across your Azure resources. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Phone Harness MCP? 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. ### Can I use Tool Router MCP with Claude Cowork? 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. ### Can I manage the permissions and scopes for Phone Harness while using Tool Router? 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. ### How safe is my data with Composio Tool Router? 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)