Skip to main content
Postman has a native MCP request type — it speaks the protocol directly and shows raw request/response data, with no AI model or chat layer in the way. That makes it the most direct way to confirm Perfai Cloud itself is healthy, independent of whichever AI client you eventually use day to day. Perfai Cloud connects as a remote streamable-http server.
Unlike every other page in this section, there’s no AI assistant here to type natural-language prompts into. You call each Perfai tool directly from Postman’s Tools tab, filling in its arguments yourself.

Get an API key

Perfai Cloud authenticates Postman with a Perfai API key. Create one and copy it — Perfai shows the full key only once. You’ll paste it into Postman’s Authorization tab as the Bearer token value.

Installation

  1. In any Postman workspace, click Add → MCP.
  2. Set the transport: choose HTTP (Postman’s label for Streamable HTTP).
  3. URL: https://mcp-server.perfai.ai/mcp
  4. Open the Authorization tab → Auth Type: Bearer Token → paste your API key.
  5. Click Run to connect.

Verify the server is connected

  1. A valid key gets you a green Connected status immediately after clicking Run — the handshake doesn’t require you to already be logged into a Perfai account, only to send a valid key.
  2. Open the Tools tab and confirm all 19 tools are listed.
  3. If it fails, re-check the key for trailing whitespace. A 401 means the key has expired or been revoked — create a new one and paste it into the Authorization tab.
The API key also signs you in: every tool runs as the user who created the key, with that user’s organizations and role. There is no separate login step.

Confirm you’re signed in

In the Tools tab, run auth_status. It shows the key’s id (pfk_xxxxxxxxxxxx_…), never the secret.

Register an app and run a scan

Run each of these from the Tools tab, filling in arguments as needed:
  1. register_app — set appUrl to https://your-app.example.com.
  2. check_app_status — run repeatedly until registrationStatus is COMPLETED. If it returns NEEDS_INPUT with reason needs_login, that’s the target app’s own login, not your Perfai account — supply it via submit_app_credentials.
  3. run_security_test — returns a taskId.
  4. check_task_status — run with that taskId until it reports COMPLETED.
  5. get_vulnerabilities — lists findings with sequence numbers, used in the fix tools below.

Fix and verify

  1. auto_fix_all — returns a prioritized, critical-first fix plan. Postman won’t apply these changes for you; copy the instructions into your editor by hand.
  2. mark_vulnerability_fixed — run once per finding, after the corresponding code change is actually made.
  3. get_fix_summary — confirms the fixed/unfixed/dismissed counts moved as expected.
  4. logout, then auth_status again — confirms the session actually cleared.