com.mcparmory/postman
PYPI · MCPARMORY-POSTMAN · 2 COMPONENTS · SCANNED SEP 20
Create, organize, and manage API collections, specifications, and team workspaces
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5740 tokens (~104/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Tool Safety93
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 8 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_fork_to_collection" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/postman MCP server?
com.mcparmory/postman runs locally as a PyPI package, launched with uvx mcparmory-postman. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-postman
claude mcp add com-mcparmory-postman -- uvx mcparmory-postman
{
"mcpServers": {
"com-mcparmory-postman": {
"command": "uvx",
"args": [
"mcparmory-postman"
]
}
}
} {
"servers": {
"com-mcparmory-postman": {
"command": "uvx",
"args": [
"mcparmory-postman"
]
}
}
} codex mcp add com-mcparmory-postman -- uvx mcparmory-postman
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-postman": {
"type": "local",
"command": [
"uvx",
"mcparmory-postman"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-postman --command uvx --arg mcparmory-postman
mcp_servers:
com-mcparmory-postman:
command: "uvx"
args: ["mcparmory-postman"] {
"McpServers": {
"com-mcparmory-postman": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-postman"
]
}
}
} assistant mcp add com-mcparmory-postman -t stdio -c uvx -a mcparmory-postman
{
"mcpServers": {
"com-mcparmory-postman": {
"command": "uvx",
"args": [
"mcparmory-postman"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 17 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 11 Sept 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcparmory-postman@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_relations_to_api_version Add Relations to API Version ~175
Link existing Postman entities (collections, environments, mocks, monitors) to an API version as relations. Specify which entity types to associate by providing their corresponding UIDs or IDs in the request body.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API to which relations will be added. |
| apiVersionId | string | yes | The unique identifier of the API version to which relations will be added. |
| contracttest | array | – | Array of Collection UIDs to associate as contract tests with this API version. |
| documentation | array | – | Array of Collection UIDs to associate as documentation with this API version. |
| mock | array | – | Array of Mock IDs to associate with this API version. |
| testsuite | array | – | Array of Collection UIDs to associate as test suites with this API version. |
No output schema declared.
No examples provided.
create_api Create API ~152
Creates a new API with a default API Version. The request must include an `api` object with at least a `name` property, and returns the created API with full details including id, name, summary, and description.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A detailed description of the API's purpose and functionality. |
| name | string | – | The name of the API. This is a required field and must be provided in the request body. |
| summary | string | – | A short summary of the API's purpose. Should be concise and suitable for display in API listings. |
| workspace | string | – | The workspace ID where the API will be created. If not specified, the API is created in the default workspace. |
No output schema declared.
No examples provided.
create_api_version Create API Version ~213
Creates a new API version within the specified API. Optionally copies schema and related resources (mocks, monitors, documentation, tests, etc.) from an existing API version.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API in which to create the new version. |
| documentation | boolean | – | When true, copies the API schema (specification/definition) from the source API version to the new version. |
| id | string | – | The unique identifier of an existing API version to copy configuration and resources from. When specified, the new version will inherit selected schema and relations from this source version. |
| mock | boolean | – | When true, copies mock server configurations from the source API version to the new version. |
| monitor | boolean | – | When true, copies monitoring configurations from the source API version to the new version. |
| name | string | – | The name for the new API version (e.g., '1.0', '2.0-beta'). Required when creating a version from scratch. |
No output schema declared.
No examples provided.
create_collection Create Collection ~144
Create a new Postman collection in Postman Collection v2 format. Returns the created collection's name, ID, and UID. Optionally specify a workspace via query parameter to create the collection in a specific workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A descriptive label for the collection (e.g., 'This is just a sample collection.'). Helps identify the collection's purpose. |
| item | array | – | An array of request items to include in the collection. Items define the API requests and folder structure within the collection. |
| name | string | – | The name of the collection. Supports dynamic variables like {{$randomInt}} for generating unique names. |
| schema | string | – | – |
No output schema declared.
No examples provided.
create_collection_from_schema Create Collection From Schema ~221
Create a new collection linked to an API schema with one or more relation types (contract test, integration test, test suite, or documentation). The collection serves as an organizational container for API-related artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API to which the collection will be linked. |
| apiVersionId | string | yes | The unique identifier of the API version to which the collection will be linked. |
| name | string | – | The display name for the new collection. This is a human-readable identifier for organizing and referencing the collection. |
| relations | array | – | An array of relation types to associate with the collection. Valid relation types are: contracttest, integrationtest, testsuite, and documentation. At least one relation type should be specified to d… |
| schemaId | string | yes | The unique identifier of the schema from which the collection will be created. |
| workspace | string | – | The workspace ID where the collection will be created. Use the workspace identifier to scope the collection to a specific workspace context. |
No output schema declared.
No examples provided.
create_environment Create Environment ~104
Create a new environment with configuration variables. Optionally specify a workspace context via query parameter. Returns the created environment's name and unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The name of the environment to create. Must be between 1 and 254 characters long. |
| values | array | – | An array of environment variables to initialize with the environment. Each variable must have a key and value; the enabled flag is optional. Up to 100 variables can be specified per environment. |
No output schema declared.
No examples provided.
create_fork_of_collection Create Fork of Collection ~135
Create a fork of an existing collection. The response includes the forked collection's name, ID, UID, and fork metadata. You can optionally specify a target workspace for the fork. Note: The fork is created with a default label 'Forked Collection' (Postman v10 API requires 'label', and the schema-declared 'name' field is rejected).
| Name | Type | Req | Description |
|---|---|---|---|
| collection_uid | string | yes | The unique identifier of the collection to fork. |
| workspace | string | – | The ID of the workspace where the forked collection should be created. If not specified, the fork will be created in the default workspace. |
No output schema declared.
No examples provided.
create_mock Create Mock ~102
Create a mock server for a collection, optionally resolving environment variables. You can specify a workspace context via query parameter to determine where the mock is created.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | The unique identifier of the collection for which to create the mock. Format is a UUID string. |
| environment | string | – | The unique identifier of an environment to use for resolving variables within the collection. Format is a UUID string. If provided, environment variables will be substituted in the mock. |
No output schema declared.
No examples provided.
create_monitor Create Monitor ~230
Create a new monitor that runs API tests on a specified schedule. The monitor will execute a Postman collection in a given environment at intervals defined by a cron expression and timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | The unique identifier of the Postman collection to monitor. This collection contains the API tests that will be executed on schedule. |
| cron | string | – | A cron expression defining the monitor's execution schedule (e.g., '*/5 * * * *' for every 5 minutes, '0 17 * * *' for daily at 5pm). Only limited schedules are supported; check Postman Monitors for… |
| environment | string | – | The unique identifier of the Postman environment to use when running the monitor. This provides variables and configuration for the collection execution. |
| name | string | – | A descriptive name for the monitor to help identify it in your workspace. |
| timezone | string | – | The timezone for interpreting the cron schedule (e.g., 'Asia/Kolkata', 'America/New_York'). Use IANA timezone database format. Defaults to UTC if not specified. |
No output schema declared.
No examples provided.
create_schema Create Schema ~165
Creates a new schema for an API version. The schema can be defined in OpenAPI (v1, v2, v3), RAML, or GraphQL format with corresponding language specification.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API to which the schema will be added. |
| apiVersionId | string | yes | The unique identifier of the API version under which the schema will be created. |
| language | string | – | The schema language format. Use 'json' or 'yaml' for OpenAPI and RAML schemas; use 'graphql' exclusively for GraphQL schemas. |
| type | string | – | The schema type specification. Supported types are 'openapi3', 'openapi2', 'openapi1', 'raml', and 'graphql'. |
No output schema declared.
No examples provided.
create_webhook Create Webhook ~127
Create a webhook that automatically triggers a specified collection when the webhook URL is called. The webhook URL is returned in the response for use in external systems.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | The ID of the collection that will be triggered when this webhook is invoked. This determines which collection executes when the webhook URL is called. |
| name | string | – | A descriptive name for the webhook to help identify its purpose and distinguish it from other webhooks in your workspace. |
| workspace | string | – | The workspace ID where the webhook will be created. Required to scope the webhook to the correct workspace context. |
No output schema declared.
No examples provided.
create_workspace Create Workspace ~199
Create a new workspace and optionally populate it with collections, environments, mocks, and monitors by their unique identifiers. Returns the created workspace name and ID.
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | – | Array of collection UIDs to include in the workspace. Order is preserved as provided. |
| description | string | – | A descriptive text for the workspace to explain its purpose or contents. |
| environments | array | – | Array of environment UIDs to include in the workspace. Order is preserved as provided. |
| mocks | array | – | Array of mock server UIDs to include in the workspace. Order is preserved as provided. |
| monitors | array | – | Array of monitor UIDs to include in the workspace. Order is preserved as provided. |
| name | string | – | The display name for the workspace. Use a descriptive name that identifies the workspace purpose or project. |
| type | string | – | The workspace type, such as 'personal' for individual workspaces or other organizational types. |
No output schema declared.
No examples provided.
delete_api Delete API ~44
Permanently deletes an API by its ID. Returns the deleted API object with its ID for confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API to delete. |
No output schema declared.
No examples provided.
delete_api_version Delete API Version ~63
Permanently deletes a specific API version. Returns the id of the deleted API version.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API containing the version to delete. |
| apiVersionId | string | yes | The unique identifier of the API version to delete. |
No output schema declared.
No examples provided.
delete_collection Delete Collection ~58
Permanently delete a collection by its unique identifier. Returns the deleted collection's id and uid upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_uid | string | yes | The unique identifier of the collection to delete. This identifier is required to specify which collection should be removed. |
No output schema declared.
No examples provided.
delete_environment Delete Environment ~56
Permanently delete a single environment by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uid | string | yes | The unique identifier of the environment to delete. This is a required string value that uniquely identifies the environment within the system. |
No output schema declared.
No examples provided.
delete_mock Delete Mock ~59
Permanently delete an existing mock by its unique identifier. This operation removes the mock and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| mock_uid | string | yes | The unique identifier of the mock to delete. This is a required string value that identifies which mock should be removed. |
No output schema declared.
No examples provided.
delete_mock_publication Delete Mock Publication ~67
Unpublish a mock by its unique identifier. This removes the mock from published state, making it unavailable for use.
| Name | Type | Req | Description |
|---|---|---|---|
| mock_uid | string | yes | The unique identifier of the mock to unpublish. This is a required string value that identifies which mock should be removed from published state. |
No output schema declared.
No examples provided.
delete_monitor Delete Monitor ~58
Permanently delete an existing monitor by its unique identifier. This operation removes the monitor and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_uid | string | yes | The unique identifier of the monitor to delete. This is a required string value that identifies which monitor to remove. |
No output schema declared.
No examples provided.
delete_workspace Delete Workspace ~57
Permanently delete an existing workspace by its ID. Returns the ID of the deleted workspace upon successful completion.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | yes | The unique identifier of the workspace to delete. This ID is required to specify which workspace should be removed. |
No output schema declared.
No examples provided.
get_api Get API ~46
Retrieve detailed information about a specific API by its ID, including metadata such as name, summary, and description.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API to retrieve. |
No output schema declared.
No examples provided.
get_api_version Get API Version ~62
Retrieve detailed information about a specific API version, including its configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API containing the version to retrieve. |
| apiVersionId | string | yes | The unique identifier of the specific API version to fetch. |
No output schema declared.
No examples provided.
get_authenticated_user Get Authenticated User ~47
Retrieve detailed information about the authenticated user, including username, full name, email address, and other profile data. Requires API Key authentication via X-Api-Key header or apikey query parameter.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_collection Get Collection ~67
Retrieve the full contents of a specific collection by its unique identifier. You must have access permissions to the collection to retrieve it.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_uid | string | yes | The unique identifier (uid) of the collection to retrieve. This is a required string value that uniquely identifies the collection within the system. |
No output schema declared.
No examples provided.
get_documentation_relations Get Documentation Relations ~75
Retrieves all documentation relations linked to a specific API version, organized by relation type with complete details for each relation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to fetch documentation relations. |
| apiVersionId | string | yes | The unique identifier of the API version for which to fetch documentation relations. |
No output schema declared.
No examples provided.
get_environment Get Environment ~60
Retrieve the full contents of a specific environment by its unique identifier. This operation requires authentication via API Key.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uid | string | yes | The unique identifier of the environment to retrieve. This is a required string value that identifies which environment's contents to access. |
No output schema declared.
No examples provided.
get_environment_relations_for_api_version Get Environment Relations for API Version ~78
Retrieves all environment relations linked to a specific API version, organized by relation type with complete details for each relation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to retrieve environment relations. |
| apiVersionId | string | yes | The unique identifier of the specific API version for which to retrieve environment relations. |
No output schema declared.
No examples provided.
get_mock Get Mock ~65
Retrieve detailed information about a specific mock by its unique identifier. Requires API Key authentication via X-Api-Key header or apikey query parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| mock_uid | string | yes | The unique identifier of the mock to retrieve. This is a required string value that uniquely identifies the mock resource. |
No output schema declared.
No examples provided.
get_monitor Get Monitor ~59
Retrieve detailed information about a specific monitor using its unique identifier. This operation requires authentication via API key.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_uid | string | yes | The unique identifier of the monitor to retrieve. This is a required string value that uniquely identifies the monitor in the system. |
No output schema declared.
No examples provided.
get_schema Get Schema ~85
Retrieves a single schema by its ID. Returns a schema object containing metadata including id, language, type, and schema definition.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API containing the schema. |
| apiVersionId | string | yes | The unique identifier of the API version containing the schema. |
| schemaId | string | yes | The unique identifier of the schema to retrieve. |
No output schema declared.
No examples provided.
get_workspace Get Workspace ~60
Retrieve a workspace by its ID, including all associated collections, environments, mocks, and monitors that you have access to.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | yes | The unique identifier of the workspace to retrieve. Must be a valid workspace ID that you have access to. |
No output schema declared.
No examples provided.
list_api_versions List API Versions ~44
Retrieve all versions of a specified API, including detailed metadata for each version.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to retrieve all versions. |
No output schema declared.
No examples provided.
list_apis List APIs ~312
Retrieve all APIs in a workspace with optional filtering by metadata, timestamps, privacy state, and text search. Results can be sorted by any response field in ascending or descending order.
| Name | Type | Req | Description |
|---|---|---|---|
| createdBy | string | – | Filter results to APIs created by a specific user. Provide the user ID. |
| description | string | – | Filter results to APIs whose description contains this value. Matching is case-insensitive. |
| direction | string | – | Set sort order to ascending (asc) or descending (desc). Defaults to descending for timestamps and numeric fields, ascending otherwise. |
| isPublic | string | – | Filter results by privacy state: use true for public APIs or false for private APIs. |
| name | string | – | Filter results to APIs whose name contains this value. Matching is case-insensitive. |
| since | string | – | Filter results to APIs updated on or after this timestamp. Use ISO 8601 date-time format. |
| sort | string | – | Sort results by a specific field name from the response. Combine with direction parameter to control sort order. |
| summary | string | – | Filter results to APIs whose summary contains this value. Matching is case-insensitive. |
| until | string | – | Filter results to APIs updated on or before this timestamp. Use ISO 8601 date-time format. |
| updatedBy | string | – | Filter results to APIs last updated by a specific user. Provide the user ID. |
| workspace | string | – | Filter results to APIs within a specific workspace. Provide the workspace ID to scope the query. |
No output schema declared.
No examples provided.
list_collections List Collections ~40
Retrieve all collections accessible to you, including your own collections and those you have subscribed to. Each collection includes its name, ID, owner, and UID.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_contract_test_relations List Contract Test Relations ~79
Retrieves all contract test relations linked to a specific API version, organized by relation type with complete details for each relation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to fetch contract test relations. |
| apiVersionId | string | yes | The unique identifier of the specific API version for which to fetch contract test relations. |
No output schema declared.
No examples provided.
list_environments List Environments ~35
Retrieve a list of all environments you own, including their names, IDs, owners, and UIDs. Requires API Key authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_integration_test_relations List Integration Test Relations ~79
Retrieves all integration test relations linked to a specific API version, organized by relation type with complete details for each relation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to fetch integration test relations. |
| apiVersionId | string | yes | The unique identifier of the API version for which to fetch integration test relations. |
No output schema declared.
No examples provided.
list_linked_relations List Linked Relations ~75
Retrieve all relations linked to a specific API version, including detailed information about each relation type and its associated relations.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to retrieve linked relations. |
| apiVersionId | string | yes | The unique identifier of the API version for which to retrieve linked relations. |
No output schema declared.
No examples provided.
list_mocks List Mocks ~31
Retrieve all mocks you have created. Returns a complete list of your mock configurations for managing and testing API responses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_monitor_relations List Monitor Relations ~68
Retrieves all monitor relations linked to a specific API version, organized by relation type with complete details for each relation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API. |
| apiVersionId | string | yes | The unique identifier of the API version for which to fetch monitor relations. |
No output schema declared.
No examples provided.
list_monitors List Monitors ~36
Retrieve a list of all monitors accessible to you, including their name, ID, owner, and unique identifier. Requires API Key authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_test_suite_relations List Test Suite Relations ~78
Retrieves all test suite relations linked to a specific API version, organized by relation type with complete details for each relation.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API for which to retrieve test suite relations. |
| apiVersionId | string | yes | The unique identifier of the API version for which to retrieve test suite relations. |
No output schema declared.
No examples provided.
list_workspaces List Workspaces ~43
Retrieve a list of all workspaces accessible to you, including your own workspaces and those shared with you. Each workspace entry includes its name, ID, and type.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
merge_fork_to_collection Merge Fork to Collection ~154
Merge a forked collection back into its destination collection. Optionally specify a merge strategy to control whether the source fork is deleted or updated with destination changes after the merge.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | The UID of the destination collection where the fork will be merged into. Required for the merge operation. |
| source | string | – | The UID of the forked collection to merge. This is the source collection that will be merged into the destination. |
| strategy | string | – | The merge strategy to apply: `deleteSource` removes the forked collection after merging, or `updateSourceWithDestination` syncs the forked collection with any changes made to the destination. Default… |
No output schema declared.
No examples provided.
publish_mock Publish Mock ~66
Publishes a mock that you have created, making it available for use. Requires the mock's unique identifier (uid) and API key authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| mock_uid | string | yes | The unique identifier of the mock to publish. This is the uid assigned to the mock when it was created. |
No output schema declared.
No examples provided.
run_monitor Run Monitor ~51
Executes a monitor immediately and waits for completion, returning the run results. This is a synchronous operation that blocks until the monitor finishes executing.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_uid | string | yes | The unique identifier of the monitor to execute. |
No output schema declared.
No examples provided.
sync_relation_with_schema Sync Relation with Schema ~135
Synchronize a relation (such as documentation, contract test, or monitor) with the current API schema to ensure consistency and alignment with schema changes.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API containing the relation to synchronize. |
| apiVersionId | string | yes | The unique identifier of the specific API version whose schema will be used for synchronization. |
| entityId | string | yes | The unique identifier of the specific relation instance to synchronize with the schema. |
| entityType | string | yes | The type of relation to sync, such as documentation, contracttest, integrationtest, testsuite, mock, or monitor. |
No output schema declared.
No examples provided.
update_api Update API ~98
Update an existing API by modifying its name, summary, or description. Returns the complete updated API object with all current details.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API to update. |
| description | string | – | The updated description for the API. Provide a clear, concise explanation of what the API does. |
| name | string | – | The updated name for the API. Use a descriptive title that identifies the API's purpose. |
No output schema declared.
No examples provided.
update_api_version Update API Version ~105
Update the name of an existing API version. Provide the API ID and version ID, along with the new name in the request body.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API containing the version to update. |
| apiVersionId | string | yes | The unique identifier of the API version to update. |
| name | string | – | The new name for the API version (e.g., '2.0'). This is the only field that can be updated. |
No output schema declared.
No examples provided.
update_collection Update Collection ~195
Replace an existing collection with updated content in Postman Collection v2 format. Returns the updated collection's name, id, and uid. Requires API Key authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_uid | string | yes | The unique identifier of the collection to update. This is a required path parameter that specifies which collection will be replaced. |
| description | string | – | A text description of the collection's purpose and contents. Supports dynamic variables in the format. |
| item | array | – | An array of request items and folders that comprise the collection. Items are processed in the order provided and define the collection's structure and endpoints. |
| name | string | – | The display name of the collection. Supports dynamic variables (e.g., {{$randomInt}}) for generating unique names. |
| postman_id | string | – | The Postman internal identifier for the collection, typically a UUID format. Used to maintain collection identity across systems. |
| schema | string | – | – |
No output schema declared.
No examples provided.
What is the com.mcparmory/postman MCP server?
com.mcparmory/postman is an MCP server listed in the public MCP registry as com.mcparmory/postman. Create, organize, and manage API collections, specifications, and team workspaces. This page covers its PyPI package (mcparmory-postman).
Is the com.mcparmory/postman MCP server safe to use?
com.mcparmory/postman scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/postman MCP server expose?
com.mcparmory/postman exposes 55 tools: list_apis, create_api, get_api, update_api, delete_api, and 50 more. Their descriptions and schemas cost roughly 5,740 tokens of context every time the server is loaded.
Is the com.mcparmory/postman MCP server still maintained?
com.mcparmory/postman is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.