mcp.hjlabs.in

Home / Servers / DigitalOcean API / harness_post_trigger_webhook

ReceiveTriggerWebhook accepts a signed delivery from an external system.

An MCP tool from the DigitalOcean API server, hosted on mcp.hjlabs.in.

ReceiveTriggerWebhook accepts a signed delivery from an external system. The one public, un-team-authenticated endpoint. There is NO DO bearer token: the caller is the customer's external system. Authentication is the per-trigger HMAC secret, verified on every delivery… [POST /v2/agents/triggers/{trigger_id}/webhook]

Name on the gateway: digitalocean_api__harness_post_trigger_webhook · may change things.

Parameters

NameTypeDescription
trigger_id requiredstringThe trigger UUID.

How to call it

Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:

call_tool arguments
{
  "name": "digitalocean_api__harness_post_trigger_webhook",
  "arguments": {
    "trigger_id": "…"
  }
}

Or connect the DigitalOcean API server directly, which lists 874 tools including this one:

Run in your terminal
claude mcp add --transport http hj-digitalocean-api https://mcp.hjlabs.in/mcp/digitalocean-api \
  --header "Authorization: Bearer YOUR_API_KEY"

Try asking

Use the receivetriggerwebhook accepts a signed delivery from an external system. tool with trigger_id set to ….

More from DigitalOcean API