bartekrutkowski/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:
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:
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:
Claude Code
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:
VS Code
Create .vscode/mcp.json:
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:
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 |
| --------------- | ------------------------------ | ------------------------------------------------------- |