Skip to content
HookWatch beta
FeaturesUse casesPricingQuickstartSecurityCompare
Resources
Resources overviewGuidesIntegrationsComparisonsChangelogDocumentationMCP server
Sign in Start beta
Changelog v1.17.0 New

MCP server and HTTP API docs

The whole workspace API is exposed as roughly 48 MCP tools for AI assistants, alongside new public documentation for the HTTP API and MCP.

Published 1 min read
On this page

An AI assistant can now read and act on your workspace through the same API the dashboard uses. This release exposes that API as MCP tools and documents both the HTTP surface and the MCP one.

Added

  • MCP server — the entire workspace API is exposed as roughly 48 Model Context Protocol tools, each proxying one API route and handing the JSON response straight to the model. Two paths reach the same tool table: a local stdio server via hookwatch mcp, and a remote Streamable HTTP endpoint. Both authenticate with a workspace API key (hwk_…) — no session, no separate credential.
  • HTTP API documentation — a public API reference with worked curl examples, and an MCP page describing the tools, the two transports, and how they authenticate.

Improved

  • The API contract was audited against the running server and several drift bugs were corrected, so the documented behaviour matches what the API actually does.

Notes

Release date comes from the v1.17.0 git tag (22 July 2026). The tool table is identical across the CLI’s stdio server and the remote HTTP server.

Related resources

Changelog v1.18.0 Workspace SSO and inactivity timeout Single sign-on through your own SAML 2.0 or OIDC identity provider, with an optional Require SSO enforcement and a session inactivity timeout. 1 min read Changelog v1.19.0 Overage pricing on metered usage Paid plans can now run past their included usage with metered overage, with projected charges surfaced in billing settings before they land. 1 min read Changelog v1.14.0 Usage metering, pay-as-you-go, and entitlements Per-unit usage metering on an idempotent ledger, pay-as-you-go and subscription billing with overage and spending limits, and a general entitlements layer. 2 min read
Get started

See what happened to every webhook.

HookWatch keeps the request, the response, and every attempt for each delivery — so the debugging, retry, and replay steps in this article are a matter of reading, not reconstructing.

Start using HookWatch Read the documentation