Postmancer MCP Server

An experimental MCP server Rest Client intended to be a replacement of tools postman & insomnia

Local serverstdio

What is the Postmancer MCP server?

An experimental MCP server Rest Client intended to be a replacement of tools postman & insomnia. That is what the postmancer mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A standalone MCP server for API testing and management, allowing AI assistants to interact with RESTful APIs through natural language.

Postmancer is an MCP (Model Context Protocol) server that enables AI assistants like Claude to make HTTP requests, manage collections of API endpoints, and test API responses. It provides similar functionality to tools like Postman or Insomnia but designed specifically for AI assistants.

  • Make HTTP requests to any REST API
  • Save and organize requests in collections
  • Set and use environment variables with variable substitution
  • Multiple authentication methods (Basic, Bearer, API Key, OAuth2)
  • Request/response history and testing

Getting it running

Installation goes through your MCP client rather than a global install: point it at npx on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Installation — The Installation tool exposed by this server

What it needs from you

Configuration is passed through the environment: LOG_LEVEL, COLLECTIONS_PATH, POSTMANCER_ENCRYPTION_KEY, ENCRYPTION_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Postmancer's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by hijaz; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.

How to install the Postmancer MCP server

{
  "mcpServers": {
    "postmancer": {
      "command": "npx",
      "args": ["-y", "npx"],
      "env": {
        "LOG_LEVEL": "your-value",
        "COLLECTIONS_PATH": "your-value",
        "POSTMANCER_ENCRYPTION_KEY": "your-value",
        "ENCRYPTION_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LOG_LEVELConfiguration value read at startup.Optional
COLLECTIONS_PATHFilesystem location the server is allowed to use.Optional
POSTMANCER_ENCRYPTION_KEYCredential the server authenticates with.Yes
ENCRYPTION_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Postmancer to Installation.

Frequently asked questions

Postmancer allows AI assistants to make HTTP requests, manage API endpoint collections, and test API responses, functioning like a Postman for AI agents.