post_v1_pubsub_jetstream_streams_stream_consumers
CreateConsumer creates a durable consumer on one stream and returns it.
CreateConsumer creates a durable consumer on one stream and returns it. A consumer is a named cursor: it tracks what has been delivered and what is acknowledged, so many workers can share it and none sees a message twice outside redelivery. 409 when the stream already has a consumer of that name with a different configuration.
| Tool | post_v1_pubsub_jetstream_streams_stream_consumers |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 7 |
| Operation | POST /v1/pubsub/jetstream/streams/{stream}/consumers |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
ack | string | — | — | — | — |
ackWait | integer | — | — | — | — |
deliver | string | — | — | — | — |
filter | string | — | — | — | — |
maxDeliver | integer | — | — | — | — |
name | string | — | — | — | Name is the durable consumer name: 1–64 of [A-Za-z0-9_-]. |
stream | string | — | — | — | Stream is the stream to consume, from the path. |
tools/list declares a type and a description for each field and nothing further. 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_pubsub_jetstream_streams_stream_consumers",
"arguments": {
"ack": "<ack>",
"ackWait": 0,
"deliver": "<deliver>",
"filter": "<filter>",
"maxDeliver": 0,
"name": "<name>",
"stream": "<stream>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. ackWait and maxDeliver 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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_post_v1_pubsub_jetstream_streams_stream_consumers | POST /v1/pubsub/jetstream/streams/{stream}/consumers | cloud | CreateConsumer creates a durable consumer on one stream and returns it. |
The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?