Remote Watchtower

works.galorweb.watchtowerPublished by watchtower.galorweb.worksOfficial publisherv1.0.0Updated Oct 30, 2026

Reach your own computers from any AI app: files, search, commands, approvals and outage alerts.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFiles & Storage

Overview

AI-generated overview

Remote Watchtower is a hosted MCP endpoint that lets an AI assistant reach your own computers for files, search, commands, approvals and outage alerts.

What you can do
  • Access files on your own machines through the assistant
  • Search across those computers
  • Run commands on them, subject to approvals
  • Handle approval requests for actions taken
  • Receive outage alerts when a machine goes down
When to use it
Useful when you want an AI app to work with your own computers remotely rather than only with cloud services, for example to look up files, search local data, run commands or be notified about outages.
Requirements
A remote MCP endpoint at the provider's hosted address, connected over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared, and no local package needs to be installed.
Before you install
The server gives an assistant access to your own computers, including running commands, so scope and approval settings matter. Access is granted through OAuth sign-in to the provider's hosted service, and file contents, search results and command output pass through that third party. Outage alerts imply the service monitors your machines.

Installation

In SourceWeft

  1. Open Remote Watchtower in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/works.galorweb.watchtower%2Fremote-watchtower/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "remote-watchtower": {
      "type": "http",
      "url": "https://watchtower.galorweb.works/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.