Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.
npx -y dingdawg-loop{
"DINGDAWG_API_KEY": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-dingdawg-dingdawg-loop": {
"command": "npx",
"args": [
"-y",
"dingdawg-loop"
],
"env": {
"DINGDAWG_API_KEY": "YOUR_SECRET_VALUE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
dingdawg-loop is an MCP server for Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y dingdawg-loop; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y dingdawg-loop. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y dingdawg-loop. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y dingdawg-loop. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y dingdawg-loop. Add required environment variables before starting Cursor or VS Code.
dingdawg-loop uses STDIO transport. Use the package or command config in Install.
dingdawg-loop inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
dingdawg-loop does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
dingdawg-loopstdio | npm | 2.0.7 | Env: DINGDAWG_API_KEY secret |