Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ENV_FILENoPath to a Postman environment export or flat JSON object supplied via `--env` to resolve collection variables.
CMCP_VAR_<name>NoProcess environment variable used to resolve a collection variable, e.g. CMCP_VAR_baseUrl=...; optional and useful for keeping secrets out of the collection file.
COLLECTION_PATHYesPath to the Postman collection JSON file to expose as an MCP server; positional argument to `cmcp serve`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
auth_digest_digestauth_requestA

Performing a simple GET request to this endpoint returns status code 401 Unauthorized with WWW-Authenticate header containing information to successfully authenticate subsequent requests. The WWW-Authenticate header must be processed to extract realm and nonce values to hash subsequent requests.

When this request is executed within Postman, the script attached with this request does the hard work of extracting realm and nonce from the header and set it as global variables named echo_digest_nonce and echo_digest_realm. These variables are re-used in subsequent request for seamless integration of the two requests.

(Postman request: Auth: Digest/DigestAuth Request | GET https://postman-echo.com/digest-auth)

auth_digest_digestauth_successA

This endpoint sends a hashed Digest Authorization header to gain access to a valid 200 Ok response code. In Postman, it uses the stored global variables, echo_digest_realm and echo_digest_nonce, to generate the hashed authorisation header.

Within Postman, for this request to successfully authenticate, running the previous request "DigestAuth Request" stores the relevant information within the global variables.

(Postman request: Auth: Digest/DigestAuth Success | GET https://postman-echo.com/digest-auth)

auth_others_basic_authA

This endpoint simulates a basic-auth protected endpoint. The endpoint accepts a default username and password and returns a status code of 200 ok only if the same is provided. Otherwise it will return a status code 401 unauthorized.

Username: postman

Password: password

To use this endpoint, send a request with the header Authorization: Basic cG9zdG1hbjpwYXNzd29yZA==. The cryptic latter half of the header value is a base64 encoded concatenation of the default username and password. Using Postman, to send this request, you can simply fill in the username and password in the "Authorization" tab and Postman will do the rest for you.

To know more about basic authentication, refer to the Basic Access Authentication wikipedia article. The article on authentication helpers elaborates how to use the same within the Postman app.

(Postman request: Auth: Others/Basic Auth | GET https://postman-echo.com/basic-auth)

auth_others_oauth1_0_verify_signatureA

OAuth1.0a is a specification that defines a protocol that can be used by one service to access "protected" resources (endpoints) on another service. A major part of OAuth1.0 is HTTP Request Signing. This endpoint allows you to check whether the request calculation works properly in the client.

The endpoint supports the HTTP Authorization header. In case the signature verification fails, the endpoint provides the four debug values,

  • base_uri

  • normalized_param_string

  • base_string

  • signing_key

For more details about these parameters, check the OAuth1.0a Specification

In order to use this endpoint, you can set the following values:

Consumer Key: RKCGzna7bv9YD57c

Consumer Secret: D+EdQ-gs$-%@2Nu7

If you are using Postman, also check the "Add params to header" and "Auto add parameters" boxes.

(Postman request: Auth: Others/OAuth1.0 Verify Signature | GET https://postman-echo.com/oauth1)

cookies_set_cookiesA

The cookie setter endpoint accepts a list of cookies and their values as part of URL parameters of a GET request. These cookies are saved and can be subsequently retrieved or deleted. The response of this request returns a JSON with all cookies listed.

To set your own set of cookies, simply replace the URL parameters "foo1=bar1&foo2=bar2" with your own set of key-value pairs.

(Postman request: Cookies/Set Cookies | GET https://postman-echo.com/cookies/set)

cookies_get_cookiesA

Use this endpoint to get a list of all cookies that are stored with respect to this domain. Whatever key-value pairs that has been previously set by calling the "Set Cookies" endpoint, will be returned as response JSON.

(Postman request: Cookies/Get Cookies | GET https://postman-echo.com/cookies)

cookies_delete_cookiesB

One or more cookies that has been set for this domain can be deleted by providing the cookie names as part of the URL parameter. The response of this request is a JSON containing the list of currently set cookies.

(Postman request: Cookies/Delete Cookies | GET https://postman-echo.com/cookies/delete)

headers_request_headersB

A GET request to this endpoint returns the list of all request headers as part of the response JSON. In Postman, sending your own set of headers through the Headers tab will reveal the headers as part of the response.

(Postman request: Headers/Request Headers | GET https://postman-echo.com/headers)

headers_response_headersA

This endpoint causes the server to send custom set of response headers. Providing header values as part of the URL parameters of a GET request to this endpoint returns the same as part of response header.

To send your own set of headers, simply add or replace the the URL parameters with your own set.

(Postman request: Headers/Response Headers | GET https://postman-echo.com/response-headers)

request_methods_get_requestB

The HTTP GET request method is meant to retrieve data from a server. The data is identified by a unique URI (Uniform Resource Identifier).

A GET request can pass parameters to the server using "Query String Parameters". For example, in the following request,

http://example.com/hi/there?hand=wave

The parameter "hand" has the value "wave".

This endpoint echoes the HTTP headers, request parameters and the complete URI requested.

(Postman request: Request Methods/GET Request | GET https://postman-echo.com/get)

request_methods_post_requestB

The HTTP POST request method is meant to transfer data to a server (and elicit a response). What data is returned depends on the implementation of the server.

A POST request can pass parameters to the server using "Query String Parameters", as well as the Request Body. For example, in the following request,

POST /hi/there?hand=wave

The parameter "hand" has the value "wave". The request body can be in multiple formats. These formats are defined by the MIME type of the request. The MIME Type can be set using the Content-Type HTTP header. The most commonly used MIME types are:

  • multipart/form-data

  • application/x-www-form-urlencoded

  • application/json

This endpoint echoes the HTTP headers, request parameters, the contents of the request body and the complete URI requested.

(Postman request: Request Methods/POST Request | POST https://postman-echo.com/post)

request_methods_put_requestC

The HTTP PUT request method is similar to HTTP POST. It too is meant to transfer data to a server (and elicit a response). What data is returned depends on the implementation of the server.

A PUT request can pass parameters to the server using "Query String Parameters", as well as the Request Body. For example, in the following raw HTTP request,

PUT /hi/there?hand=wave

(Postman request: Request Methods/PUT Request | PUT https://postman-echo.com/put)

request_methods_patch_requestC

The HTTP PATCH method is used to update resources on a server. The exact use of PATCH requests depends on the server in question. There are a number of server implementations which handle PATCH differently. Technically, PATCH supports both Query String parameters and a Request Body.

This endpoint accepts an HTTP PATCH request and provides debug information such as the HTTP headers, Query String arguments, and the Request Body.

(Postman request: Request Methods/PATCH Request | PATCH https://postman-echo.com/patch)

request_methods_delete_requestB

The HTTP DELETE method is used to delete resources on a server. The exact use of DELETE requests depends on the server implementation. In general, DELETE requests support both, Query String parameters as well as a Request Body.

This endpoint accepts an HTTP DELETE request and provides debug information such as the HTTP headers, Query String arguments, and the Request Body.

(Postman request: Request Methods/DELETE Request | DELETE https://postman-echo.com/delete)

utilities_response_status_codeC

This endpoint allows one to instruct the server which status code to respond with.

Every response is accompanied by a status code. The status code provides a summary of the nature of response sent by the server. For example, a status code of 200 means everything is okay with the response and a code of 404 implies that the requested URL does not exist on server. A list of all valid HTTP status code can be found at the List of Status Codes wikipedia article. When using Postman, the response status code is described for easy reference.

Note that if an invalid status code is requested to be sent, the server returns a status code of 400 Bad Request.

(Postman request: Utilities/Response Status Code | GET https://postman-echo.com/status/200)

utilities_streamed_responseA

This endpoint allows one to receive streaming http response using chunked transfer encoding of a configurable length.

A streaming response does not wait for the entire response to be generated on server before flushing it out. This implies that for a fairly large response, parts of it can be streamed to the requestee as and when it is generated on server. The client can then take actions of processing this partially received data.

(Postman request: Utilities/Streamed Response | GET https://postman-echo.com/stream/10)

utilities_delay_responseB

Using this endpoint one can configure how long it takes for the server to come back with a response. Appending a number to the URL defines the time (in seconds) the server will wait before responding.

Note that a maximum delay of 10 seconds is accepted by the server.

(Postman request: Utilities/Delay Response | GET https://postman-echo.com/delay/3)

utilities_get_utf8_encoded_responseA

If a response of an endpoint requires to send data beyond the basic English / ASCII character set, the charset parameter in the Content-Type response header defines the character encoding policy.

This endpoint returns an UTF8 character encoded response body with text in various languages such as Greek, Latin, East Asian, etc. Postman can interpret the character encoding and use appropriate methods to display the character set in responses.

(Postman request: Utilities/Get UTF8 Encoded Response | GET https://postman-echo.com/encoding/utf8)

utilities_gzip_compressed_responseA

This endpoint returns the response using gzip compression algorithm. The uncompressed response is a JSON string containing the details of the request sent by the client. For this endpoint to work, one should request with Accept-encoding header containing gzip as part of its value. Postman supports gzip, deflate and SDCH decoding and automatically sends them as part of the request.

HTTP Compression allows the server to send responses in a compressed format, which is uncompressed by the client before processing. This reduces network bandwidth consumption at the cost of increase in CPU usage. To know more about this, refer the HTTP Compression wikipedia article.

(Postman request: Utilities/GZip Compressed Response | GET https://postman-echo.com/gzip)

utilities_deflate_compressed_responseA

This endpoint returns the response using deflate compression algorithm. The uncompressed response is a JSON string containing the details of the request sent by the client. For this endpoint to work, one should request with Accept-encoding header containing deflate as part of its value. Postman supports gzip, deflate and SDCH decoding and automatically sends them as part of the request.

HTTP Compression allows the server to send responses in a compressed format, which is uncompressed by the client before processing. This reduces network bandwidth consumption at the cost of increase in CPU usage. To know more about this, refer the HTTP Compression wikipedia article.

(Postman request: Utilities/Deflate Compressed Response | GET https://postman-echo.com/deflate)

draft_auth_oauth2_0_oauth2_0_get_access_tokenA

This endpoint is used to get the access_token

It requires the following secret client credentials to be sent as part of the form body along with the authentication code obtained as part of the redirect_uri from the previous request.

code: xWnkliVQJURqB2x1

grant_type: authorization_code

redirect_uri: https://www.getpostman.com/oauth2/callback

client_id: abc123

client_secret: ssh-secret

If the correct credentials are not passed, the server returns with a 401 Unauthorized response.

(Postman request: [draft] Auth: OAuth2.0/OAuth2.0 Get Access Token | POST https://postman-echo.com/oauth2/token)

draft_auth_oauth2_0_oauth2_0_get_resourceC

Once the bearer token has been obtained, it can be passed as Authorization header to access user's resources.

Authorization: Bearer vp7jx...

If the Authorization header is not passed the endpoint returns 401 Unauthorized.

(Postman request: [draft] Auth: OAuth2.0/OAuth2.0 Get Resource | GET https://postman-echo.com/oauth2/user/info)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 22 tools

Disambiguation4/5

Most tools map to a single, distinct postman-echo endpoint, so an agent can generally pick the right one (cookies get/set/delete, each HTTP method, each auth flavor). The main soft spot is the pair headers_request_headers vs headers_response_headers, whose descriptions are easy to invert, and the two-step digest pair requires understanding that digestauth_request must precede digestauth_success. Otherwise boundaries are clear.

Naming Consistency3/5

Names follow a rough category_prefix_action scheme, but the verb is inconsistently present (cookies_get_cookies vs auth_others_basic_auth vs headers_request_headers) and the oauth2 draft tools suffer from stuttering redundancy (draft_auth_oauth2_0_oauth2_0_get_access_token). It is readable and prefix-grouped, but not a predictable verb_noun pattern throughout.

Tool Count3/5

22 tools is on the heavy side for what is essentially a mirror of the postman-echo demo endpoint collection. Several tools are near-duplicates in spirit (gzip vs deflate, the digest two-step, two separate OAuth1/OAuth2 groups), which inflates the count beyond what a typical agent workflow needs.

Completeness4/5

The surface covers HTTP methods (GET/POST/PUT/PATCH/DELETE), cookie lifecycle, header echo/injection, and basic/digest/OAuth1/OAuth2 auth plus compression, streaming, delay and encoding utilities — a solid lifecycle for an echo service. Gaps are minor: no HEAD/OPTIONS, no /ip, /uuid, /json, /xml, or /image endpoints, and the digest flow depends on Postman global-variable state an MCP agent cannot easily carry across calls.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues