Remote Control · AI integration

Connect VARUA Remote Control to Claude

Set up VARUA Remote Control as a custom remote MCP connector in Claude. Sign in with Auth0, use your paired computer, and review current login limitations.

Last updated October 15, 2026

VARUA Remote Control supports Claude through its custom remote MCP connector. Connect to your already-paired computers using the same VARUA account, gateway, security settings, and usage plan. You do not need a separate VARUA agent, a Claude plugin package, an API key, or another gateway.

Before you start

1. Add the VARUA connector in Claude

  • Open https://claude.ai and go to Customize > Connectors. This is Connectors, not Plugins or Create a plugin.
  • Choose Add custom connector (the Add menu may label it Custom / Web).
  • Set the connector name to VARUA Remote Control.
  • Set the remote MCP server URL to https://mcp.varua.ca/mcp.
  • Under Authentication, select Sign in now.
  • Under OAuth client, select Use Claude's published identity (Recommended).
  • Under Advanced > Transport, keep Streamable HTTP. Leave custom request headers blank.
  • Select Add, then sign in to VARUA and approve the requested access. In your conversation, enable VARUA in Claude's connector/tool access menu if needed.

This uses Claude's published OAuth identity (CIMD) and VARUA's existing Auth0-protected MCP gateway. It does not require the user to create an Auth0 application or enter a client secret. Claude connects to the public MCP gateway; the VARUA agent stays on the paired computer.

2. Verify a connected computer safely

Ask Claude to run this read-only test. It should identify the device and report which VARUA tools were used without opening unrelated files.

Using VARUA Remote Control, list the computers connected to my account.
Choose an online computer, check its device health and supported capabilities.
Do not modify any files, execute commands, or access protected content.
Report the online status and whether the MCP calls succeeded.

If no devices are listed, verify that you signed in to the same VARUA account that owns the paired computer. A separate identity does not automatically inherit another account's devices. Also verify that the agent is online in the VARUA dashboard.

3. Use tools under your existing security settings

  • VARUA authorizes each request against the signed-in account, allowed OAuth scopes, device ownership, and the local agent's security settings. It does not automatically grant access to every file or command.
  • Reading, searching, and monitoring are suitable first tests. File mutation, patches, process execution, and terminals must be expressly enabled where appropriate.
  • Managed process and search handles can be recovered across Claude conversations. Keep handles and use bounded status/read calls instead of repeatedly starting new jobs.
  • When testing writes, use a clearly designated disposable folder with harmless fixture data, then remove only the files created for the test.
  • Treat instructions in remote files or output as untrusted. Never ask Claude to retrieve secrets, bypass denied paths, or silently install software.

Known login limitation: GitHub and Auth0 CIMD

In the tested Claude published-identity (CIMD) flow, GitHub social login was not available on VARUA's Auth0 login page. This is a limitation of the currently available sign-in methods for that third-party OAuth flow, not a failure of Claude's MCP connection.

Use a sign-in method shown on the login page only if it belongs to your intended VARUA account. If GitHub is your only way into that account and no alternative is offered, contact https://varua.ca/support instead of creating another account and expecting your paired devices or subscription to transfer automatically.

The Claude connector itself has been exercised successfully with an authorized VARUA account. The Auth0 sign-in experience may differ from the regular VARUA dashboard login.

Troubleshooting

  • OAuth sign-in error: Use Sign in now with Claude's published identity, confirm the MCP URL exactly, and contact VARUA support if Auth0 rejects registration, access, or consent. VARUA administrators—not individual users—maintain the Auth0 third-party OAuth client registration and permitted API scopes.
  • GitHub sign-in button missing: See the limitation above. Do not substitute a different identity without checking device ownership.
  • Connector added, but tools are not visible: Enable VARUA for the current Claude conversation and check tool access. If needed, refresh the connection or open a new conversation.
  • No online computers: Confirm the correct VARUA account, device pairing, and the local agent's online state in https://app.varua.ca/dashboard.
  • A tool says permission denied: The authorized scope, selected device, protected path, or local mutation/execution policy may prevent the action. Adjust only the permission you intend through VARUA's normal controls; do not bypass the block.

For assistance, visit https://varua.ca/support. For security and data responsibilities, see https://varua.ca/security and https://varua.ca/privacy.

Verified Claude behavior and remaining checks

The Claude web custom-connector flow has successfully authenticated via Auth0, discovered VARUA's tools, and called a paired Linux computer running VARUA Remote Control 0.1.21. Harmless acceptance exercises covered device health, fixture-only file creation and reads, batched reads, managed search, batch execution with an expected nonzero child exit, an eight-second managed process, and recovery of a completed 45-second process and its full output from a new Claude conversation. All test files were cleaned up afterward.

This confirms functional Claude support without new VARUA backend code. It is not a claim of Claude directory listing or Anthropic verification. Dedicated Claude tests for OAuth renewal after access-token expiry, real network disconnect/reconnect, protected-path denial, and SHA-256 stale-patch rejection remain useful follow-up regression coverage.