Connect ChatGPT and Claude to Your Computer with EXZA Remote

What is EXZA Remote?

EXZA Remote is a remotely accessible Model Context Protocol service that connects ChatGPT, Claude, and other compatible MCP clients to a computer you own or are authorized to use. It combines an authenticated cloud endpoint with a local client running on macOS, Windows, or Linux.

Unlike a cloud-hosted virtual desktop, EXZA Remote works with your own computer. An authorized AI assistant can use supported tools to inspect permitted files, check system information, follow terminal jobs, run approved commands, and perform compatible desktop actions. The exact capabilities depend on your operating system, AI client, account permissions, and authorized scope.

Important: This GitHub repository is a public product-information repository, not the source code for the private EXZA Remote application. You do not need to clone it to install the client.

How the connection works

1. Your AI assistant connects to the EXZA Remote MCP service using MCP and OAuth.
2. The service routes an authorized session to your paired computer.
3. The local client checks whether the requested operation is supported and permitted.
4. If an action requires approval, you can approve or reject it.
5. Closing the local client terminal ends the computer's active connection.

The public MCP endpoint is https://remote.exza.de/mcp. Device pairing is account-specific and requires both a server-confirmed PIN and local terminal approval.

Key features

• AI assistant connectivity: Use one HTTPS MCP endpoint with ChatGPT, Claude, or another compatible MCP client.
• Secure device pairing: Pair a computer using a temporary six-digit PIN and confirm the request locally.
• File operations: Discover, inspect, and manage files within the approved device scope.
• Terminal and job support: Run supported commands and follow authorized long-running tasks.
• System information: Check device status, system details, and supported process information.
• Desktop interactions: Perform supported application or window actions when the operating system and its permissions allow them. Some functions are specific to macOS.
• Approval controls: Review sensitive requests through local and platform authorization mechanisms.
• Device dashboard: View paired devices, manage connections, review usage, and access account or billing settings.
• Cross-platform client: Installation paths are available for macOS, Windows, and Linux, although tested behavior and available tools vary by platform.

The current integration registers 59 MCP tool interfaces. This number does not mean that every tool works on every operating system or that every action can run without approval. Consult the tool catalog and platform compatibility guide before planning an OS-specific workflow.

Prerequisites

Before installing EXZA Remote, make sure you have:

• A computer you own or are authorized to manage.
• An EXZA account created through the customer dashboard.
• Internet access.
• Node.js 22 or newer, including npm.
• On macOS or Linux, curl, unzip, and a SHA-256 utility.
• An AI client and account that support custom remote MCP connections.

EXZA Remote itself should run as your normal user and does not require administrator or root access. Your Node.js installer may separately request administrator approval.

Verify Node.js and npm

Open Terminal on macOS or Linux, or PowerShell on Windows, and run:

node --version
npm --version

The Node.js result must begin with v22 or a newer major version. If Node.js is missing or outdated, install a maintained LTS release from the official Node.js download page, reopen your terminal, and check the versions again.

If nvm is already installed on Linux, you can select a maintained LTS release with:

nvm install --lts
nvm use --lts

Do not copy an unknown curl | bash command to install a version manager. Follow trusted Node.js or distribution-specific instructions instead. Also avoid changing the runtime while an EXZA Remote connection is active; finish the current session first.

Install the local client

Use the official command displayed in the EXZA customer portal. The installation scripts download the official client archive over HTTPS, verify its SHA-256 checksum, install runtime dependencies, and start the client in a visible foreground terminal.

macOS

Open Terminal, confirm that Node.js and npm meet the requirements, and then run:

curl -fsSL https://remote.exza.de/install.sh -o exza-install.sh && sh exza-install.sh

Windows 10 or 11

Open PowerShell as a normal user and run:

node --version
npm --version
curl.exe -fsSL https://remote.exza.de/install.ps1 -o exza-install.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File .\exza-install.ps1

The -ExecutionPolicy Bypass setting applies only to that PowerShell process; it does not permanently change the system policy. Inspect the downloaded script before running it, confirm that it came from remote.exza.de, and follow your organization's security requirements. Windows native end-to-end testing is currently more limited than macOS testing.

Linux

After verifying Node.js 22 or newer and npm, run:

curl -fsSL https://remote.exza.de/install.sh -o exza-install.sh && sh exza-install.sh

Linux distribution and desktop-tool compatibility can vary. Check the official platform documentation for current limitations.

Keep the EXZA Remote terminal open while using the service. The client runs visibly in the foreground, and closing that terminal ends the active computer connection.

Pair your computer

1. Register or sign in at EXZA Remote — My Devices.
2. Verify your email if requested.
3. Start the local client and wait for a server-confirmed six-digit PIN to appear in the terminal.
4. Enter the PIN in the customer dashboard within five minutes.
5. Check that the requesting EXZA account is correct.
6. Press Y in the terminal to approve the pairing, or press N to reject it.

