Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.
DingDawg Loop Protocol (DDLP) — safe scheduled AI agents with governance gates.
Every loop execution is verified, receipted, and fail-closed. MCP-native. Works with CrewAI, LangGraph, Claude Code, and Cursor.
npx dingdawg-loop
Or as an MCP server in Claude Desktop / Claude Code:
{
"mcpServers": {
"dingdawg-loop": {
"command": "npx",
"args": ["dingdawg-loop"]
}
}
}
DDLP wraps any scheduled agent action with a governance gate that:
| Tool | Description |
|---|---|
register_loop | Register a new scheduled loop with name, description, cron, and governance policy |
execute_loop | Run one cycle of a registered loop — governance gate fires before any action |
list_loops | List all registered loops with status, last execution, and receipt count |
pause_loop | Pause a running loop — no executions until resumed |
resume_loop | Resume a paused loop |
loop_audit | Retrieve the full signed receipt audit trail for any loop |
DDLP classifies every loop at registration time. High-risk categories require elevated approval:
DROP statementsWorks with any MCP-compatible AI client:
BUSL-1.1 — see LICENSE
DingDawg Enterprise — hello@dingdawg.com — dingdawg.com
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y dingdawg-loopMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dingdawg-dingdawg-loop": {
"command": "npx",
"args": [
"-y",
"dingdawg-loop"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencedingdawg-loopnpmio.github.dingdawg/dingdawg-loop works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.