toolpg_list_triggers
groupWhat changed
endpointhttps://mcp.steadybase.io/mcp
YOUR TRIGGERS FROM THE BOX (Postgres). Every trigger defined for your tenant: TRIGGER_ID, NAME, CRITERIA_TEXT, SCOPE, FILTERS, the signal types the runner mapped the words to, ACTIVE, LAST_RUN_AT, LAST_HIT_AT and HIT_COUNT.
arguments
| include_inactive | boolean | also list paused triggers (default false) |
| limit | integer | max rows (default 100, cap 500) |
install
claude mcp add --transport http steadybase https://mcp.steadybase.io/mcp --header "Authorization: Bearer $STEADYBASE_KEY"
call
curl -s https://api.steadybase.io/v1/mcp/call -H "Authorization: Bearer $STEADYBASE_KEY" -H "Content-Type: application/json" -d '{"tool":"pg_list_triggers"}' contract
| A quote comes with its receipt | Every returned statement carries the verbatim sentence and the URL it came from, and where the source is a transcript, the character offsets inside it. A statement with no receipt is not returned. |
| Empty is an answer | When there is no sourced statement, the skill returns nothing. It does not summarise, infer, or fill the gap from general knowledge. Handle the empty case rather than retrying until something appears. |
| No personal contact data | No email address, phone number, home address or personal social account is returned by any skill, at any tier. A person is a name, a professional role, a LinkedIn profile URL and the public record that puts them in that role. |
| No customer data crosses a key | A tenant-scoped skill reads only that tenant. Nothing about any customer appears on the public site or in another tenant answer. |
steadybase-$