palugada-postman-api

name	palugada-postman-api
description	TRIGGER when the user asks about their Postman collections, saved API requests, endpoints, environments, or wants a curl for an existing request — use the postman-bridge MCP (offline-first).

Postman collections (offline-first)

The postman-bridge MCP server reads Postman data from local exports, app backups, and an on-disk API cache — all zero-cost. The Postman API (free plan ≈ 300 calls/month, every endpoint counts) is only the fallback. Workflow:

1. postman_sources — free; shows what exists locally + budget + key status.
2. postman_find_requests / postman_get_collection — free; browse requests (folder path, method, URL) across everything on disk.
3. postman_get_request — free; full headers/body/scripts + a ready-to-run curl, with {{variables}} resolved via environment=<name> (secret values stay masked unless reveal_secrets=true).
4. Collection only in the cloud? postman_list_collections refresh=true (1 call) then postman_get_collection <uid> (1 call — cached forever after).
5. postman_quota shows the remaining monthly budget.

Prefer asking the user to export a collection into ~/.palugada/postman-mcp/collections/ over spending API budget when the budget is low.