User-level MapleMCP
Runs with the enrolled user’s ordinary Windows or Linux permissions. Use it for files, terminal work, browser control, diagnostics, development, and other tasks that do not require SYSTEM/root.
MapleMCP separates what an account may ask for from what the installed endpoint is allowed to do. Standard and Pro use the same control plane; you choose the operating-system authority.
Runs with the enrolled user’s ordinary Windows or Linux permissions. Use it for files, terminal work, browser control, diagnostics, development, and other tasks that do not require SYSTEM/root.
Runs with SYSTEM authority on Windows or root authority on Linux. Intended for owners who deliberately want full-machine administration and self-repair capability.
A device advertises only the groups you grant. Authority and capability are separate: having SYSTEM/root does not automatically publish every tool.
| Mode | Behaviour |
|---|---|
| Guarded / Standard | High-risk mutations can require exact-action approval. Device and account restrictions always apply. |
| Full Send | Pre-authorizes routine mutations within the granted authority; R5/protected actions can still step up. |
| Owner Unrestricted | Trusted-owner privileged authority with fewer action gates. Hard safety floors and explicit session-loss confirmation remain. |
Network, reboot, credential, agent-repair, and similar operations can cut off the session that requested them.
Device information, app launch, links, and background connection.
Active notifications and media-session controls when Android grants the permission.
Accessibility tree, screenshot, taps, scroll, text entry, global actions, and gestures after explicit Accessibility enablement.
MapleMCP does not know or defeat your PIN, password, biometric, or device lock.
A tool works only when both layers permit it.