[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_117":118},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_56":-5,"_57":49,"_58":59,"_60":61,"_62":63,"_64":65,"_66":67,"_68":47,"_69":70,"_71":72,"_73":74,"_75":76,"_77":78,"_79":-5,"_80":-5,"_81":-5,"_82":49,"_83":-5,"_84":59,"_85":86,"_87":88,"_89":90,"_91":92,"_93":94,"_95":96},"apiUrl","https://odel.app/api","creator","melaya-labs","moduleId","melaya-mcp","@melaya-labs/melaya-mcp","displayName","Melaya","tagline","Create and run any AI agents systems from 6k+ tools. Give your AI hands access to your Android.","iconKey","https://avatars.githubusercontent.com/u/294689857?v=4","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://api.melaya.org/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1788070135000,"updatedAt",1788497548000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=org.melaya%2Fmelaya","sourceVerified",false,"sourceMissingSince","importedAt","upstreamStars",0,"upstreamUpdatedAt",1788494876000,"detectedTransport","streamable-http","detectedAuthType","oauth","probeStatus","ok","lastProbedAt","githubRepoUrl","https://github.com/melaya-labs/melaya-mcp","githubRepoFullName","melaya-labs/melaya-mcp","releaseId","ext-melaya-labs-melaya-mcp","version","1.1.4","descriptionMarkdown","

\n\n# Melaya MCP Server\n\n**Let an AI assistant use your Android phone, your browser, and the rest of your Melaya account.**\n\n[![MCP Registry](https://img.shields.io/badge/MCP_Registry-org.melaya%2Fmelaya-6E56CF)](https://registry.modelcontextprotocol.io)\n[![smithery badge](https://smithery.ai/badge/info-h530/melaya)](https://smithery.ai/servers/info-h530/melaya)\n[![Listed on mcpservers.org](https://mcpservers.org/badge.svg)](https://mcpservers.org/servers/melaya-labs/melaya-mcp)\n[![Glama MCP server](https://glama.ai/mcp/servers/@melaya-labs/melaya-mcp/badge)](https://glama.ai/mcp/servers/@melaya-labs/melaya-mcp)\n[![Tools](https://img.shields.io/badge/tools-77_across_8_domains-22D3EE)](#what-it-can-do)\n[![Auth](https://img.shields.io/badge/auth-OAuth_2.1_%2B_PKCE-10B981)](#permissions)\n[![License](https://img.shields.io/badge/license-Apache--2.0-blue)](./LICENSE)\n\n[Documentation](https://github.com/melaya-labs/melaya/blob/main/docs/mcp.md) · [Melaya](https://melaya.org) · [Device Control](https://melaya.org/en/product/agentic-device-control) · [MCP Server](https://melaya.org/en/product/mcp)\n\n

\n\n

\n $\"Melaya:$ \n

\n\nMelaya 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.**\n\nThis is a remote [Model Context Protocol](https://modelcontextprotocol.io) server. MCP is a vendor-neutral standard, so one endpoint works everywhere:\n\n```\nhttps://api.melaya.org/mcp\n```\n\nNothing to install, no SDK required.\n\n## Connect\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Claude Code	\n\n```bash\nclaude mcp add --transport http melaya https://api.melaya.org/mcp\n```\n\n
Codex CLI	\n\n```bash\ncodex mcp add melaya --url https://api.melaya.org/mcp\n```\n\nDirect HTTP needs `experimental_use_rmcp_client = true` in `~/.codex/config.toml`.\n\n
Cursor	\n\n`~/.cursor/mcp.json`, or `.cursor/mcp.json` for one project:\n\n```json\n{ \"mcpServers\": { \"melaya\": { \"url\": \"https://api.melaya.org/mcp\" } } }\n```\n\n
Claude	\n\nclaude.ai, Desktop and mobile: Settings → Connectors → Add custom connector, paste `https://api.melaya.org/mcp`\n\n
ChatGPT	\n\nSettings → Connectors → Developer mode, paste the same endpoint\n\n
Le Chat	\n\nConnectors → Add custom MCP connector\n\n
VS Code	\n\n```bash\ncode --add-mcp '{\"name\":\"melaya\",\"type\":\"http\",\"url\":\"https://api.melaya.org/mcp\"}'\n```\n\n
Everything else	\n\nWindsurf, 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:\n\n```json\n{ \"mcpServers\": { \"melaya\": { \"url\": \"https://api.melaya.org/mcp\" } } }\n```\n\n

\n\nAuthentication 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.\n\nThen just ask:\n\n> Connect my phone and go through my unread Instagram DMs.\n\n---\n\n## What it can do\n\n### Operate your phone\n\nRead the screen, open apps, tap, type, scroll, swipe, screenshot. You watch it work, and one control stops everything.\n\n

\n $\"The$ \n

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

\n $\"App$ \n

\n\n### Operate a browser\n\nThe 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.**\n\n

\n $\"A$ \n

\n\nIt 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.\n\n### Build and run agents\n\nList 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.\n\n

\n $\"The$ \n

\n\n### Read your connected services\n\nMail, documents, your ERP. **Read-only, structurally**: 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.\n\n### Find out what happened\n\nRuns, transcripts, tool traces, failure diagnosis, cost, and what your agents have learned across runs.\n\n---\n\n## What it cannot do\n\nEnforced on the device itself, not on the server, so no prompt and no agent instruction can move them.\n\n### It only touches what you allow-list\n\nApps on the phone, origins in the browser. The agent can hand access back, narrowing the list or clearing it, but **only you can grant it**.\n\n

\n $\"The$ \n

\n\nThat 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.\n\n### Publishing and paying always ask you\n\nYou see the exact text before it goes out, and approvals reach you even when the phone is locked.\n\n

\n $\"An$ \n \n $\"An$ \n

\n\n### There is a STOP control\n\nOn the phone overlay and in the Melaya app. It halts everything immediately, across every agent and every connected assistant.\n\n### Approvals are listed here, never decided here\n\nThe gate exists to put a human between an agent and a consequential action, and the caller here is a model reading untrusted content. You approve in the Melaya app or on your phone.\n\nPassword fields are excluded from screen reads.\n\nAlso deliberately absent, and enforced by tests rather than by convention: **trading** (it writes against live exchange keys), **administration** (no honest consent sentence exists for it), and **credential values of any kind**.\n\n---\n\n## Permissions\n\nEight scopes, one per domain. You grant them individually.\n\n| Scope | What it allows |\n|---|---|\n| `melaya:read` | Your workspace: pipelines, runs, traces, evaluations, pending approvals |\n| `melaya:platform` | Your account and plan: tier, usage against limits, subscription |\n| `melaya:runner` | Set up and check the Melaya runner on your computer |\n| `melaya:phone` | Operate your paired Android phone, inside apps you allow-listed |\n| `melaya:browser` | Operate a connected browser, on sites you allowed |\n| `melaya:pipelines` | Create, edit, schedule, run and cancel agent pipelines |\n| `melaya:connectors` | Read data from connected services. Read only |\n| `melaya:team` | Read project membership, and invite people you name |\n\nThe tool list your assistant receives is filtered to what you granted, so connecting for phone control alone shows **23 tools rather than all 77**. If a capability seems missing, you declined it; reconnect and approve it.\n\n> [!NOTE]\n> **If you also use the Melaya SDK**, \"connectors\" means something different there. In the SDK it is project credential storage. Here, `melaya:connectors` is reading data from services you already connected. This surface cannot store, read or delete a credential.\n\n## Requirements\n\n- A Melaya account — free at [melaya.org](https://melaya.org)\n- An Android phone (Android 8 or newer) for phone control. There is no iOS build.\n- The Melaya extension on Chrome or Edge for browser control\n- For autonomous agents: Node 18+, Python 3.11+, and a signed-in CLI on the machine hosting the runner\n\n## Privacy\n\nScreen and page content read during a run goes to Melaya and to whichever model you selected, for the duration of that run. The [privacy policy](https://melaya.org/en/legal/privacy) covers collection, retention and deletion.\n\nOne credential does cross the boundary, and it is worth naming: if you set up the optional local runner, the command you are given contains a runner token. It is valid for 7 days, revocable in settings or with `melaya_runner_revoke`, and unavoidable because the runner starts from a command line. On a hosted assistant that command appears in your conversation history. Nothing else does; provider and connector credentials are resolved server-side and never reach the assistant.\n\nDisconnecting in Melaya settings immediately revokes the connection's ability to renew itself. A token it already holds keeps working until it expires, at most one hour.\n\n## What's in this repo\n\n| Path | Purpose |\n|---|---|\n| `server.json` | Manifest for the [official MCP Registry](https://registry.modelcontextprotocol.io) |\n| `.mcp.json` | Remote server declaration |\n| `.claude-plugin/`, `skills/`, `commands/` | Claude Code plugin packaging — one distribution of the same server |\n\nThe server itself runs as part of the Melaya platform; this repo is its public manifest, packaging and documentation.\n\n## The rest of the platform\n\nThis server is one surface onto Melaya. Its tool domains map to the products\nbehind them, so if a scope is useful the product page explains what it reaches:\n\n| Product | What it is | `melaya:` scope |\n|---|---|---|\n| [Melaya Agents Builder](https://melaya.org/en/product/agentic-framework) | Visual builder for agent pipelines, 6,633+ tools and 111+ subagents | `pipelines` |\n| [Melaya Assistant](https://melaya.org/en/product/assistant) | The governed operating layer over those agents | `platform` |\n| [Device Control](https://melaya.org/en/product/agentic-device-control) | Android phone control through the accessibility tree | `phone` |\n| [Melaya Browser Control](https://melaya.org/en/product/agentic-browser-control) | Origin-scoped control of a paired browser | `browser` |\n| [Melaya MCP Server](https://melaya.org/en/product/mcp) | This server | all of the above |\n\nThe [browser extension](https://melaya.org/en/blog/melaya-browser-extension) is\nwhat Browser Control talks to, and ships for Chrome, Edge and Firefox.\n\nPricing starts at a $0 Sandbox tier for evaluating the platform during open\nbeta: [see plans](https://melaya.org/en/pricing).\n\n## Links\n\n- [Full documentation](https://github.com/melaya-labs/melaya/blob/main/docs/mcp.md)\n- [Melaya SDKs](https://github.com/melaya-labs/melaya) — nine languages\n- [Product overview](https://melaya.org/en/product/mcp) · [All products](https://melaya.org)\n- [Privacy Policy](https://melaya.org/en/legal/privacy) · [Terms](https://melaya.org/en/legal/terms)\n- [Support](mailto:info@melaya.org)\n\n## License\n\nApache-2.0, matching the [Melaya SDKs](https://github.com/melaya-labs/melaya).\n\nIt covers what is in this repository — the registry manifest, the plugin packaging, the skills and this documentation. It is not a licence to the Melaya service itself: using the hosted server at `api.melaya.org` needs a Melaya account and is governed by the [Terms](https://melaya.org/en/legal/terms).\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays","iconType","image","upstream",{"_103":104,"_105":106,"_107":-5,"_108":109,"_110":111,"_112":113},"requiredSecrets",[],"tags",[99,100,101,102],"assets",[],"stats",{"_97":59,"_98":59},"ratingAvg","reviewCount","ai-agents","android-automation","browser-automation","gemini-cli-extension","topics",[99,100,101,102,114,115,116],"license","Apache-2.0","language","registryName","org.melaya/melaya","homepage","https://melaya.org/en/product/mcp","packages",[],"mcp","mcp-server","model-context-protocol","ENV",{"_119":120,"_121":122,"_123":124},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]