v3.0.0-beta.1

Pre-release of v3.0.0: Outpost support, write mode for the Gateway MCP server, and a rename of the Gateway MCP tools.

npm install -g hookdeck-cli@beta

If you use the Gateway MCP server, read this first

Every Gateway product tool is renamed from hookdeck_* to gateway_*, and the events and requests tools are each split in two. Per-tool permission grants and allowedTools entries do not survive a rename — whatever you had approved for hookdeck_events is not approved for gateway_events, so you will be asked to grant again, and any allowedTools config needs updating by hand.

Before	After
hookdeck_attempts	gateway_attempts
hookdeck_connections	gateway_connections
hookdeck_destinations	gateway_destinations
hookdeck_events	gateway_events (list) and gateway_event (by id)
hookdeck_help	gateway_help
hookdeck_issues	gateway_issues
hookdeck_metrics	gateway_metrics
hookdeck_requests	gateway_requests (list) and gateway_request (by id)
hookdeck_sources	gateway_sources
hookdeck_transformations	gateway_transformations

hookdeck_login and hookdeck_projects keep their names — they are platform tools shared with the Outpost server.

If you have rules or hooks matching on tool names, prefer a server-scoped pattern such as mcp__hookdeck__* over naming individual tools, so a future rename does not break them again.

What to test

• Upgrade path: install, restart your MCP client, re-grant permissions, confirm existing workflows still work
• Write mode: --allow-write (or HOOKDECK_MCP_ALLOW_WRITE), then gateway_event retry — and confirm no write action is offered without it
• Outpost: the hookdeck outpost … tree and hookdeck outpost mcp
• Non-webhook destinations: creating an AWS, GCP, Azure, RabbitMQ or Kafka destination — the config is validated against each type's published schema, so tell us if a create is rejected or stores something other than what you passed

What is new

• Outpost support — tenants, destinations, destination types, events, attempts, topics, config, metrics, publishing and deployment status, plus an MCP server.
• Write mode for the Gateway MCP server — 28 write actions across connections, sources, destinations, transformations, events, requests and issues, off by default behind --allow-write. pause/unpause stay available in read-only mode, because read-only is the mode people investigate incidents in.
• New filters on events and requests, on both the MCP tools and the CLI: search_term, next_attempt_at, delivery_group, events_count, ignored_count, cli_events_count, attempts.

Fixes

Around thirty. Most are cases where a command told you it had done something it had not:

• event cancel and event mute printed the new state and exited 0 on an event that had already been delivered, where nothing had changed
• outpost destination enable and disable reported the action you asked for rather than the state the destination ended up in
• outpost event retry printed a success tick even when the retry was declined
• transformation run printed an empty result instead of an error when your code threw, returned nothing, or failed to parse
• a list filter you passed could be ignored, so you got every result back with nothing to indicate the filter had not been applied
• Outpost destinations were created without TLS even though the destination type documents it as on by default, which meant credentials could go out in the clear
• --help printed your API key when it was set in the environment
• a resource id containing a path separator could act on a different resource than the one you named
• gateway destination update accepted --url and changed nothing unless you also passed --type
• outpost publish --data '{}' failed with "data is required" for a payload you had supplied

If you have scripts that check exit codes or parse output, this is the release to run them against.

Known gaps in this beta

• Invalid Outpost metric filter dimensions are accepted and ignored, so a typo in --filter can return unfiltered data. Being fixed before GA.
• CLI error messages currently go to stdout rather than stderr, so --output json is not machine-safe on a failure path. Under discussion for GA in #367.

Please report anything you find at https://github.com/hookdeck/hookdeck-cli/issues — a beta is only worth cutting if the problems come back to us.

Full Changelog: v2.5.0...v3.0.0-beta.1