TinyPNG for AI agents
TinyPNG compresses PNG, JPEG, and WebP images to cut file size while keeping quality, used by designers and developers preparing images for the web. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in TinyPNG.
Compress an image
Shrink a PNG, JPEG, or WebP file and get back a smaller version for the web.
Check compression count used
Read how many compressions have been used this billing period, a read-only usage check.
Download a compressed image
Retrieve the compressed result after processing an uploaded image.
5 TinyPNG actions, graded by risk.
Every TinyPNG action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- tinypng.get_compression_countGet TinyPNG Compression Count
write
4Create and change things. Allow, or ask the user first.
- tinypng.tinify_outputDownload Compressed Image
- tinypng.transform_imageTransform Compressed Image
- tinypng.shrink_and_get_image_idShrink and get image ID
- tinypng.tinify_compress_and_store_in_azureCompress and Store Image in Azure
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
TinyPNG in three steps.
- 01Your users connect TinyPNGThey add their TinyPNG api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “download Compressed Image” can wait for the user to approve.
- 03Any agent can actYour agent calls TinyPNG through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('tinypng', { read: 'allow', write: 'ask', // tinify_output destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How TinyPNG connects.
Users add their TinyPNG api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same TinyPNG connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use TinyPNG from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
TinyPNG and Arc0, answered.
Can I use TinyPNG with Claude, ChatGPT or Cursor?
Yes. Connect TinyPNG to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the TinyPNG actions you allow.
How do users connect TinyPNG?
Users add their TinyPNG api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which TinyPNG actions can my agent take?
5 in total: 1 read, 4 write and 0 destructive, such as “download Compressed Image”. Your policies decide which of them each agent may call.
Can I make my agent read-only in TinyPNG?
Yes. Allow read actions and deny writes in the TinyPNG policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call TinyPNG too?
Yes. The same TinyPNG connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug TinyPNG into your agent.
Your users connect TinyPNG once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan