Back to Directory/Developer Tools

io.github.dingdawg/dingdawg-loop

Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.

Developer ToolsJavaScriptv2.0.8

dingdawg-loop

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.

Install

npx dingdawg-loop

Or as an MCP server in Claude Desktop / Claude Code:

{
  "mcpServers": {
    "dingdawg-loop": {
      "command": "npx",
      "args": ["dingdawg-loop"]
    }
  }
}

What it does

DDLP wraps any scheduled agent action with a governance gate that:

  • Evaluates the loop description before execution
  • Blocks destructive, financial, or sensitive operations until policy thresholds are met
  • Signs every execution with an Ed25519 receipt
  • Provides full audit history per loop

MCP Tools

ToolDescription
register_loopRegister a new scheduled loop with name, description, cron, and governance policy
execute_loopRun one cycle of a registered loop — governance gate fires before any action
list_loopsList all registered loops with status, last execution, and receipt count
pause_loopPause a running loop — no executions until resumed
resume_loopResume a paused loop
loop_auditRetrieve the full signed receipt audit trail for any loop

Governance gates

DDLP classifies every loop at registration time. High-risk categories require elevated approval:

  • Destructive operations — file deletion, database mutations, DROP statements
  • External communications — email sends, Slack messages, webhook calls
  • Financial operations — any spend, transfer, or payment action
  • Sensitive data access — PII reads, credential access, health records
  • Bulk operations — mass updates, batch sends, bulk deletes

Compatibility

Works with any MCP-compatible AI client:

  • Claude Desktop / Claude Code
  • Cursor
  • CrewAI (via MCP bridge)
  • LangGraph (via MCP bridge)

License

BUSL-1.1 — see LICENSE

Publisher

DingDawg Enterprise — hello@dingdawg.com — dingdawg.com

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y dingdawg-loop

Set up in your AI client

Merge 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.

json
{
  "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 reference

Package

dingdawg-loopnpm

Compatible MCP Clients

io.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.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.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.

Learn More