Frequently Asked Questions on Remote Access

RemotePC MCP connects your RemotePC account with MCP-compatible AI clients using the open Model Context Protocol (MCP) standard. It allows supported AI clients to access RemotePC capabilities through a single, secure MCP connection, without requiring a custom integration for each AI client.

RemotePC MCP securely connects your RemotePC account with MCP-compatible AI clients using the open Model Context Protocol (MCP) standard. The hosted MCP service allows you to connect without deploying or managing your own MCP server.

After authorization, your AI client can use supported RemotePC tools to access your account, devices, and connectivity capabilities based on your requests and the access permissions you select.

Note: RemotePC supports hosted MCP only and does not support self-hosted MCP deployment.

RemotePC MCP uses authenticated access to connect an AI client to your RemotePC account. Your RemotePC credentials are not shared with the connected AI client. Access is controlled through explicit permissions and session duration, while RemotePC host-level protections continue to apply.

RemotePC MCP provides two permission levels:

• View Only: Allows the AI client to access supported information, such as account details, device information, screens, windows, and files, without performing actions on the remote computer.
• Full Control: Allows the AI client to access supported interactive and action-based capabilities, subject to RemotePC host-level controls.

You can configure the MCP session duration while authorizing an AI client. Sessions can be configured from 12 hours to 30 days.

Sessions expire automatically when the selected duration ends and cannot be renewed without reauthorization.

Yes. You can revoke access for any connected AI application from your RemotePC account.

To revoke access,

1. Sign in to your RemotePC account.
2. Go to My Account > MCP Connections.
3. Click Revoke access for the application you want to disconnect from your RemotePC account.
4. Click Revoke access in the confirmation popup.

Once access is revoked, the application will no longer be able to access RemotePC through the existing MCP authorization. To restore access, you must authenticate and authorize the application again.

Important Notes:

• Revoking an MCP authorization may interrupt active operations. If an MCP connection is revoked while requests are in progress, those operations may be interrupted or fail.
• Revoking an MCP connection from an AI client may not revoke its authorization in your RemotePC account. To verify whether access has been revoked, sign in to your RemotePC account and navigate to My Account > MCP Connections. If the application's authorization is still active, click Revoke access to revoke it.

No. RemotePC MCP operates based on the permissions configured for the connected AI client. View Only access allows the AI client to retrieve supported information, while Full Control access allows it to perform supported actions, subject to RemotePC host-level controls.

No. You do not need to write any code. Add RemotePC MCP as a connector or plugin in a supported AI client, sign in to your RemotePC account, and authorize access. The AI client connects to RemotePC using the open Model Context Protocol (MCP) standard.

View-only tools

Tool	Description
get_devices	Retrieves the list of devices configured for your RemotePC account, along with their status and details
get_user_info	Retrieves your RemotePC account details, including your plan, email address, phone number, and next billing date
list_sub_users	Lists the sub-users associated with your RemotePC account
get_groups	Lists the computer and user groups configured for your account
get_user_invoices	Retrieves invoice details, including the amount, date, and charge description
list_open_apps	Lists visible windows on a remote device, including their titles, positions, sizes, associated processes, and monitor information. This helps the agent identify the correct window before interacting with it.
screenshot	Captures the remote device's screen, including the primary display, a specific monitor, a window, or the full virtual desktop. The screenshot includes coordinate information to help the agent interact with the correct on-screen elements.
get_device_file	Retrieves a file of up to 10 MB from the remote device and provides a temporary, signed download link. The file contents are not sent directly through chat.
get_recent_devices	Lists the recently accessed devices on your RemotePC account

Full-control tools

Tool	Description
run_command	Executes a command on the remote device and returns the command output, exit code, and timeout status.
device_restart	Schedules or cancels a restart on the remote device, with a configurable grace period and an optional on-screen warning message.
update_remotepc_app	Checks for the latest RemotePC host application version, downloads and installs the update, and confirms the installed version.
connect_to_device	Generates a temporary URL for connecting to a remote device. The URL expires after a limited period.
mouse	Controls the mouse on the remote device by moving the cursor, clicking, scrolling, and dragging at specific coordinates Example: Move the cursor to a button and click it, scroll through a webpage, or drag a file to another location.
keyboard	Sends text input and key combinations, such as Ctrl+S or Alt+F4, to interact with applications on the remote device. Example: Type text into a document, press Ctrl+S to save a file, or press Alt+F4 to close a window.
send_chat_message	Displays an on-screen message to the person using the remote device, allowing the agent to communicate updates or explain an action. The message does not provide a reply channel to the agent.

RemotePC host-level protections apply to MCP access. Mouse control and keyboard control are blocked when the remote computer is locked.

RemotePC MCP works with supported MCP-compatible AI clients that support remote Streamable HTTP MCP servers, including:

• ChatGPT
• Claude
• Cursor
• Codex
• Grok

Follow the guide for your AI client to add the RemotePC MCP endpoint, sign in, authorize access, and choose your permission level and session duration.