postmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTMCP_FILE_ROOTS | No | Directories that local file tools can access. Defaults to the project directory. | |
| POSTMCP_MAX_FILE_BYTES | No | Maximum allowed file size in bytes for local file reads. Default is 10 MiB (10485760), maximum 100 MiB. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_usage_guideA | Read the instructions and workflow guidelines for LLM agents to use this MCP server effectively (explains variables, interpolation, chaining, and websockets). |
| project_createB | Create a new API testing project workspace. |
| project_switchC | Switch active project workspace. |
| project_listB | List all project workspaces in the database. |
| project_deleteA | Delete a project workspace (cascades and deletes its environments, credentials, and test history). |
| project_renameC | Rename an existing project workspace. |
| env_configureB | Configure or create an environment profile (e.g. dev, prod) inside the active project. Saves credentials directly into the local SQLite DB. |
| env_switchB | Switch active environment within the project workspace. |
| env_listA | List all environments configured under the active project. |
| env_deleteC | Delete an environment profile. |
| env_set_variableB | Set a variable key-value pair inside the active environment configuration. |
| env_get_variableC | Get the value of a specific variable from the active environment. |
| env_delete_variableB | Delete a variable from the active environment configuration. |
| env_list_variablesB | List all variables defined in the active environment. |
| env_renameC | Rename an existing environment profile. |
| env_set_allowlistA | Configure explicit target domains allowed for outgoing requests. Empty denies all. Use private:host only for trusted internal hosts. |
| env_get_allowlistB | Get the current URL allowlist configuration. |
| http_requestA | Send a RESTful HTTP request. Automatically injects credentials and cookies from the active environment. Evaluates assertions and logs request/response details to history database. |
| ws_connectA | Open a persistent WebSocket connection, backed by headers and cookies from active environment. Returns connectionId. |
| ws_sendC | Send a text or JSON frame down a WebSocket connection. |
| ws_readB | Read the latest buffered messages. Can wait for specific regex pattern to arrive. |
| ws_closeC | Close connection. |
| ws_listB | List active socket connection IDs. |
| history_listB | List previous request-response audit records stored in the SQLite database. |
| history_getA | Retrieve details of a specific request audit log by ID. |
| history_compareB | Compare two request executions, checking metrics and structural JSON response body differences. |
| history_clearB | Delete logs from history table. |
| test_run_suiteB | Execute multiple sequential REST requests, extract dynamic fields to active environment variables, run assertions, and output a testing Markdown report. |
| db_statusA | Get statistics about the local SQLite database, including database file path, file size, and row counts of all tables. |
| db_resetA | DANGER: Factory reset the SQLite database. Closes database, deletes the database file, and recreates a fresh blank schema with a DefaultProject. |
| swagger_importA | Import API routes and schemas from a local Swagger/OpenAPI file or remote URL, outputting a structured Markdown API Reference. |
| graphql_requestB | Send a GraphQL query/mutation to a GraphQL endpoint. Automatically injects credentials and variables. |
| suite_saveB | Save or update a named test suite in the database under the active project. |
| suite_loadC | Load a saved test suite by ID and execute it immediately. |
| suite_listA | List all saved test suites under the active project. |
| suite_deleteC | Delete a saved test suite. |
| history_exportB | Export request history as a JSON array. |
| env_exportC | Export an environment configuration as a portable JSON object. |
| env_importC | Import an environment configuration from a portable JSON object. |
| project_exportC | Export a project (including all its environments) as a portable JSON object. |
| project_importC | Import a project (including all its environments) from a portable JSON object. |
| postman_importB | Import a Postman Collection v2 JSON file, generating a structured Markdown API reference. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 42 tools
Tools are grouped by clear resource prefixes (project_, env_, ws_, history_, suite_, db_) plus dedicated protocol tools (http_request, graphql_request), so most selections are unambiguous. The main overlap is test_run_suite vs suite_load (which also executes immediately) and env_configure vs env_set_variable, but descriptions distinguish these adequately.
The dominant convention is resource_action (project_create, env_set_variable, ws_connect, history_compare, suite_save), applied consistently across nearly all tools. Minor deviations like mcp_usage_guide and test_run_suite break the pattern slightly but remain readable and predictable.
42 tools is heavy for what is essentially an API-testing client, and the surface exceeds the 25-tool threshold where each tool clearly earns its place. Several clusters (five env variable tools, five ws tools, five history tools, four suite tools) could be consolidated without losing capability.
Coverage is strong across the domain: full project and environment lifecycles, import/export, WebSocket sessions, history audit/compare, and saved suites. The main gap is the absence of standalone named-request CRUD outside suites, so reusable single requests can only live in a suite.