DENGEL / DOCS

Dengel MCP setup

Dengel MCP lets an agent ask for repository ownership context, review decisions, collisions and Receipts. It also has a separate proposal endpoint for handing off a pushed candidate; proposal is a request for human review, not approval, verification, landing, promotion or spending. Ask your operator for access to the private Streamable HTTP endpoint, its client token and the repository it is configured for. The examples below use the read endpoint. Use the full endpoint URL provided by your operator, including the /mcp path.

Codex

Make DENGEL_MCP_CLIENT_TOKEN available in Codex's environment, then run:

codex mcp add dengel --url "$DENGEL_MCP_URL" \
  --bearer-token-env-var DENGEL_MCP_CLIENT_TOKEN
codex mcp get dengel

Claude Code and Cursor

Use the following configuration in .mcp.json for Claude Code or .cursor/mcp.json for Cursor. Set both variables in the environment from which you launch the client. The configuration contains variable references only.

{
  "mcpServers": {
    "dengel": {
      "type": "http",
      "url": "${env:DENGEL_MCP_URL}",
      "headers": {
        "Authorization": "Bearer ${env:DENGEL_MCP_CLIENT_TOKEN}"
      }
    }
  }
}

For Claude Code, change both variable references to ${DENGEL_MCP_URL} and ${DENGEL_MCP_CLIENT_TOKEN} respectively. Use /mcp to check the connection. In Cursor, check the server under MCP in Settings.

Proposal handoff

If your operator enabled /mcp-write, connect using its separate URL and client token. Push the candidate ref first, then call submit with the configured project, candidate ref, full commit id, and registered agent role. The tool opens a proposal only. Use status to read its state and needs_you to inspect the human decision queue. If a response identifies a decision class, routed owner and Decide link, return those details and stop for that person; do not retry, notify, or attempt a decision through MCP.

If the operator binds the proposal surface to a single Git project with dengel_gateway_project, it also offers get_contract and required_evidence, protected_paths, and expected_cost. The gateway reads the approved check contract and path policy from the selected project. The price estimate covers external Guard verification. A formal quote is created only for the actual proposal. The project-scoped surface omits the tenant decision queue and returns empty status for a different project. Public OAuth requires a project-bound identity through the gateway.

First request

Ask the agent to list the Dengel tools, then ask it to use build_receipts for a recent delivery Receipt if your operator enabled access to Build. The receipts tool reports promotion history, which is a separate store. If Dengel reports could not check, ask your operator to check the connection and use the panel to inspect the original evidence. Landing still requires a human decision in Dengel.

See the CLI reference for browser login and command-line receipt lookup, and the Guard quickstart for candidate review.