gateway
Manage MCP gateways (the agent-core-gateway service).
Gateways are asynchronous resources. create, update, and delete
return immediately with the resource in a transitional state and converge in
the background. The lifecycle FSM is WAITING_CREATING → CREATING → ACTIVE
(and WAITING_UPDATING → UPDATING → ACTIVE, WAITING_DELETING → DELETING →
DELETED); failures land in a terminal *_ERROR state (CREATE_ERROR,
UPDATE_ERROR, ERROR, ERROR_DELETING). Use wait to block until a
terminal state.
Available commands
| Command | Description |
|---|---|
| create | Create a new MCP gateway |
| generate | Print a gateway create template (YAML or JSON) |
| list | List gateways |
| get | Show a gateway |
| update | Update a gateway's mutable fields |
| delete | Delete a gateway |
| wait | Wait for a gateway to reach a terminal state |
Sub-resource groups
| Group | Commands |
|---|---|
| flavors | list |
| access-logs | list · stats |
| inbound-auth | jwt idp-app set · jwt idp-app clear |
| private-network | routes get · routes set |
| service-account | repair |
Recommended workflow for complex specs
Gateway creation exposes many nested, mutually-exclusive fields (targets,
outboundAuth, inboundAuth/JWT, privateNetwork) that cannot all be expressed as
flags. For anything beyond the simple path, generate a template, fill it in, and
apply it with --file: