Kraken.io for AI agents
Kraken.io is an image optimization service that compresses image files to cut page weight while preserving visual quality, used by web and design teams before publishing. 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 Kraken.io.
Compress an image by URL
Optimize a hosted image to shrink its file size before it goes on a web page.
Check usage, read-only
Look up account status to see how much optimization quota remains this cycle, a read-only check with no image changes.
Preserve metadata on export
Optimize an image while keeping its metadata intact, for photos that need attribution kept.
3 Kraken.io actions, graded by risk.
Every Kraken.io 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.
- kraken_io.check_user_statusCheck Kraken.io User Status
write
2Create and change things. Allow, or ask the user first.
- kraken_io.preserve_metadataPreserve Image Metadata
- kraken_io.optimize_image_urlOptimize Image by URL
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Kraken.io in three steps.
- 01Your users connect Kraken.ioThey add their Kraken.io api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “preserve Image Metadata” can wait for the user to approve.
- 03Any agent can actYour agent calls Kraken.io through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('kraken_io', { read: 'allow', write: 'ask', // preserve_metadata destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Kraken.io connects.
Users add their Kraken.io 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 Kraken.io 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 Kraken.io from any agent.
Kraken.io and Arc0, answered.
Can I use Kraken.io with Claude, ChatGPT or Cursor?
Yes. Connect Kraken.io 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 Kraken.io actions you allow.
How do users connect Kraken.io?
Users add their Kraken.io 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 Kraken.io actions can my agent take?
3 in total: 1 read, 2 write and 0 destructive, such as “preserve Image Metadata”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Kraken.io?
Yes. Allow read actions and deny writes in the Kraken.io policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Kraken.io too?
Yes. The same Kraken.io connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Kraken.io into your agent.
Your users connect Kraken.io once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan