05 / 05

Stop being the mousefor your AI.

You read the screen to it. You click for it. You paste between it and your apps. Connect one address and the assistant you already use runs your phone, drives your browser, and builds, runs and schedules your Melaya agents itself.

One address.Your AI stops being blind.

https://api.melaya.org/mcp

MCP is a vendor-neutral standard, the same idea as a USB port. Melaya runs one. Paste it into the assistant you already use and it gets 74 tools across your phone, your browser and your agents, filtered to the permissions you granted.

One endpointno install, no SDK, works in the assistant you already pay for
74 toolsphone, browser, agents, connected services, your account records
8 scopesgranted one at a time, and the tool list is filtered to what you approved
You attachthe phone, the tab, the apps are yours to pick. The model never chooses

Pick your assistant. Paste. Done.

One endpoint, nothing to install. Most assistants take a single line.

Your assistant
Run this command

Add --scope user to make it available in every project instead of just this one.

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

Melaya asks which permissions to grant. Tick what you want, leave the rest dark, then just ask.

Create a free account

On Claude Code or Codex the CLI is faster than any settings screen.

You get sent to a Melaya screen once, where you pick which permissions to grant. Then you are done.

Right now,
you are the API.

Your assistant is smart and blindfolded. You are its eyes, its hands, and its clipboard.

01

You screenshot so it can see a screen it could read itself.

02

You copy and paste between the assistant and the app that does the work.

03

You do the clicking because it can only tell you where to click.

Screens were built for eyes and fingers. Your assistant has neither.

Give your assistant hands.

Three surfaces, one connection.

Your phone

Reads the Android screen, opens apps, taps, types, swipes.

No integrationApp playbooksIds, not pixels

Your browser

You attach the tab. It reads, acts, then verifies.

Portals with no APINetwork and consolePerformance report

Your agents

Hand off the jobs that outlast a conversation.

Validate firstSchedule and runYour machine

Here is what you actually type.

No syntax to learn. Just ask.

Go through my unread Instagram DMs on my phone. Summarize who wants what. Do not reply to anyone.

melayaEnter to send

Open the supplier portal tab I just attached. Pull every invoice from August into a table with number, date and amount.

melayaEnter to send

This product page feels slow. Load it in the attached tab and tell me the three things costing me the most, with the file and the number.

melayaEnter to send

Every Monday at 8am, run the agent that checks last week's runs and tells me which ones failed and why.

melayaEnter to send

Narrow the leash. Never widen it.

Tick what you would grant. The tool list your assistant receives is cut to match, before it ever sees it.

74of 74
tools reach your assistant
Try it

Everything granted. Most people grant far less.

  • The agent can narrow this during a run. It can never widen it.
  • Publishing and paying always stage an approval you see first.
  • Trading, admin and credential values are absent, and tests keep them absent.

Questions people actually ask

The short version: one address, permissions you pick, and an agent that can narrow its own access but never widen it.

What is MCP, in one sentence?

A vendor-neutral standard that lets an AI assistant use outside tools, so one endpoint works in every assistant that speaks it.

Do I need to install anything?

Not for phone or account access. Paste the address and approve the connection. Browser control needs the Melaya extension in your own browser, and autonomous agents need the Melaya runner on your own machine.

Which assistants work?

Any MCP client. Claude Code, Claude, ChatGPT, Cursor, Codex, Le Chat, VS Code, Windsurf, Zed, Cline, Goose, Gemini CLI and Qwen Code all take the same endpoint.

Is my password shared?

No. Authentication is OAuth 2.1 with PKCE. You approve permissions on a Melaya screen and the assistant receives a scoped token. Provider and connector credentials are resolved server-side and never reach the assistant.

Can the agent give itself more access?

No. It can narrow its allow-list during a run and never widen it. Granting happens in the Melaya app or on your phone, on a screen that can ask you properly.

Does it work on iPhone?

Phone control is Android only, version 8 or newer. There is no iOS build, because the accessibility access this needs does not exist there.

What does it cost?

A Melaya account is free to create. The MCP endpoint is included. Autonomous agent runs use your own model subscription on your own machine.

Give your assistant hands.

One address. One approval screen. Grant the scopes you want and leave the rest dark. Then stop being the mouse.

OAuth 2.1 with PKCE. Your password is never shared. The tool list is filtered to the scopes you approved.
Join the community
// Cookies
Melaya uses a small set of first-party cookies that are strictly necessary to authenticate you, maintain your session, and protect the platform from abuse. We do not use advertising cookies, cross-site trackers, or third-party analytics by default. The full cookie list is in our Privacy Policy.