The website step and local confirmation work together: knowing the PIN alone is not enough to complete pairing without approval at the computer.

Connect ChatGPT, Claude, or another MCP client

In an AI client that supports custom remote MCP connectors, create a connection with these settings:

• Name: EXZA Remote
• Server URL: https://remote.exza.de/mcp
• Sign-in: Your EXZA account through the OAuth flow

Complete the sign-in process, select the intended device, and carefully review the requested permissions. Custom MCP connector availability depends on the AI service, subscription plan, and account or workspace settings.

Run a safe first request

Begin with a read-only status check rather than a command or file modification. For example:

Check whether my EXZA Remote computer is online. Do not change anything.

Once the connection works, try a narrowly scoped request that clearly states the allowed location and prohibits changes:

Inspect the permitted project folder and summarize its top-level files. Do not edit, rename, move, or delete anything.

For a development workflow, you could request an approved local test only after reviewing the command:

Show me the test command you propose to run in the permitted project folder. Wait for my approval before executing it.

Other supported workflows can include checking tooling, reviewing permitted logs, inspecting running processes, collecting environment information, following a long-running terminal job, or coordinating supported desktop tasks. Whether a request succeeds depends on the available tool, operating system, granted permissions, and any required approval.

Manage the running client

Enter the following commands inside the running EXZA Remote terminal when needed:

• status displays the current connection and pairing state.
• new code requests another PIN when the computer is not yet paired and the previous PIN has expired.
• reset pairing begins a local pairing reset when the previous pairing has been revoked or is unusable.
• confirm reset pairing confirms that reset within 30 seconds. Pairing the computer again will still require approval with Y.

Do not start a second agent while the first terminal remains connected. Removing a device through the website and resetting local pairing are separate operations.

Advanced usage and safety tips

Use the smallest practical scope

Authorize only the files, applications, devices, and actions required for the current task. A narrow request is easier to review than an unrestricted instruction. Ask the assistant to explain a proposed command or modification before approving it.

Separate inspection from modification

Start by requesting a read-only inspection. After reviewing the result, make a second request for a specific change. This reduces ambiguity and gives you another opportunity to reject an unsafe operation.

Monitor long-running work

For builds, tests, or scripts that take time, use the supported job-following capabilities rather than repeatedly starting the same command. Keep the local terminal visible and watch for approval requests.

Account for platform differences

Do not assume that all 59 registered interfaces are available on every system. Desktop automation may depend on OS-level permissions, and some actions are macOS-specific. Linux desktop compatibility varies by distribution, while native Windows testing is currently more limited than macOS.

Protect credentials and private data

• Never paste passwords, access tokens, device secrets, or pairing PINs into an AI conversation.
• Do not publish private logs when requesting support.
• Inspect sensitive commands and file changes before approving them.
• Download installers only from remote.exza.de.
• Disconnect devices through the portal when access is no longer needed.
• Close the local terminal to end the current active connection.

No remote-access system can eliminate every risk. Account authentication, OAuth authorization, device pairing, local confirmation, permission checks, and HTTPS provide layers of protection, but you remain responsible for reviewing requested actions.

Troubleshooting

Node.js is missing or too old

If the terminal reports command not found, not recognized, or Node.js version 20 or lower, install Node.js 22 or newer and make sure it is on your shell's PATH. Reopen Terminal or PowerShell before checking again.

The pairing PIN expired

In an unpaired running client, enter new code to request a fresh PIN. Enter it in the dashboard within five minutes and approve the correct account locally.

A previous pairing no longer works

Use reset pairing, followed by confirm reset pairing within 30 seconds. Then complete the normal website and local approval process again.

The AI client cannot add the MCP server

Confirm that the service, plan, account, or workspace supports custom remote MCP connectors. Also verify that the server address is exactly https://remote.exza.de/mcp and that the EXZA OAuth flow was completed.

The computer appears offline

Check that the local client terminal is still open, use status, and verify internet connectivity. Closing the terminal disconnects the active client.

Usage allowance and documentation

EXZA Remote offers a free tier with 10,000 successful tool calls per EXZA account per UTC month, shared across connected AI clients. Current premium options, pricing, availability, and fair-use terms are shown on the official website and customer dashboard.

For current setup instructions and platform-specific details, consult the official Help Center, getting-started guide, ChatGPT and Claude setup guide, and security model.

Conclusion

EXZA Remote provides a controlled way to connect an MCP-compatible AI assistant to your own computer. Install the foreground client, pair the device with both a temporary PIN and local confirmation, add the authenticated MCP endpoint, and start with read-only requests. Keep permissions narrow, review sensitive actions, account for platform differences, and disconnect the client when your work is complete.