Hanzo
Cloud MCPmq

post_v1_mq_streams_stream_consumers

Creates a durable pull consumer on a stream and returns it.

Creates a durable pull consumer on a stream and returns it.

Toolpost_v1_mq_streams_stream_consumers
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments12
OperationPOST /v1/mq/streams/{stream}/consumers
Productmq

Arguments

FieldTypeRequiredDefaultValuesDescription
ack_policystring
ack_waitstring
deliver_policystring
descriptionstring
durable_namestring
filter_subjectstring
max_ack_pendinginteger
max_deliverinteger
opt_start_seqinteger
opt_start_timestringdate-time
replay_policystring
streamstringStream is the stream name, from the path.

tools/list declares a type and a description for each field and nothing further. The Values column is taken from POST /v1/mq/streams/{stream}/consumers, the operation this tool dispatches to — the same declaration the REST API validates against. A means neither the door nor that operation constrains the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "post_v1_mq_streams_stream_consumers",
         "arguments": {
           "ack_policy": "<ack_policy>",
           "ack_wait": "<ack_wait>",
           "deliver_policy": "<deliver_policy>",
           "description": "<description>",
           "durable_name": "<durable_name>",
           "filter_subject": "<filter_subject>",
           "max_ack_pending": 0,
           "max_deliver": 0,
           "opt_start_seq": 0,
           "opt_start_time": "2026-01-01T00:00:00Z",
           "replay_policy": "<replay_policy>",
           "stream": "<stream>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. max_ack_pending, max_deliver, opt_start_seq and opt_start_time hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

OperationRouteProductSummary
post_v1_mq_streams_stream_consumersPOST /v1/mq/streams/{stream}/consumersmqCreates a durable pull consumer on a stream and returns it.

The same capability over plain HTTP is in the mq API reference, on https://api.hanzo.ai.


All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page