Kraken.io MCP integration for AI agents.
Connect AI agents to Kraken.io through 2 structured actions, including get user status and optimize image. Review authentication, inputs, workflows, and safe…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Kraken.io integration exposes
The Kraken.io Agent App exposes 2 provider-backed actions for design & media work. Its current contract lets an authorized agent fetch the current kraken.io plan status and monthly optimization quota and optimize one image with kraken.io from either a public url or direct upload, then store the result in local transit storage. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Kraken.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Kraken.io capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_user_statusREADFetch the current Kraken.io plan status and monthly optimization quota.
optimize_imageREVIEWOptimize one image with Kraken.io from either a public URL or direct upload, then store the result in local transit storage.
INPUTS: sourceUrl / contentBase64 / fileName / lossy / quality
INPUT CONTRACTS
Know what the action needs before it runs.
optimize_image
sourceUrlOPTIONAL- The public URL of the source image to optimize.
contentBase64OPTIONAL- The Base64-encoded source image bytes to upload.
fileNameOPTIONAL- The filename used for direct upload requests.
lossyOPTIONAL- Whether Kraken.io should use lossy optimization instead of lossless optimization.
qualityOPTIONAL- The custom image quality level for JPG, PNG, and GIF output.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get User Status
Fetch the current Kraken.io plan status and monthly optimization quota. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_user_statusVerify with Optimize Image
Optimize one image with Kraken.io from either a public URL or direct upload, then store the result in local transit storage. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
optimize_imageSAFETY BOUNDARY
Operate Kraken.io with explicit limits
- Authorize Kraken.io with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Kraken.io data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Kraken.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Kraken.io task completed successfully.
CONNECTION MODEL
API key
Kraken.io API key used inside the auth.api_key request body. Find it in your Kraken.io account API Credentials page: https://kraken.io/account/api-credentials
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Kraken.io.