Compress, resize and convert images with TinyPNG by URL, and check this month's compression count. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"tinypng": {
"url": "https://tinypng.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"tinypng": {
"type": "http",
"url": "https://tinypng.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your TinyPNG API key.
Get a free key (500 compressions a month) at tinify.com/developers, then copy it from your API dashboard. Every compression, resize and conversion counts against your own Tinify quota. Your key is used only to call the Tinify API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your TinyPNG API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
tinypng_compress_image | write | Compress an image from a URL WRITE (uses quota): ask TinyPNG (Tinify) to fetch a public image by URL and compress it (JPEG, PNG, WebP, AVIF or JPEG XL). Returns the output_url (Tinify's Location address of the compressed image), the compressed size and type, the savings when the input size is known, and the Compression-Count header (compressions used this month). The image is stored by Tinify for about 48 hours; output_url needs your API key, so use tinypng_download_image to get the bytes and tinypng_transform_image to resize, convert or keep metadata. Each compression counts against the monthly quota of your Tinify API key (the free plan includes 500 per month); resizing and converting count one extra compression each. POST /shrink. |
tinypng_transform_image | write | Resize, convert or keep metadata of a compressed image WRITE (uses quota): apply a resize, a format conversion and/or metadata preservation to an image compressed earlier (the output_url from tinypng_compress_image, valid about 48 hours). Returns the resulting type, byte size, width, height and Compression-Count; the image itself is returned too when include_image is true and it is under 1 MB. Resize: method scale (give width OR height), or fit / cover / thumb (give width AND height); images are never scaled up. Convert: one or more of image/webp, image/jpeg, image/png, image/avif, image/jxl (several = the smallest is returned) or */* (the smallest of WebP, JPEG, PNG); converting a transparent image to JPEG needs a background colour. Preserve: copyright, creation, location (location is JPEG only) keeps that metadata, which makes the file slightly larger. Each call is a fresh request: resize and convert each count one extra compression on your monthly Tinify quota, preserve is free. Tinify returns the bytes only (no new URL), so only include_image gives you the transformed file, and only when it is under 1 MB. POST /output/{id}. |
tinypng_download_image | read | Download a compressed image Fetch the compressed image of an earlier tinypng_compress_image (its output_url, valid about 48 hours) and return it as an image with its type, byte size, width and height. Images over 1 MB are described but not returned inline. Downloading does not use extra compression quota. GET /output/{id}. |
tinypng_get_usage | read | Get compression usage this month How many compressions your Tinify API key has used this calendar month (the Compression-Count header), and whether the key is valid. The check sends an empty request that Tinify refuses, so nothing is compressed and no quota is used. Compare with your Tinify plan (the free plan includes 500 per month). POST /shrink with no body. |
tinypng_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
tinypng_request_feature | Request a missing feature Tell usefulapi that the user needs something the TinyPNG tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
tinypng_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED TinyPNG tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
tinypng_cancel_subscription | Cancel the Pro subscription Cancel the caller's TinyPNG Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run tinypng_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper API key | $9/mo · $90/yr | Unlimited |
Pro covers this TinyPNG server only. Subscribe with tinypng_upgrade (it returns a Stripe Checkout link). Cancel any time with tinypng_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running tinypng_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by TinyPNG. The server calls the TinyPNG API with your own TinyPNG access, so it sees only the data that your account can see.
The login page asks for your TinyPNG API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your TinyPNG API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the TinyPNG API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in TinyPNG.
Yes, if you approve it. 2 of the 4 TinyPNG tools can create or change data. The other 2 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this TinyPNG server only. Run tinypng_usage_status to see how many calls you used.
Ask the AI to run tinypng_upgrade: it returns a Stripe Checkout link. To cancel, run tinypng_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with tinypng_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.