Environments
An environment is a named target for Try-It requests: a base URL, request headers and timeouts. This page explains how to create and share environments.
Roles: Any signed-in user with access to the service can create an environment and view the public ones. Editing or deleting needs the creator or an
admin. Only anadmincan open an environment to the MCP server.
Where to find them#
The Environments section of a service page lists the environments. It is collapsed on every page view and loads when you expand it. The section is hidden for AsyncAPI services, which have no Try-It.
Fields#
| Field | Description |
|---|---|
| Name | A label shown in the Try-It list. |
| Base URL | Prepended to the Path field in Try-It. |
| Headers | Name/value pairs merged into Try-It requests. Each header can be marked Sensitive. |
| Timeouts | Connect and response timeouts in seconds, 1–300, default 10. |
| Skip TLS verification | Do not validate the target's certificate. |
| Public | Visible to everyone who can read the service. |
| Available through the MCP server | See below. |
The table can be filtered by name or base URL, by visibility (all, public, private), by whether an environment is available for MCP, and by author. A column shows an MCP badge for environments open to the MCP server.
Visibility#
A private environment is yours: others do not see it on the service page, and it is offered in Try-It only to you. A public environment is visible to everyone who can read the service. An administrator sees all environments on the service page, but a private environment of another user is never offered as a Try-It target, even to an administrator.
A person who cannot manage a row sees a read-only View action. Every row can also be exported (to a Postman collection), by anyone who can see it.
Sensitive headers#
Mark a header as Sensitive when its value is a token or a key. People still see and use the value in the web interface. The MCP server shows it to an AI model only as ******** and removes it from the responses it relays.
Opening an environment to MCP#
An administrator can switch on Available through the MCP server for a public environment. This makes it a possible target of Try-It requests made by AI clients. If anyone else later changes its base URL, TLS setting or headers, the flag switches off until an administrator confirms it again. See Try-It Through MCP.
Exports#
Choosing an environment for a service in the Export Wizard adds curl commands to the exported endpoints. The environment must be visible to you, as in Try-It.