How to integrate Phone Harness MCP with Hermes

Connect Hermes 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

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Phone Harness account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Phone Harness with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,500+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Phone Harness with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Phone Harness

Ask your agent to connect to Phone Harness, or simply request any Phone Harness-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Phone Harness connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Phone Harness or request any Phone Harness-related task. It will prompt you to authenticate and authorize access.

5. Done!

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.

Way Forward

With Phone Harness connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

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. Hermes 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