Loading...
Postmancer is a standalone MCP server for AI assistants to interact with RESTful APIs, enabling HTTP requests, API collection management, and response testing.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Postmancer is a standalone MCP server for AI assistants to interact with RESTful APIs, enabling HTTP requests, API collection management, and response testing.
Postmancer's safety depends heavily on configuration and the APIs it interacts with. It's relatively safe if used with well-defined, non-destructive APIs and strong encryption. However, it becomes risky when used with APIs that allow data modification or deletion, especially without proper access controls and key management.
Performance depends on the network latency and API response times. Large collections may take longer to load.
Cost depends on the usage of the APIs being accessed. Consider API rate limits and pricing models.
npm install -g{
"mcpServers": {
"postmancer": {
"command": "npx",
"args": ["-y", "postmancer"],
"env": {
"LOG_LEVEL": "info"
}
}
}
}http_requestSends HTTP requests to any specified URL.
Can be used to access or modify data on any accessible API endpoint.
list_collectionsLists all saved API collections.
Read-only operation that does not modify any data.
list_requestsLists all requests within a specific collection.
Read-only operation that does not modify any data.
save_requestSaves a new request to a specified collection.
Adds data to a collection, but does not directly impact external systems.
request_from_collectionExecutes a saved request from a specified collection.
Executes a pre-defined HTTP request, potentially modifying data.
set_environment_variableSets an environment variable for use in request templates.
Modifies the environment, potentially affecting future requests.
get_environment_variablesRetrieves all currently set environment variables.
Read-only operation that does not modify any data.
Environment Variable
cloud
Postmancer's safety depends heavily on configuration and the APIs it interacts with. It's relatively safe if used with well-defined, non-destructive APIs and strong encryption. However, it becomes risky when used with APIs that allow data modification or deletion, especially without proper access controls and key management.
Autonomy is limited only by the permissions of the APIs Postmancer interacts with. There are no built-in safeguards to prevent unintended actions.
Production Tip
Always set strong encryption keys and carefully manage API access credentials in production environments.
Set the `POSTMANCER_ENCRYPTION_KEY` and `ENCRYPTION_KEY` environment variables to strong, randomly generated secrets.
By default, collections are stored in `~/.postmancer`. You can change this with the `COLLECTIONS_PATH` environment variable.
Set environment variables using the `set_environment_variable` tool, then reference them in your requests using `{{variable_name}}` syntax.
Yes, Postmancer supports OAuth2 authentication. Configure the necessary parameters in your request settings.
Yes, as long as the Postmancer server has network access to the internal APIs.
If installed globally with npm, use `npm update -g postmancer`. If using npx, it will automatically use the latest version.
You can set the `LOG_LEVEL` environment variable to `debug`, `info`, `warn`, or `error`.