Leonardo.Ai MCP integration for AI agents.
Connect AI agents to Leonardo.Ai through 3 structured actions, including get generation, create generation, and list models. Review authentication, inputs, w…
- ACTION CONTRACTS
- 3
- 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 Leonardo.Ai integration exposes
The Leonardo.Ai Agent App exposes 3 provider-backed actions for ai and design & media work. Its current contract lets an authorized agent retrieve a leonardo.ai generation job status and normalized generated image urls, create a leonardo.ai image, video, audio, or 3d generation job using json model parameters, and list leonardo.ai production api models and their model-specific parameter schemas. 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 Leonardo.Ai account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Leonardo.Ai capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_generationREADRetrieve a Leonardo.Ai generation job status and normalized generated image URLs.
INPUTS: generationId
create_generationWRITECreate a Leonardo.Ai image, video, audio, or 3D generation job using JSON model parameters.
INPUTS: model / parameters / public
list_modelsREADList Leonardo.Ai production API models and their model-specific parameter schemas.
INPUT CONTRACTS
Know what the action needs before it runs.
get_generation
generationIdREQUIRED- The Leonardo.Ai generation job identifier.
create_generation
modelREQUIRED- The Leonardo.Ai production model identifier, such as phoenix-v1.0.
parametersREQUIRED- The model-specific generation parameters accepted by Leonardo.Ai.
publicOPTIONAL- Whether generated assets should appear in the Leonardo.Ai community feed.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Generation
Retrieve a Leonardo.Ai generation job status and normalized generated image URLs. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_generationControl Create Generation
Create a Leonardo.Ai image, video, audio, or 3D generation job using JSON model parameters. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_generationVerify with List Models
List Leonardo.Ai production API models and their model-specific parameter schemas. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_modelsSAFETY BOUNDARY
Operate Leonardo.Ai with explicit limits
- Authorize Leonardo.Ai with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 Leonardo.Ai rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Leonardo.Ai task completed successfully.
CONNECTION MODEL
API key
Leonardo.Ai production API key used with the Authorization Bearer header. Create or copy it from the official API Access page: https://app.leonardo.ai/api-access.
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
- 2
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Leonardo.Ai.