Getting started
From install to your first MCP tool call — step by step.
Fourteen short steps. Each one says what you do, where you click and what you will see. After the first requests everything runs on your own machine — no account, no API key, no tokens spent.
The plan
Fourteen steps, each one a few minutes.
You need Testnizer 1.6.0 and an internet connection for steps 2–4 (they call httpbin.org). Everything from step 7 on talks to servers that Testnizer itself runs on 127.0.0.1.
01 / 14Install
Install Testnizer and create a project.
Download the build for your system from testnizer.com/download, install it and open it. Then create the project this training works in.
- Home
- New Project
- Create New
Petstore- Create
An empty project. The rail on the left: APIs, Tests, Mocks, History, Tools, Security and Settings at the bottom. No sign-up screen — there is no account.
~/Library/Application Support/Testnizer/%APPDATA%\Testnizer\~/.config/Testnizer/02 / 14First request
Send your first request.
Open an HTTP tab, call a public echo service, read the answer — then save it with Ctrl/Cmd S into a new folder called httpbin.
- + New
- HTTP
- GET
https://httpbin.org/get- Send
Status, time and size above the response, the JSON body and the headers. The Console (Ctrl/Cmd Alt C) shows the raw request and response.
{ "args": {}, "headers": { "Accept": "*/*", "Host": "httpbin.org", "User-Agent": "Testnizer/1.6.0" }, "url": "https://httpbin.org/get" }
03 / 14Environments
Put the host and the token in an environment.
Create an environment with baseUrl = https://httpbin.org and token = sk-demo-1234 (type secret), make it active, and change the URL to {{baseUrl}}/get.
- environment selector, right end of the tab bar
- Manage Environments
- New Environment
- Add Variable
- Set Active
The same response as before — the variable is resolved when you send. The secret is masked in History and the Console, encrypted on disk where the OS has a keychain, and left out of Git commits and exports.
- staging
- Globals
04 / 14Authorization
Send a bearer token — once, for the whole folder.
Set the token on the httpbin folder, then add a request to {{baseUrl}}/bearer in that folder whose auth is Inherit from parent.
- right-click the folder
- Settings
- Authorization
- Bearer Token
{{token}}
200 with "authenticated": true. Remove the token and the same call answers 401. The nearest setting wins: request, then folder, then project.
{ "authenticated": true, "token": "sk-demo-1234" }
05 / 14Scripts and tests
Make the request check its own answer.
On the /bearer request, write two pm.test checks — or add them without code as assertions. Postman scripts run as they are.
- Scripts
- Post-response
- or
- Tests
- + Add Assertion
After Send, the response's Test Results tab lists each check as passed or failed. The same script behaves the same in the Runner.
1pm.test('status is 200', () => { 2 pm.response.to.have.status(200) 3}) 4pm.test('token accepted', () => { 5 pm.expect(pm.response.json().authenticated).to.be.true 6})
06 / 14Runner
Run the whole folder and keep the report.
Save both requests (Ctrl/Cmd S), then run the httpbin folder in one go and export the result as a single HTML file.
- right-click the folder
- Run
- Start run
- Export HTML
One row per request with its status, time and tests, a passed / failed total, and a report you can open in any browser — credentials masked. Iterations, data files, Setup and Teardown are on the same screen.
07 / 14Mock server
Start a mock API on your own machine.
Create an HTTP mock from the ready-made REST example — a small Users API — start it and call it from a request tab.
- Mocks
- New mock server
- HTTP
- REST example
- Create
- Start & open in request tab
The server on http://127.0.0.1:3001. GET /users/2 answers a user, /users/7 answers 404. Every call appears in the mock's Logs tab. A saved folder can become a mock too: right-click → Create Mock Server from this folder.
- GET/usersList users
- GET/users/:idids 1–3 exist, others 404
- POST/users201
- DELETE/users/:id204
08 / 14MCP
Start an MCP server and connect to it.
Create an MCP mock from the Echo preset — one echo tool that returns its text — and open it in an MCP tab, already filled in.
- Mocks
- New mock server
- MCP
- Echo
- Start & open in MCP tab
- Connect
Streamable HTTP to http://127.0.0.1:3100/mcp, the negotiated protocol version, the server's name, and the Tools tab with echo. Under Messages, Frames shows the handshake as raw JSON-RPC.
- ƒechoreturns its text argument
09 / 14Tool call
Call the tool, then save the call with a test.
Fill the text argument from the form Testnizer builds out of the tool's schema, run it, and save the call so it can run again in the Runner.
- Tools
echotext: hello- Run
- Ctrl/Cmd S
The result with hello in its content, the time it took, and a tools/call pair in Frames. A post-response test can read it through pm.mcp.
{ "content": [{ "type": "text", "text": "hello" }] }
1pm.test('echo answers', () => { 2 pm.expect(pm.mcp.isError).to.equal(false) 3 pm.expect(pm.mcp.content[0].text).to.equal('hello') 4})
10 / 14Security scan
Scan the server and read the report.
Run the security scan against the Echo server you are connected to. It is your own server on your own machine, so you are allowed to test it.
- Security
- Scan
- open a finding
- Save HTML report…
A grade from A to F, a score out of 100 and the checks by category — each with its evidence. Plain HTTP on 127.0.0.1 is only noted. Rate-limit checks need Include active probes, which is off by default. Your grade depends on the server's settings.
11 / 14AI Chat
Let a model call your tool — and approve it.
Start an AI mock with the Tool call round-trip preset — it plays a model that asks for a tool. Give the chat the Echo call you saved in step 9 and send a prompt. No provider key is used.
- New mock server
- AI
- Tool call round-trip
- Start & open in AI Chat tab
- Add a saved MCP request…
- Load tools
- Allow once
An approval card with the tool and its arguments before anything runs — approval is on by default, “Run tools without asking” lasts for this tab only. Then the tool result, the reply and its time and token counts.
12 / 14Import
Bring a Postman collection in, scripts and all.
Import a collection exported from Postman — a v1, v2.0, v2.1 or v3 file, a v3 Native Git folder, an environment or a .zip. The version is read from the file.
- Ctrl/Cmd O
- Postman
- choose the file
- or
- Import folder…
A report of what came in, what was skipped and what could not be carried — for example Kafka and Postman Data requests in a v3 collection are skipped. Collection auth lands on the folder; requests inherit it.
13 / 14GIT
Share the project through your Git repository.
Connect the project to a repository and push it. A teammate picks it up with Clone from Git on the New Project screen and pulls your later changes.
- Settings
- Storage
- Save Mode: Git
- branch menu
- Commit…
- Commit and push
The changed requests, environments and suites to commit. Your token goes out empty — after a pull your teammate sees how many secrets to fill in. Scripts in the cloned project wait until they allow them.
14 / 14Shortcuts and tips
Ten keys that save you the most clicks.
Paste a cURL into the URL bar
It becomes a full request — method, headers, body, auth. One Undo puts the text back.
Generate Code — 36 variants
Turn the open request into code for your language. Secret variables stay as {{name}} unless you choose to include them.
118 dynamic variables
{{$randomEmail}}, {{$guid}}, {{$timestamp}} … — the same names as Postman.
What's next
Go deeper — the docs pick up from here.
That's the tour. Now try it on your own API.
Questions and bug reports: github.com/apinizer/testnizer/issues