Documentation menu

Publishing, domains and production controls

On this page

Check production capacity and configuration before publishing. Code publication and a running production website are different actions.

Use these tools

  1. Call the relevant read or status tool first.
  2. Review the target and required arguments.
  3. Run one intended action, with explicit human confirmation where required.
  4. Inspect status or re-read the affected resource afterward.

Inputs below describe the public contract. Your connected server’s current tool list is authoritative. Some tools require a particular host, target, inference mode or plan. Identifiers are values returned by earlier tools; do not invent them.

production_status

The project’s published production site.

Read the returned resource and use its current values when planning the next action.

ArgumentRequiredType or accepted values

| projectId | No | string |

Operation: read-only.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

publish_production

Publish the project as its production site.

Requires eligible production capacity. Review settings, sign-in and legal pages before confirming publication.

ArgumentRequiredType or accepted values

| projectId | No | string |

| confirm | Yes | boolean |

Operation: can change state or start work; destructive effects are possible.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

production_control

Restart or stop the production site.

Operates the production site. Stopping it can interrupt users; verify the project and action.

ArgumentRequiredType or accepted values

| projectId | No | string |

| action | Yes | restart, stop |

Operation: can change state or start work; destructive effects are possible.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

custom_domain

Attach, verify or detach a custom domain.

Use the action enum in the schema. Follow returned DNS instructions and verify the domain before treating it as active.

ArgumentRequiredType or accepted values

| projectId | No | string |

| action | Yes | attach, verify, detach |

| domain | No | string; minLength 4; maxLength 253 |

Operation: can change state or start work.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

production_auth

The production site’s standalone sign-in.

Read the returned resource and use its current values when planning the next action.

ArgumentRequiredType or accepted values

| projectId | No | string |

Operation: read-only.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

set_production_redirects

Set the standalone sign-in’s redirect addresses.

Only add intended sign-in return addresses. Review their domains and test the production login flow.

ArgumentRequiredType or accepted values

| projectId | No | string |

| redirects | Yes | array of string |

Operation: can change state or start work.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

list_slots

The organization’s workloads.

Lists the account’s application workloads exposed by the public interface. Use production_status for a particular site.

Arguments: none ({}).

Operation: read-only.

Available setups: stdio, cloud project, cloud inference; stdio, cloud project, delegated inference; stdio, local project, cloud inference; stdio, local project, delegated inference; hosted HTTP.

The machine-readable tool contracts include nested argument schemas.

MCP home · Recovery workflow · Costs