get_hogwarts_staffLABSCO 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 APIget_characters_in_house— characters from a specific Hogwarts house, taking ahouseparameterget_hogwarts_studentsandget_hogwarts_staff— the two staff and student rostersfetch_spells— spells from the Harry Potter APIfetch_octocats— Octocats from GitHub's Octodex APInode 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
USE CASES
01
Seeing how a Postman collection becomes MCP tools
List the generated tools with their parameters and open the matching file to see how each one is wired.
02
Testing an MCP client end to end
Connect a server whose tools always work and need no credentials, to confirm the client side is configured correctly.
03
Trying the SSE transport
Run the same server over Server-Sent Events, in Docker or locally, to compare with the stdio path.
6 tools
Listed in project docs. Your client may show a different list.
fetch_spellsget_hogwarts_studentsget_characters_in_houseget_all_charactersfetch_octocatsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
docker on PATH
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
docker run -i --rm --env-file=.env octocat-hp-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"octocat-hp-mcp-server-local": {
"command": "<YOUR_ABSOLUTE_PATH_TO_NODE>",
"args": [
"<YOUR_ABSOLUTE_PATH_TO_MCP_SERVER>"
]
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"octocat-hp-mcp-server-docker": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--env-file=.env",
"octocat-hp-mcp-server"
]
}
}
}
