Melaya

Melaya MCP Server

Let an AI assistant use your Android phone, your browser, and the rest of your Melaya account.

Also listed on mcp.so · mcpserver.dev · mcpmarket · cursor.directory · Glama · Product Hunt · AlternativeTo · SaaSHub · AI Agents Directory · AgentLocker · LaunchKiwi

Documentation · Melaya · Device Control · MCP Server

Melaya pairs a phone to your account and gives an agent the same view of it a person has: it reads the screen through Android's accessibility tree, then taps, types, swipes, and moves between apps. No per-app integration, no vendor API. If you can use the app, so can the agent.

This is a remote Model Context Protocol server. MCP is a vendor-neutral standard, so one endpoint works everywhere:

https://api.melaya.org/mcp

Nothing to install, no SDK required.

Connect

Claude Code

claude mcp add --transport http melaya https://api.melaya.org/mcp

Codex CLI

codex mcp add melaya --url https://api.melaya.org/mcp

Direct HTTP needs experimental_use_rmcp_client = true in ~/.codex/config.toml.

Cursor

~/.cursor/mcp.json, or .cursor/mcp.json for one project:

{ "mcpServers": { "melaya": { "url": "https://api.melaya.org/mcp" } } }

Claude

claude.ai, Desktop and mobile: Settings → Connectors → Add custom connector, paste https://api.melaya.org/mcp

ChatGPT

Settings → Connectors → Developer mode, paste the same endpoint

Le Chat

Connectors → Add custom MCP connector

VS Code

code --add-mcp '{"name":"melaya","type":"http","url":"https://api.melaya.org/mcp"}'

Everything else

Windsurf, Zed, Cline, Goose, Lovable, Gemini CLI, Qwen Code and any other MCP client take the same block, in whichever file that client uses for MCP servers:

{ "mcpServers": { "melaya": { "url": "https://api.melaya.org/mcp" } } }

Authentication is OAuth 2.1 with PKCE. You choose which permissions to grant on a Melaya consent page; the assistant receives a scoped token. Your password is never shared.

Then just ask:

Connect my phone and go through my unread Instagram DMs.

---

Give your AI the Melaya skill

This server gives your assistant the tools. The [Melaya skill](https://github.com/melaya-labs/melaya-mcp/tree/main/skills/melaya) gives it the method: which tool to call first, how to connect services, build and validate a pipeline on a real run, set triggers and approvals, and read results. Install both and your assistant gets real work right the first time instead of guessing.

Any assistant (ChatGPT, Gemini, Cursor, …): paste this line.

Install the Melaya skill from https://github.com/melaya-labs/melaya-mcp/tree/main/skills/melaya and use it whenever I ask you to work with Melaya.

Claude Code: the Melaya plugin from this repo already bundles it, next to melaya-setup. Installing the plugin is enough. To use the skill on its own, copy it into your skills folder, then restart. It loads on its own when you mention Melaya.

git clone --depth 1 https://github.com/melaya-labs/melaya-mcp /tmp/melaya-mcp && cp -r /tmp/melaya-mcp/skills/melaya ~/.claude/skills/

Claude.ai and Claude Desktop: download skills/melaya as a .zip and upload it under Settings → Capabilities → Skills. Anywhere else, add SKILL.md as a project instruction or rules file.

Starts right Opens every session with melaya_setup_status and closes each gap it reports before doing anything else. Stays safe Never asks for a key in chat, never decides an approval for you, confirms before anything is sent or deleted.

Builds pipelines that run Reads the config before changing it, previews before saving, and judges a run by its real output, not its status. Loads only what it needs One short router plus eleven modules: quickstart, pipelines, agentic systems, data, triggers and approvals, devices, handover.

What it can do

Operate your phone

Read the screen, open apps, tap, type, scroll, swipe, screenshot. You watch it work, and one control stops everything.

Melaya ships navigation playbooks for common apps, so the agent arrives knowing where things are instead of exploring blindly.

Operate a browser

The same read-act-verify loop on a desktop site, through the Melaya extension on Chrome or Edge. You attach the tab; the model never picks one. Several conversations, pipelines and the extension panel can work in the same browser at once, each in its own tab (up to 8): attach returns an agent id that the conversation passes on every browser call, and a tab another agent is using is never touched.

It can also debug the page it is on: network activity, console output, and a performance diagnosis that ranks causes with the file and the number behind each, rather than handing over a raw panel. Credential values are redacted at capture, before anything reaches the model.

Build and run agents

Create a project for the work (one per client pilot, say), list the template library and instantiate a validated template, or author a pipeline from scratch, validate it before saving, schedule it, and watch it run. Hand a long or recurring job to an autonomous agent on your own machine, on your own model subscription, that carries on after the conversation ends.

Read, and act through, your connected services

Mail, documents, your ERP. Read-only by default, structurally: without the separate write permission the write path is blocked in two independent places, so a write stays blocked even if Melaya's own tool catalog is out of date.

Grant melaya:connectors.write as well and the assistant can act for you there too: send an email, create or update a record or a file. That includes tools that move money or trade (payments, refunds, purchases, transfers, ad-spend changes, orders): the consent screen says so, discovery labels them, and your assistant should confirm the exact action and amount with you first. Every write runs at once, with no second prompt, and is audit-logged. LinkedIn session tools are never reachable over MCP, at any permission.

Manage projects

Create a project, rename it or edit its description, and delete it once it is empty. Delete is a dry run until confirmed, only the project's creator can do it, and a project that still holds pipelines, run history or other members is refused. Plan limits apply exactly as in the app.

Find out what happened

Runs, transcripts, tool traces, failure diagnosis, cost, and what your agents have learned across runs.

---

What it cannot do

Enforced by the device or by the Melaya server, not by instructions, so no prompt and no agent instruction can move them.

It only touches what you allow-list

Apps on the phone, origins in the browser. The agent can hand access back, narrowing the list or clearing it, but only you widen it: phone apps on your phone or in the Melaya app, and browser sites on the Melaya Browser Control page or by asking your assistant to add one (it then calls melaya_browser_allow_sites with that site; you can also ask it for every site). The skills tell it never to widen access on its own or because of something it read.

That asymmetry is deliberate. The agent reads text off your screen, and text can be written by anyone: a message, a comment, a web page. A boundary it could widen in response to what it reads would not be a boundary.

Payments on your phone always ask you

Direct phone control from your assistant runs in safe mode: publishing and paying stage an approval card, and you see the exact text before anything goes out. Phone agents and phone pipelines your assistant starts or saves keep the payment card in every mode: autonomous is stored and run as payments_only from here, which lets an agent publish without a card you asked it to skip, but still stops before every purchase or payment. Only you can set a fully unattended phone mod