Watchgoose

Name: Watchgoose
Author: bartekrutkowski

by bartekrutkowskiversion 1.1.3i★ –iComputer or cloud

Registry nameio.github.bartekrutkowski/watchgoose-mcp

Install

Overview

Description from the maker (original English)

Monitor cron jobs and recurring work through a project-scoped Watchgoose connection.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiVery new↓ 90/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: WATCHGOOSE_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: WATCHGOOSE_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.watchgoose.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "watchgoose": {
      "command": "npx",
      "args": [
        "-y",
        "watchgoose-mcp"
      ],
      "env": {
        "WATCHGOOSE_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http watchgoose https://mcp.watchgoose.com/mcp

Or run it on your computer

claude mcp add watchgoose --env WATCHGOOSE_API_KEY=your-value -- npx -y watchgoose-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "watchgoose": {
      "url": "https://mcp.watchgoose.com/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "watchgoose": {
      "command": "npx",
      "args": [
        "-y",
        "watchgoose-mcp"
      ],
      "env": {
        "WATCHGOOSE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "watchgoose": {
      "type": "http",
      "url": "https://mcp.watchgoose.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "watchgoose": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "watchgoose-mcp"
      ],
      "env": {
        "WATCHGOOSE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.watchgoose.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

WATCHGOOSE_API_KEY secret required env
Project-scoped Watchgoose API key: hcr_ read-only or hcw_ read-write.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account bartekrutkowski, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 397 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18444 servers in this category
Published to the registry more recently than 74% of the other 18444 servers in this category
Basic checks equal to or better than 100% of the other 18444 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Watchgoose safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WATCHGOOSE_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.3) reached the registry 15 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Egovframe Scaffold MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

Egovframe Scaffold MCP

eGovFrame (전자정부 표준프레임워크) projects: templates, components, CRUD, build, 5.x migration, dependencies

by EricSeokgonEarly↓ 1.4K/wkUpdated today

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Watchgoose MCP

Watchgoose MCP connects MCP-capable AI clients to the Watchgoose Management API. It lets you inspect cron and recurring-task monitoring, with check changes available only when you explicitly enable writes.

Hosted connector

Use the hosted Streamable HTTP endpoint in clients that support OAuth 2.1 and Dynamic Client Registration:

https://mcp.watchgoose.com/mcp

Available in

Watchgoose is available in the Claude connector directory.

Watchgoose is listed in ChatGPT plugins for GPT and Codex.

Watchgoose is listed in the official MCP Registry.

The watchgoose-mcp package is available on npm.

In Claude, open Settings > Connectors and add the endpoint as a custom connector. For Claude Code, run:

claude mcp add --transport http --scope user watchgoose https://mcp.watchgoose.com/mcp

The browser consent flow limits each connection to one project and defaults to read-only access. See the Watchgoose MCP documentation for the tool and privacy boundaries.

Requirements

Node.js 20 or later
A project-scoped Watchgoose API key from Project settings → API Access → Create (read-only)

Use an hcr_ read-only key when you only need check state and status history. Use an hcw_ read-write key when you also need pings, integrations, or check changes.

Claude Desktop

Add this entry to claude_desktop_config.json and restart Claude Desktop:

"mcpServers": { "watchgoose": { "command": "npx", "args": ["-y", "watchgoose-mcp"], "env": { "WATCHGOOSE_API_KEY": "hcr_your_project_key" } } } }

Claude Code

claude mcp add --env WATCHGOOSE_API_KEY=hcr_your_project_key \

--transport stdio --scope user watchgoose -- npx -y watchgoose-mcp

Run claude mcp get watchgoose to check the connection.

Cursor

Create .cursor/mcp.json in your project, or add the same entry to your user MCP configuration:

"mcpServers": { "watchgoose": { "command": "npx", "args": ["-y", "watchgoose-mcp"], "env": { "WATCHGOOSE_API_KEY": "hcr_your_project_key" } } } }

VS Code

Create .vscode/mcp.json:

"servers": { "watchgoose": { "type": "stdio", "command": "npx", "args": ["-y", "watchgoose-mcp"], "env": { "WATCHGOOSE_API_KEY": "hcr_your_project_key" } } } }

Run MCP: List Servers and start watchgoose.

Cline

Cline connects to the hosted endpoint with OAuth, so no API key is needed. Open MCP Servers > Configure MCP Servers and add this entry to cline_mcp_settings.json:

"mcpServers": { "watchgoose": { "type": "streamableHttp", "url": "https://mcp.watchgoose.com/mcp" } } }

Keep "type": "streamableHttp" exactly as written; without it Cline falls back to SSE and the connection fails. When Cline prompts you to authenticate, sign in to Watchgoose in the browser, choose one project and keep read-only access unless you want Cline to change checks. To use a project API key instead, add the npx entry from the Cursor section above to the same file.

Environment

