> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lusor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an AI app

> Give Claude, ChatGPT, Grok, Hermes, Pi, Codex or Cursor your phones through the Lusor MCP server.

Lusor runs a remote [MCP](https://modelcontextprotocol.io) server at:

```
https://mcp.lusor.ai/mcp
```

Add that URL to an AI app that supports custom MCP connectors, sign in with your Lusor account, and the app can run agents on your phones and control them directly. You don't need to wait for an app directory listing. Adding Lusor by URL works today in every app below.

> [card] [Claude](https://docs.lusor.ai/connect/claude.md)
>
> Free, Pro, Max, Team and Enterprise

> [card] [ChatGPT](https://docs.lusor.ai/connect/chatgpt.md)
>
> Business, Enterprise and Edu workspaces

> [card] [Grok](https://docs.lusor.ai/connect/grok.md)
>
> Every plan, including Free

> [card] [Hermes](https://docs.lusor.ai/connect/hermes.md)
>
> Hermes Agent, any install

> [card] [Pi](https://docs.lusor.ai/connect/pi.md)
>
> The Pi coding agent

> [card] [Codex](https://docs.lusor.ai/connect/codex.md)
>
> The Codex CLI

> [card] [Cursor](https://docs.lusor.ai/connect/cursor.md)
>
> The Cursor editor and agent

## What the app gets

The server exposes two tools:

| Tool | What it does |
| - | - |
| `search` | Reads the Lusor API reference to find the right operation and its parameters. |
| `execute` | Calls the Lusor API: list phones, start an agent run, read its status and output, tap, type, take a screenshot. |

The app writes a short piece of code that `execute` runs. It reaches only documented `/v1` operations of the [Lusor API](https://docs.lusor.ai/api-reference/introduction.md), and every call is checked by the API, so the app can do no more than an API key can.

## Signing in

There are two ways to authenticate. Both give the same access.

* **Sign in with Lusor (OAuth).** The app shows a Lusor sign-in when you connect. You choose the organization to connect, and the app never sees a key. This is the default in every app below.
* **API key.** For apps that let you set request headers, send `Authorization: Bearer lusor_...` with a key from your workspace's **API keys** page in the [Lusor app](https://app.lusor.ai). A key is tied to one workspace. See [Authentication](https://docs.lusor.ai/authentication.md).

With OAuth, requests use your organization's default workspace. An app can choose another workspace by sending the `X-Lusor-Workspace` header, and a workspace id in an API path always takes precedence.

> [!NOTE]
>
> An MCP connection can do what an API key can and nothing more. Billing, API keys, members, the vault, adding or removing phones, static IPs, workspace creation and routines answer `403 forbidden_for_mcp_oauth`. Manage those in the Lusor app.

## App directories

Lusor is being submitted to Claude's Connectors Directory and ChatGPT's app directory. When a listing is approved, the app's page here links to it for one-click setup. Until then, and on plans where a directory isn't available, use the add-by-URL steps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.