Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Watchtower implements the ingestion protocols of hosted error trackers, so their official SDKs report to it unchanged. Moving off a hosted tracker means changing one setting, the DSN or the push endpoint, rather than re-instrumenting every service. Errors are grouped into issues you can triage with your team, alerted to Slack, Linear and email, and handed to coding agents through MCP.
It runs as a single Go binary with Postgres as its only dependency.
Self-hosted error tracking. A drop-in for Sentry and AppSignal SDKs: one Go binary and Postgres, with Slack, Linear, email and an MCP server for coding agents.
sentry-cli or Sentry's bundler
plugins.You need Docker with Compose. Run:
curl -fsSL https://raw.githubusercontent.com/olucurious/watchtower/main/install.sh | sh
It sets Watchtower up in ./watchtower with generated secrets, starts it with
Postgres, and prints the address and a one-time setup code. To use another
folder, run … | WATCHTOWER_DIR=my-folder sh; the installer never takes over a
folder that belongs to another project. Open the address,
enter the code, and create your administrator account. Then create a project;
its page walks you through creating a key, adding the SDK and sending a first
error, and links to it as soon as it arrives.
Images are published for amd64 and arm64. To run a specific version, set
WATCHTOWER_VERSION (for example WATCHTOWER_VERSION=0.1.0) when you run the
installer, or in watchtower/.env later.
mkdir watchtower && cd watchtower
curl -fsSLO https://raw.githubusercontent.com/olucurious/watchtower/main/compose.yaml
cat > .env <<EOF
WATCHTOWER_DB_PASSWORD=$(openssl rand -hex 16)
WATCHTOWER_SECRET_KEY=$(openssl rand -hex 32)
EOF
docker compose up -d
docker compose exec watchtower watchtower setup-code # the code for the first account
To build the image from a checkout instead of pulling it:
git clone https://github.com/olucurious/watchtower.git && cd watchtower
# create .env as above, then:
docker compose -f compose.yaml -f compose.build.yaml up -d --build
Create a key on the project's page for the SDK the service already uses. The key's settings are shown once; Watchtower stores only a hash.
Replace the DSN; nothing else changes.
SENTRY_DSN=https://<key>@watchtower.example.com/<project-id>
Elixir ({:sentry, "~> 13.4"})
# config/runtime.exs
config :sentry, dsn: System.get_env("SENTRY_DSN"), environment_name: config_env()
# lib/my_app/application.ex, in start/2: report crashed processes, and say
# where log-reported errors (such as failed database connections) came from
:logger.add_handler(:sentry_handler, Sentry.LoggerHandler, %{config: %{metadata: [:mfa, :application]}})
Node.js (npm install @sentry/node)
const Sentry = require("@sentry/node")
Sentry.init({ dsn: process.env.SENTRY_DSN, environment: process.env.NODE_ENV })
Python (pip install sentry-sdk)
import os, sentry_sdk
sentry_sdk.init(dsn=os.environ["SENTRY_DSN"], environment="production")
Browser (npm install @sentry/browser)
import * as Sentry from "@sentry/browser"
Sentry.init({ dsn: "https://<key>@watchtower.example.com/<project-id>" })
Set two variables. Packages and instrumentation stay as they are.
APPSIGNAL_PUSH_API_ENDPOINT=https://watchtower.example.com
APPSIGNAL_PUSH_API_KEY=<key>
For the AppSignal browser SDK, create an AppSignal (browser) key and pass
its settings to new Appsignal({ key, uri }).
Every tested version has a captured payload in the test suite. The AppSignal protocol is reverse-engineered, so that adapter is marked experimental; see docs/adapters/appsignal.md. A weekly workflow checks for new AppSignal releases.
/), status tabs, sparklines and bulk resolve, mute or reopen.Alerts fire when an issue is new, when a resolved issue comes back, or when an issue reaches a number of events in an hour, optionally limited to a minimum level and one environment. They're written to an outbox in the same transaction as the event that triggered them, then delivered with retries, so an event is never stored without its alert. Each destination shows its last delivery or error and has a Test button.
Use an incoming webhook, or an existing Slack app's bot token (xoxb-…) with
a channel ID and the bot invited to that channel. Messages link straight to
the event that triggered them.
Add a Linear destination with an API key (Linear › Settings › Security & access › Personal API keys) and pick a team.
Each Linear issue is created with an ID derived from the Watchtower issue and your secret key, so a retried or concurrent request can never file it twice.
Members get email when an issue is assigned to them, when an issue they own regresses, and when someone comments on one, and can opt in to a daily or weekly digest of new issues, regressions and the busiest issues. Each member chooses on their Account page, which also has a Send test email button that shows the mail server's answer.
Set WATCHTOWER_EMAIL_PROVIDER to turn email on:
smtp works with any provider: Postmark, Amazon SES, Mailgun, Resend,
Google Workspace, Cloudflare Email Service, or a relay of your own.cloudflare uses Cloudflare Email Service's REST API, which also accepts
user-owned tokens (its SMTP endpoint accepts only account-owned ones).The sender's domain must be verified with your provider.
Watchtower runs a Model Context Protocol
server at /mcp, so an agent can pick up an error, understand it and fix it.
Create a token under Account › Agent access; the dialog shows the setup for
Claude Code, Codex, Cursor and other clients. For Claude Code:
claude mcp add --transport http watchtower https://watchtower.example.com/mcp \
--header "Authorization: Bearer wtp_…"
Then ask, for example, "Find the most frequent unresolved error in the reader project in Watchtower and fix it."
Tokens act as the member who created them, so an agent's changes appear under that member's name. They are read-only or read-write, can expire after 30 or 90 days, are stored only as SHA-256 digests, and stop working when revoked or when their owner is disabled. Error text reported by applications is labelled as untrusted data in every brief, and the endpoint rejects cross-origin browser requests.
Watchtower accepts uploads from sentry-cli and Sentry's Vite, webpack and
esbuild plugins. Create an upload token on the project's page, then in CI:
export SENTRY_URL=https://watchtower.example.com SENTRY_AUTH_TOKEN=wtk_… SENTRY_ORG=watchtower SENTRY_PROJECT=web
npx @sentry/cli sourcemaps inject ./dist
npx @sentry/cli sourcemaps upload ./dist
Before grouping, minified frames are mapped back to the original file, function and line, with surrounding source. Bundles match by debug ID, or by release and file URL for uploads without one, so issues group by your original code and stay stable across builds.
Watchtower reads WATCHTOWER_* environment variables.
Invalid settings stop Watchtower at startup with a message naming the variable, rather than failing later.
WATCHTOWER_PUBLIC_URL to the address SDKs and
people use. SDKs need to reach the ingestion endpoints; the web UI and
/mcp can stay on a private network.docker compose pull && docker compose up -d in the install directory. Database migrations run
automatically at startup.pg_dump like
any other database, and keep WATCHTOWER_SECRET_KEY with it.GET /healthz checks the process; GET /readyz
also checks the database. GET /metrics serves Prometheus counters for
accepted, rejected and shed events per adapter, worker outcomes, alerts,
emails and retention.WATCHTOWER_ROLES. Workers coordinate through Postgres SKIP LOCKED and
lock issues in a fixed order, so any number can run at once. Each process
uses up to 25 database connections (pool_max_conns in the URL); keep
replicas × pool size below Postgres's max_connections.X-Sentry-Rate-Limits) instead of
events being dropped silently. The limit is approximate: replicas together
can pass it by about a second of traffic. Events that fail processing five
times move to ingest_dead_letter.Sentry SDKs ─▶ sentry adapter ─┐
AppSignal agents ─▶ appsignal adapter ─┼─▶ scrub ─▶ queue ─▶ worker ─▶ issues & events
Browser SDK ─▶ appsignal-frontend adapter ─┘ (symbolicate, │
group, alert) ├─▶ web UI and API
├─▶ Slack · Linear · email
└─▶ MCP for coding agents
key=value pairs are redacted, as are tags, context values
and URL parameters with sensitive names.watchtower setup-code # a new code for creating the first account in the browser
watchtower user create [email protected] -admin # the password is prompted, never in argv
watchtower project create reader -name "Reader Web"
watchtower key create reader sentry
watchtower issues reader -status unresolved
watchtower issue resolve 12 -actor ada
watchtower adapters # adapters and tested SDK versions
watchtower healthcheck # exits 0 when the local server is healthy
Contributions are welcome. CONTRIBUTING.md covers setting up a development environment, running the tests and preparing a pull request, and AGENTS.md describes the architecture and the rules every change must keep, for people and coding agents alike.
Watchtower is licensed under the Apache License, Version 2.0. Contributions are accepted under the same licence.
Self-hosted error tracking. A drop-in for Sentry and AppSignal SDKs: one Go binary and Postgres, with Slack, Linear, email and an MCP server for coding agents.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Watchtower ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Self-hosted error tracking. A drop-in for Sentry and AppSignal SDKs: one Go binary and Postgres, with Slack, Linear, email and an MCP server for coding agents.
