Skip to main content
The Verdikt MCP server lets coding agents open cert windows, post signals, and read gate decisions without leaving the IDE.

​
Prerequisites

  • API key (vdk_live_…) from Settings → Agent access
  • Workspace ID from Settings → General
  • Node.js 18+

​
1. Get the MCP server

Clone the Verdikt repo (or use your existing checkout) and install MCP deps once: 
git clone https://github.com/useverdikt/Verdikt.git
cd Verdikt/mcp
npm install
Note the absolute path to mcp/src/index.js — you will reference it in config.

​
2. Cursor config

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project): 
{
  "mcpServers": {
    "verdikt": {
      "command": "node",
      "args": ["/absolute/path/to/Verdikt/mcp/src/index.js"],
      "env": {
        "VERDIKT_API_URL": "https://api.useverdikt.com",
        "VERDIKT_API_KEY": "vdk_live_…",
        "VERDIKT_WORKSPACE_ID": "ws_…"
      }
    }
  }
}
Replace the path and secrets with your values. For local API dev, set VERDIKT_API_URL to http://127.0.0.1:8787. Restart Cursor after saving.

​
3. Optional Cursor rule

Copy the Verdikt agent rule from the repo (.cursor/rules/verdikt.mdc) into your project so the agent knows when to call check_gate and post_signals.

​
Tools available

ToolPurpose
create_releaseOpen cert window (pass commit_sha, pr_number, repo metadata)
post_signalsSubmit signal values for a release
get_verdictRead status, blocking signals, intelligence
check_gateMerge decision — read action: merge | self_heal | escalate
check_gate_by_shaSame gate lookup by PR commit SHA
escalateHand off to human when blocked
record_outcomePost-deploy calibration

​
Agent loop (read action, not exit code alone)

actionBehavior
mergeCertified — merge/deploy allowed
self_healMissing signals or still collecting — fix and re-post
escalateThreshold failure — call escalate, wait for human override
Use mode: strict when only pure CERTIFIED (no override) should pass.

​
Typical PR flow

  1. Agent opens or updates a PR.
  2. Apply label verdikt:rc (or create_release with commit SHA + repo metadata).
  3. Integrations auto-pull; agent post_signals only for metrics CI produces locally.
  4. check_gate or check_gate_by_sha — act on action.
  5. GHA gate workflow + branch protection enforce merge even if the agent misbehaves.

​
Session tracking

MCP sends X-Verdikt-Agent-Session on every request. Audit events for one agent run share the same session ID in the Verdikt audit trail.