Summary

The generator's output, with two APIs that need no keys.

As a workshop artefact it does exactly the right thing: the APIs are trivial, so nothing distracts from the mechanism — how a Postman request becomes a tool file, how the tool list is assembled, and how the same server runs over stdio, SSE or Docker. Read it as a template to copy rather than a data source to depend on.

What it is

A teaching example produced by the Postman Agent Generator in MCP server mode. Each selected Postman request became a JavaScript tool file, and `mcpServer.js` exposes them over MCP — so it demonstrates the path from an existing API collection to a working server, using two APIs that need no credentials.

What you get

`get_all_characters` — every character from the Harry Potter API
`get_characters_in_house` — characters from a specific Hogwarts house, taking a `house` parameter
`get_hogwarts_students` and `get_hogwarts_staff` — the two staff and student rosters
`fetch_spells` — spells from the Harry Potter API
`fetch_octocats` — Octocats from GitHub's Octodex API
`node index.js tools` — list every generated tool with its description and parameters, which is how you inspect what a generated server actually exposes

Requirements

Nothing for these two APIs — no key is needed for the Octocat and Harry Potter endpoints. Node.js v16 or higher (v20 or higher recommended) and npm; `npm install` from a clone, then point your client at `node` and the absolute path to `mcpServer.js`. A Dockerfile is included, and `node mcpServer.js --sse` serves it over Server-Sent Events instead, which the Docker run maps to port 9000. Generated tools read a per-workspace API key from `.env` where the API needs one, which these do not.

Setup effort

One command — docker run -i --rm --env-file=.env octocat-hp-mcp-server