# Watchgoose [Health: Active] **Category:** 💻 Developer Tools **Repository:** https://github.com/bartekrutkowski/watchgoose-mcp **GitHub Stars:** 1 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/watchgoose ## Description Monitor cron jobs and recurring work through a project-scoped Watchgoose connection. ## Claude Desktop Quick Installation Install path detected from listing signals. Uses `npx` (confidence: high): ```json "mcpServers": { "watchgoose": { "command": "npx", "args": ["-y","watchgoose-mcp"] } } ``` ## Documentation & README # 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: ```text https://mcp.watchgoose.com/mcp ``` ### Available in Watchgoose is [available in the Claude connector directory](https://claude.ai/directory/watchgoose). Watchgoose is [listed in ChatGPT plugins for GPT and Codex](https://chatgpt.com/plugins/plugin_asdk_app_6a95a3bd1df8819197ab3ccbf9269e8d). Watchgoose is [listed in the official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.bartekrutkowski/watchgoose-mcp). The [`watchgoose-mcp` package is available on npm](https://www.npmjs.com/package/watchgoose-mcp). In Claude, open **Settings > Connectors** and add the endpoint as a custom connector. For Claude Code, run: ```shell 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](https://watchgoose.com/docs/mcp/) 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: ```json { "mcpServers": { "watchgoose": { "command": "npx", "args": ["-y", "watchgoose-mcp"], "env": { "WATCHGOOSE_API_KEY": "hcr_your_project_key" } } } } ``` ## Claude Code ```shell 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: ```json { "mcpServers": { "watchgoose": { "command": "npx", "args": ["-y", "watchgoose-mcp"], "env": { "WATCHGOOSE_API_KEY": "hcr_your_project_key" } } } } ``` ## VS Code Create `.vscode/mcp.json`: ```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`. ## 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. 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. ## Development ```shell 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. ## License MIT