Log inSubmit server
Melaya logo

Melaya

Connects AI assistants to an Android phone, browser tabs, and Melaya account workflows through a remote MCP endpoint.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Melaya

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "melaya": {
      "command": "npx",
      "args": [
        "-y",
        "@melaya/runner@1.1.60"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @melaya/runner@1.1.60

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

Melaya MCP server connects AI assistants to an Android phone, supported browser tabs, and Melaya account workflows through a remote MCP endpoint. It reads Android accessibility data and performs actions such as opening apps, tapping, typing, swiping, scrolling, and taking screenshots. Browser control works through a Melaya extension for Chrome or Edge, while OAuth 2.1 with PKCE limits access to permissions the user approves. Reach for it when an agent must operate mobile apps or browser sessions without separate per-app APIs.

Use cases

  • Operate an Android app through natural-language instructions
  • Review unread messages on a paired phone
  • Automate tasks in an attached Chrome or Edge tab
  • Diagnose browser console, network, and performance issues
  • Create and monitor recurring Melaya pipelines

Key features

  • Android screen reading through accessibility data
  • Phone taps, typing, swipes, scrolling, and screenshots
  • Chrome and Edge tab automation
  • Browser network and console inspection
  • Pipeline creation, validation, scheduling, and monitoring
  • OAuth 2.1 with PKCE and scoped permissions

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @melaya/runner@1.1.60 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.8kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Melaya works

What the Melaya MCP server does

The Melaya MCP server lets an AI assistant work with a paired Android phone, a connected browser tab, and other capabilities in a Melaya account. Phone interaction uses Android’s accessibility tree to read the visible interface, then carries out actions such as opening apps, tapping controls, entering text, scrolling, swiping, and capturing screenshots. This approach is intended for apps that do not provide a separate agent integration.

Browser automation follows a similar read, act, and verify pattern. The Melaya extension supports Chrome and Edge, and the user attaches the tab that the agent should control. Multiple conversations or workflows can use separate tabs, with an agent identifier passed into later browser calls. The browser features also expose network activity, console output, and a performance diagnosis; captured credential values are redacted before they reach the model.

How the Melaya MCP server works

Melaya provides a hosted MCP endpoint at https://api.melaya.org/mcp, so clients connect over HTTP rather than installing a local SDK or package. The assistant sends MCP requests to the endpoint, and Melaya performs approved operations against the paired phone, attached browser tab, or account resources.

Authentication uses OAuth 2.1 with PKCE. During connection, the user selects permissions on a Melaya consent page and the assistant receives a scoped token.

The repository also provides a Melaya skill for assistants that need procedural guidance. It describes setup checks, service connections, pipeline validation, triggers, approvals, and result handling. The skill is separate from the MCP tools and can be installed through client-specific instructions.

Setup and configuration

Add the hosted endpoint to an MCP client using that client’s HTTP-server configuration. Claude Code, Codex CLI, Cursor, and VS Code each have documented commands or configuration examples in the repository. Windsurf, Zed, Cline, Gemini CLI, and other MCP clients can use the same server URL in their MCP configuration format.

Claude clients, ChatGPT, and Le Chat can add the endpoint through their custom connector settings where supported. After connecting, complete the OAuth consent flow and grant the permissions needed for the intended work. A phone must be paired with the Melaya account for mobile operations, and a browser tab must be attached before browser actions can target it.

Tools and capabilities

The Melaya MCP server covers the following documented areas:

  • Read an Android phone’s screen through accessibility data.
  • Open apps and interact with visible controls.
  • Tap, type, scroll, swipe, and capture screenshots.
  • Drive an attached Chrome or Edge tab.
  • Inspect browser network activity and console output.
  • Produce a ranked browser performance diagnosis.
  • Create projects, list templates, instantiate templates, and author pipelines.
  • Validate, schedule, and monitor pipeline runs.
  • Work with triggers, approvals, devices, and handover features described by the Melaya skill.

Common-app navigation playbooks are also included for supported phone workflows.

Limitations and notes

Mobile control depends on a paired Android phone and the accessibility information available from its current interface. Browser control is limited to a tab the user attaches through the Melaya extension; the agent does not choose a tab automatically. The endpoint requires network access and OAuth authorization, and available actions depend on the permissions granted during consent.

The skill is optional. It can improve procedural guidance, but connecting the MCP endpoint supplies the tools themselves. The project is licensed under Apache-2.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Melaya

Melaya is an MCP server that connects AI assistants to a paired Android phone, attached Chrome or Edge browser tabs, and Melaya account workflows. Its main tools read screens, open apps, tap, type, swipe, scroll, capture screenshots, automate browser sessions, inspect diagnostics, and manage pipelines through a hosted endpoint.

You do not need to install a local package; add `https://api.melaya.org/mcp` as an HTTP MCP server in your client. Then complete the OAuth 2.1 consent flow, pair a phone for mobile actions, or attach a browser tab for browser automation.

Yes, Melaya works with Cursor through its MCP configuration. Add the hosted URL in `~/.cursor/mcp.json` for all projects or `.cursor/mcp.json` for one project, then authorize the requested permissions.

Yes, Melaya can control an attached Chrome or Edge tab through its browser extension. The user selects and attaches the tab, and later browser calls use the returned agent identifier so separate sessions do not target the wrong tab.

No API key is described as required; the server uses OAuth 2.1 with PKCE. You approve permissions on a Melaya consent page, and the assistant receives a scoped token without receiving your password.

Related MCP servers

All in OS Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMelaya AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/melaya?style=directory)](https://allmcps.com/mcp/melaya)
HTML Embed
<a href="https://allmcps.com/mcp/melaya"><img src="https://allmcps.com/api/badge/melaya?style=directory" alt="Melaya on AllMCPs" /></a>