Update to Postman

{
  "name": "postman-mcp-server",
  "description": "Postman concepts and MCP tool guidance. Loaded when working with Postman MCP tools to make better decisions about tool selection and workarounds.",
  "included_files": [
    {
      "relative_path": "references/docs.md",
      "size_in_bytes": 3869
    },
    {
      "relative_path": "references/learn.md",
      "size_in_bytes": 4750
    },
    {
      "relative_path": "references/mcp-limitations.md",
      "size_in_bytes": 1704
    },
    {
      "relative_path": "references/mock.md",
      "size_in_bytes": 4205
    },
    {
      "relative_path": "references/search.md",
      "size_in_bytes": 3955
    },
    {
      "relative_path": "references/security.md",
      "size_in_bytes": 4979
    },
    {
      "relative_path": "references/setup.md",
      "size_in_bytes": 5579
    },
    {
      "relative_path": "references/sync.md",
      "size_in_bytes": 4545
    },
    {
      "relative_path": "references/test.md",
      "size_in_bytes": 3332
    }
  ],
  "skill_md_contents": "---\nname: postman-mcp-server\ndescription: Postman concepts and MCP tool guidance. Loaded when working with Postman MCP tools to make better decisions about tool selection and workarounds.\nuser-invocable: false\n---\n\n# Postman Knowledge\n\nReference for Postman concepts and MCP tool selection. Use this context when working with Postman MCP tools to make better decisions.\n\nSee `references/setup.md` for how to to setup postman mcp server and auth.\n\n## Core Concepts\n\n- **Collection:** A group of API requests organized in folders. The primary unit of work in Postman. Contains requests, examples, tests, and documentation.\n- **Environment:** Key-value pairs (variables) scoped to a context (dev, staging, prod). Used to swap base URLs, auth tokens, and config without changing requests.\n- **Workspace:** Container for collections, environments, and specs. Can be personal, team, or public.\n- **Spec (Spec Hub):** An OpenAPI or AsyncAPI definition stored in Postman. Can generate collections and stay synced.\n- **Request:** A single API call definition (method, URL, headers, body, tests).\n- **Response:** A saved example response for a request. Used by mock servers and documentation.\n- **Folder:** A grouping within a collection, typically by resource (e.g., \"Users\", \"Orders\").\n- **Tags:** Labels on collections for categorization and search.\n- **Monitor:** A scheduled collection runner that checks API health.\n- **Mock Server:** A fake API that serves example responses from a collection.\n\n## Decision Guide\n\n| Goal | Approach |\n|------|----------|\n| Push code changes to Postman | Create/update spec in Spec Hub, then sync to collection |\n| Consume a Postman API | Read collection + generate client code |\n| Find an API | Use `searchPostmanElements`, then drill into details |\n| Test an API | Run collection with `runCollection` |\n| Create a fake API for frontend | Create mock server from collection with examples |\n| Document an API | Analyze collection completeness, fill gaps, optionally publish |\n| Audit API security | Run security checks against spec or collection |\n| Learn how to use a Postman feature | Search Postman docs with `searchLearningCenter` (Full mode) |\n\n## MCP Tool Selection\n\n**Workspace operations:** `getWorkspaces`, `getWorkspace`, `createWorkspace`\n**Collection CRUD:** `getCollections`, `getCollection`, `createCollection`, `putCollection`, `patchCollection`, `deleteCollection`\n**Request/Response:** `getCollectionRequest`, `createCollectionRequest`, `updateCollectionRequest`, `getCollectionResponse`, `createCollectionResponse`, `updateCollectionResponse`\n**Folder management:** `getCollectionFolder`, `createCollectionFolder`, `updateCollectionFolder`\n**Spec Hub:** `getAllSpecs`, `getSpec`, `createSpec`, `getSpecDefinition`, `updateSpecFile`, `getSpecFiles`\n**Sync:** `generateCollection`, `syncCollectionWithSpec`, `syncSpecWithCollection`\n**Environments:** `getEnvironments`, `getEnvironment`, `createEnvironment`, `putEnvironment`\n**Mocks:** `getMocks`, `getMock`, `createMock`, `publishMock`, `unpublishMock`\n**Tests:** `runCollection`\n**Docs:** `publishDocumentation`, `unpublishDocumentation`\n**Search:** `searchPostmanElements` , `getTaggedEntities`\n**Learning Center:** `searchLearningCenter` (Full mode only — searches Postman product docs for how-to guidance)\n**User:** `getAuthenticatedUser`\n\nSee `references/mcp-limitations.md` for known limitations and workarounds.\n\n## Workflows\n\nEach reference below is a full MCP-tool workflow for one goal — the tool\ncall sequence, what to present at each step, and error handling. Reach for\none once the Decision Guide above has picked a goal; they assume MCP tools\nonly, no `postman` CLI.\n\n- `references/setup.md` — first-run auth (OAuth or API key) and workspace verification.\n- `references/search.md` — discover APIs across workspaces with `searchPostmanElements`.\n- `references/sync.md` — create/update collections from specs, or sync a spec from collection changes.\n- `references/mock.md` — create a mock server from a collection or spec.\n- `references/test.md` — run collection tests and diagnose failures.\n- `references/docs.md` — generate, improve, and publish API documentation.\n- `references/security.md` — audit a spec or collection against the OWASP API Top 10.\n- `references/learn.md` — search the Postman Learning Center for how-to guidance.\n"
}