What AI can do
Check account status, launch or stop accounts, test and assign proxies, and help review activity.
AI assistant
Let AI handle repetitive actions.
Connect your preferred AI tools to MaskPilot. They can check accounts, test proxies, or open and stop accounts within your existing access.
MaskPilot 
Get started in four steps
01
Open MaskPilot
02
Turn on the AI assistant
03
Connect your AI tool
04
Work within your current access
What you control
Admins decide who can use AI. It can only work with content the current user already has permission to access.
Tasks and boundaries
What it can do, where it runs, and who approves it.
MaskPilot exposes capabilities to AI tools through local MCP. The client must run on the same computer and remain signed in, while every call still passes the current account and team permission checks.
Start with repetitive actions you can verify.
Begin with status checks, lists, and proxy tests, then enable launch, stop, or binding actions only after the results are clear. The current client version defines the available tool list.
- List accounts, proxy groups, and available proxies
- Run proxy tests on the current computer
- Bind or unbind proxies for authorized accounts
- Launch or stop accounts the current user can access
The caller and MaskPilot run on the same computer.
Sign in to the client and enable the AI assistant, then configure the current local address and Bearer Token in the caller. Closing MaskPilot stops the local connection.
- The service listens on a local address by default
- Never place the Token in public docs, screenshots, or logs
- Update the caller after resetting the Token
A visible tool name does not grant extra access.
Calls are rejected when a teammate lacks account assignment or feature permission. Admins can disable AI for teammates, and recent calls make it possible to review what ran.
- Tool discovery and call authorization are separate
- AI follows teammate account visibility
- Results remain visible in the current client history
Confirm one layer at a time when a connection fails.
Check that the client is running and signed in, then inspect the AI switch, local address, Token, and current tool name. Avoid replacing several settings before the failing layer is known.
- Read the current Token again when authentication fails
- Compare unknown tools with the names returned by this client version
- Review teammate and account assignments after a permission failure
Start with read-only tasks
Check account access and local boundaries before connecting AI.
Download and sign in to MaskPilot. Let AI read account or proxy status first, then enable state-changing actions after permissions and call history look correct.