gyazo_image
Fetch image content and metadata from Gyazo
LABSCO SUMMARY
Screenshots stop being things you paste and start being things you can look up.
Gyazo already holds every capture you took; full-text search is what turns that pile into something an agent can retrieve from, and upload closes the loop when the agent produces an image of its own. Organising is not part of the deal — no albums, no deletion, no editing metadata after the fact.
What it is
A four-tool server over the Gyazo API: full-text search across your uploads, capture retrieval with metadata, and upload.
What you get
- Full-text search across the captures uploaded to the account, up to 100 results a page
- Any capture fetched by its id or its Gyazo URL, image content and metadata together
- The most recent upload fetched without needing to know its id first
- New images uploaded with a title, description, referer URL and originating app
Requirements
GYAZO_ACCESS_TOKEN — search and the latest-upload lookup both run against the captures belonging to that token.
Setup effort
One command plus a key — npx @notainc/gyazo-mcp-server, then supply credentials
USE CASES
01
Finding the screenshot you took of that error last month
Search the library for the words that were on screen, then pull the matching capture with its metadata so the model is looking at the image rather than your recollection of it.
02
Handing over the screenshot you just took
Grab the most recent upload without looking up an id — the capture you made seconds ago becomes the thing being discussed, and its URL is there if you want to refer back to it.
03
Filing a generated image where the team already looks
Upload it with a title, a description and the page it came from, so it lands in the same library everyone already searches instead of an attachment nobody can find again.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
gyazo_latest_image
Fetch latest uploaded image content and metadata from Gyazo
gyazo_search
Full-text search for captures uploaded by users on Gyazo
gyazo_upload
Upload an image to Gyazo
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
- npx on PATH
- GYAZO_ACCESS_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @notainc/gyazo-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"gyazo-mcp-server": {
"command": "npx",
"args": [
"@notainc/gyazo-mcp-server"
],
"env": {
"GYAZO_ACCESS_TOKEN": "<YOUR_GYAZO_ACCESS_TOKEN>"
}
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · TERMINAL
git clone https://github.com/nota/gyazo-mcp-server
cd gyazo-mcp-server
npm run image:buildCLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"gyazo-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GYAZO_ACCESS_TOKEN",
"gyazo-mcp-server"
],
"env": {
"GYAZO_ACCESS_TOKEN": "<YOUR_GYAZO_ACCESS_TOKEN>"
}
}
}
}The gyazo-mcp-server image is not pulled from a registry: it is the one npm run image:build builds from your clone, so run that first. <YOUR_GYAZO_ACCESS_TOKEN> is the access token from https://gyazo.com/api.
