Postman Tool Generation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTMAN_API_KEY | Yes | Your Postman API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_ai_toolB | Generate code for an AI agent tool using a Postman collection and request |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.
One tool is too few for the server's stated purpose of 'Postman Tool Generation,' which implies a broader scope like generating, managing, or testing tools. A single generation tool feels thin and incomplete for this domain.
The tool surface is severely incomplete for the inferred domain of Postman-based tool generation. There are obvious gaps, such as no tools for listing, editing, deleting, or testing generated tools, which limits agent workflows to a single action.