Model Context Protocol (MCP) server for Gyazo API integration - Upload images, list, retrieve, and manage your Gyazo screenshots
Most developer tooling work still happens through a UI a human drives. Gyazo MCP server moves it into the conversation instead. Model Context Protocol (MCP) server for Gyazo API integration - Upload images, list, retrieve, and manage your Gyazo screenshots.
The server publishes 9 tools. What each one is for:
upload_image — Upload images to Gyazolist_images — List your uploaded imagesget_image — Get detailed information about a specific imagedelete_image — Delete an image from Gyazoget_oembed — Get oEmbed information for a Gyazo image URLTools — The Tools tool exposed by this serverResources — The Resources tool exposed by this serverStandalone — The Standalone tool exposed by this serverBuild — The Build tool exposed by this serverConfiguration is passed through the environment: GYAZO_ACCESS_TOKEN, YOUR_PROJECT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@mercy34mercy/gyazo-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Gyazo's toolset — upload_image, list_images, get_image and 6 more — is a fair guide to whether it matches your workflow. It is maintained by mercy34mercy; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| upload_image | Upload images to Gyazo |
| list_images | List your uploaded images |
| get_image | Get detailed information about a specific image |
| delete_image | Delete an image from Gyazo |
| get_oembed | Get oEmbed information for a Gyazo image URL |
| Tools | The Tools tool exposed by this server. |
| Resources | The Resources tool exposed by this server. |
| Standalone | The Standalone tool exposed by this server. |
| Build | The Build tool exposed by this server. |
{
"mcpServers": {
"gyazo": {
"command": "npx",
"args": ["-y", "@mercy34mercy/gyazo-mcp"],
"env": {
"GYAZO_ACCESS_TOKEN": "your_token_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GYAZO_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_PROJECT_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.