Variable	Required	Default	Description
`WATCHGOOSE_API_KEY`	Yes	-	Project-scoped `hcr_` read-only key, `hcw_` read-write key, or legacy 32-character key.
`WATCHGOOSE_API_URL`	No	`https://watchgoose.com/api/v3`	Management API base URL. HTTPS is required except for loopback development hosts. The key is sent to this host, so use only a URL you trust.
`WATCHGOOSE_ENABLE_WRITES`	No	`false`	Set to `true` to expose mutation tools when the key is read-write.
`WATCHGOOSE_API_KEY_ACCESS`	Legacy keys only	-	Required as `read-only` or `read-write` for an unprefixed 32-character key.

The server classifies key prefixes locally and never probes the API to infer access. Setting WATCHGOOSE_ENABLE_WRITES=true cannot give a read-only key additional access.

Tools

Checks are addressed by stable 40-character unique_key values. UUIDs, ping URLs, and integration UUIDs are used only inside the server and are not shown to the AI client.

Tool	Required access	Management API mapping
`list_checks`	Read-only	`GET /checks/`
`get_check`	Read-only	`GET /checks/`
`list_flips`	Read-only	`GET /checks/ /flips/`
`list_pings`	Read-write	Resolve `unique_key`, then `GET /checks/ /pings/`
`list_channels`	Read-write	`GET /channels/`
`create_check`	Read-write plus writes enabled	`POST /checks/`
`update_check`	Read-write plus writes enabled	Resolve `unique_key`, then `POST /checks/`
`pause_check`	Read-write plus writes enabled	Resolve `unique_key`, then `POST /checks/ /pause`
`resume_check`	Read-write plus writes enabled	Resolve `unique_key`, then `POST /checks/ /resume`
`delete_check`	Read-write plus writes enabled	Resolve `unique_key`, then `DELETE /checks/`

Integration assignments use exact integration names. Names must be non-empty and unique within the project.

create_check is a create-or-update operation when unique is supplied: a matching existing check has its supplied settings replaced. timeout without schedule also switches a scheduled check to interval monitoring: the stored schedule string remains, but no longer governs cadence. Include the confirmed schedule to retain scheduled monitoring. Other omitted settings remain unchanged. channels: [] clears all alert integration assignments. The tool therefore advertises destructiveHint: true. A new check awaits success/failure for completion-based cadence; a first failure can move it down. An optional start ping can initiate runtime monitoring before completion.

List results are capped at 100 checks, 100 pings, 200 flips, and 100 integrations. Every serialized tool result is also capped at 24,000 characters. Results include metadata when entries are omitted.

Security

Writes are disabled by default, even with an hcw_ key.
The API key is sent only in the X-Api-Key header and is never logged or returned.
API redirects are rejected so credentials cannot be forwarded to another host.
Check UUIDs, ping and update URLs, integration UUIDs, and unknown future API fields are removed from output.
Pings keep only type, date, n, scheme, method, and duration. Source IP addresses, user agents, run IDs, and body URLs are removed.
Ping bodies are never requested.
The server has no telemetry.

Protect client configuration files that contain API keys. Prefer a dedicated project and the least-privileged key that exposes the tools you need. Revoke a key from Watchgoose project settings when it is no longer in use.

Report vulnerabilities privately as described in SECURITY.md.

Workflow skills

The repository includes portable skills for auditing scheduled-job coverage, drafting single-job setup, triaging missed heartbeats, reviewing existing monitoring health, and proposing approved create-only batches from an audit, list or CSV. See the skills guide for local installation, examples, and safety boundaries. Skills do not grant additional access, automatically run jobs, or change the existing directory listings.

The installable monitoring plugin lives in plugins/watchgoose-monitoring/, with one canonical skill tree and remote-MCP adapters. Load that subfolder rather than the repository root; the old root plugin/skill paths are superseded without automatic migration of installed copies. The npm CLI and hosted endpoint remain unchanged.

Each release also publishes the plugin as the root of pixeware/watchgoose-plugin:

Gemini CLI: gemini extensions install https://github.com/pixeware/watchgoose-plugin
Grok Build: grok plugin install pixeware/watchgoose-plugin --trust
Any agent that reads Agent Skills: npx skills add pixeware/watchgoose-plugin, then add the hosted endpoint in your client

Development

npm install

npm run format:check npm run lint npm run typecheck npm test npm run publish:dry-run

Production integration tests are opt-in and require dedicated test-project keys. They never run in CI.

Every user-visible distribution shares one release version: the npm package, server.json, the hosted server, the Claude and portable plugin manifests and the OpenAI plugin. Bump WATCHGOOSE_RELEASE_VERSION in packages/core/src/constants.ts and the matching manifests together; tests/skills/release-version.test.ts fails if any of them disagree. The OpenAI upload ZIP is built with npm run build:openai-plugin.

Watchgoose

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Egovframe Scaffold MCP

README from the maker

Watchgoose MCP

Hosted connector

Available in

Requirements

Claude Desktop

Claude Code

Cursor

VS Code

Cline

Environment

Tools

Security

Workflow skills

Development

Support

License

Various badges