MapleMCP

YOUR DEVICES. YOUR DECISION.

Control your own devices with AI.

MapleMCP securely connects AI assistants and automation to the computers and phones you choose, with explicit permissions, local execution, and access you can revoke.

Early public beta. Start with a device you control.

You stay in control at every layer.

You enroll the device

Installing MapleMCP does not silently give an account access. You approve enrollment and verify the device.

You choose capabilities

Set the files, search, terminal, diagnostics, and mobile controls available for each device.

You can revoke access

Remove a device, change its capabilities, or revoke a client authorization from your control center.

WHAT YOU CAN DO

Useful work, with boundaries you can see.

Files & diagnostics

Inspect allowed files, search content, gather system details, and troubleshoot the device you selected.

Work with a Windows PC →

Managed processes

Run terminal work only where you grant process access, using the installed agent’s operating-system permissions.

Review desktop permissions →

Browser & Android control

Use supported browser and mobile controls only when the right device and operating-system permissions are available.

Explore Android control →

Resident Worker

Let an enrolled endpoint carry out supported work and keep attention items visible when a person is needed.

See product use cases →

Multiple enrolled devices

Choose the right workstation, server, or phone for the task from one authorized connection.

Understand remote MCP →

Fleet coordination

Early fleet features remain gated to the accounts and endpoints where backend support is available.

Get beta support →

HOW IT WORKS

From install to a safe first task.

Install MapleMCP on a device you control.

Choose the installer for your supported platform and follow the on-device setup flow.

Approve the enrollment.

Confirm the short code in your browser so the device joins only your account.

Choose the permissions you need.

Start small. You can add or remove capability groups later from the dashboard.

Connect an MCP client and ask for work.

Use an authorized AI client to choose the device and request an allowed action.

START WITH AN OUTCOME

Built for real device work.

Maintain a homelab

Check services, inspect diagnostics, and work on the right enrolled Linux host.

AI for homelabs →

Troubleshoot a remote PC

Gather evidence first, explain the problem, then make an authorized change.

AI IT support →

Control does not mean bypassing security.

MapleMCP does not bypass operating-system accounts, Android lock screens, MFA, passkeys, or CAPTCHA. Local permissions still apply, and sensitive credentials stay out of AI prompts.