'%20stroke='url(%23em)'/%3e%3cellipse%20cx='30'%20cy='34'%20rx='26'%20ry='20'%20fill='url(%23gm)'/%3e%3cpath%20d='M12.5%2013.00L52.5%2021.74L52.5%2024.33L12.5%2017.60Z'%20fill='url(%23lm)'/%3e%3crect%20x='14.20'%20y='19.29'%20width='6.60'%20height='28.93'%20rx='1.45'%20fill='url(%23cm0)'/%3e%3crect%20x='27.00'%20y='21.24'%20width='5.60'%20height='24.81'%20rx='1.23'%20fill='url(%23cm1)'/%3e%3crect%20x='37.60'%20y='22.85'%20width='4.70'%20height='21.42'%20rx='1.03'%20fill='url(%23cm2)'/%3e%3crect%20x='46.60'%20y='24.22'%20width='4.00'%20height='18.53'%20rx='0.88'%20fill='url(%23cm3)'/%3e%3cpath%20d='M12.5%2050.00L52.5%2042.57L52.5%2044.26L12.5%2053.00Z'%20fill='%237fa3ff'%20opacity='.75'/%3e%3c/svg%3e)
PorticolMoving from Postman
Porticol reads what you already have in Postman. Collections, environments and the scripts in them come across, and the same collections then run in CI and for your coding agents.
Export from Postman
In Postman, export each collection as a Collection v2.1 file and each environment as an environment file. Keep them together in one folder.
Import into Porticol
Choose Import… in the palette and pick the files, several at once if you like. Import them into a new collection, or into an existing one where each file becomes a folder. Before anything is written, a report shows what will be created and anything that couldn't be brought across. See Import.
Scripts and tests
Porticol's scripts use the same pm object as Postman's: variables in every scope, the
request and the response, pm.test and pm.expect for assertions, and
pm.sendRequest. Pre-request and test scripts on the collection, its folders and its
requests run in that order, and console.log writes to the response's Console tab. See
Scripts and tests.
Environments and secrets
Each environment can have a colour, and a protected environment asks you before every send. Secret values stay in your operating system's keychain rather than in the workspace file; see Your data and Shared secrets for sharing them with a team.
Run them in CI
porticol-cli runs a Postman collection file as it is:
porticol-cli run checkout.postman_collection.json -r junit:report.xml
It writes JUnit, JSON and HTML reports and exits with a code your pipeline can act on. See the command line reference.
Give your agents the collections
Add Porticol's MCP server to Claude Code, or any MCP client, and your agent can search the workspace, read requests, send them and run collections, with secrets resolved inside Porticol and masked before anything leaves:
claude mcp add porticol -- porticol-cli mcp
See MCP server.
Going back
Export a collection or folder as a Postman v2.1 collection, and an environment as a Postman environment file, whenever you need them in Postman again. See Export.