Summary
The local display is the point: the assistant sets what is shown, and can read the same state back.
fetch-pokemon resolves a name or a number and puts the result on a page served locally, and get-current-pokemon reads that state back, which makes the pair a shared surface between the model and a screen rather than a dataset you would query in bulk. What these calls cover is the type of the fetched Pokemon and whatever the current view holds — there is no search, no filtering and no listing.
What it is
A small server over Pokemon lookups that renders what it fetches on localhost, where fetch-pokemon accepts a name or a number and get-current-pokemon reads back what is showing.
What you get
- Fetch-pokemon takes a pokemon value as either a number or a name and displays its type on localhost.
- Get-current-pokemon returns information about the Pokemon currently displayed, and takes no parameters.
Requirements
Nothing — no account, no key.
Setup effort
One command — pokemon-mcp-server