Compresses an image and holds it by ID, resizes or converts it before download, and uploads the result to Azure Blob Storage in one call.
5actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro compresses an image using TinyPNG's optimization and uploads the result directly to Azure Blob Storage in a single operation. Your optimized image is now stored and ready for immediate use on your site or app.
Ayro compresses an image and returns its TinyPNG image ID for tracking or future retrieval. Compressed image IDs let you reference optimized versions across workflows without re-uploading.
Ayro retrieves a previously compressed image by its TinyPNG image ID and makes it available for download. You can pull any past compression without re-running the optimization process.
Each card is one request a support team gets, and the TinyPNG actions Ayro runs to close it.
Ayro shrinks the file and keeps the returned image ID, applies a resize, a format conversion or a metadata rule to that same compressed copy, then downloads the finished version.
Ayro compresses the image and uploads it to the target Azure blob in a single operation, with no intermediate download, and reports how many compressions the account has spent this month.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the TinyPNG actions it has and picks the ones a request needs.
Authorize the TinyPNG account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the TinyPNG actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeTinyPNG · Ayro
What can you do in TinyPNG without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside TinyPNG.
JPEG, PNG and WebP - the formats the Tinify API accepts. Compress and Store Image in Azure names all three explicitly, and Transform Compressed Image can convert between them once a file has been shrunk.
All 5 actions your agent can call on TinyPNG, straight from the live MCP connection.
Retrieve the number of compressions made this month.
Shrink an image and return its TinyPNG image ID.
Compress an image using the Tinify API and upload the optimized result directly to Azure Blob Storage in a single operation.
Retrieve a compressed image by its image ID.
Transform a compressed image by resizing, converting format, preserving metadata, or storing to cloud storage.
Same connection, same setup. Pick the next one your team already uses.
Creates and imports designs, uploads assets to the content library, exports finished work in the right format, and comments on drafts under review.
Turns a written brief into a DreamStudio generation, guides it with a reference image, and checks which engines and credits the key has left.
Lists the design templates available on an Imejis.io account so a team can confirm which layouts exist, and their exact names, before requesting a render.
Searches a workspace for the right board, reads the widgets and tags already on it, and posts sticky notes onto it at set coordinates.
Generates the Plasmic globalContexts snippet so a developer gets working code instead of a documentation link.
Reads project colours, text styles, and components, updates design tokens, uploads new screen versions, and clears annotations left on screens.

Authorize the account and your agent has all 5 actions from the first conversation.
