Eden AI MCP integration for AI agents.
Connect AI agents to Eden AI through 2 structured actions, including list models and create chat completion. Review authentication, inputs, workflows, and sa…
- 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 Eden AI integration exposes
The Eden AI Agent App exposes 2 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent list the eden ai models available to the current api key and create a non-streaming eden ai openai-compatible chat completion. 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 Eden AI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Eden AI capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_modelsREADList the Eden AI models available to the current API key.
create_chat_completionWRITECreate a non-streaming Eden AI OpenAI-compatible chat completion.
INPUTS: model / messages / fallbacks / router_candidates / frequency_penalty
INPUT CONTRACTS
Know what the action needs before it runs.
create_chat_completion
modelREQUIRED- The Eden AI model identifier, formatted as `<vendor>/<model>`.
messagesREQUIRED- The ordered conversation history sent to the model.
fallbacksOPTIONAL- Fallback model identifiers to try in order if the primary model fails.
router_candidatesOPTIONAL- Candidate model identifiers used when model is `@edenai`.
frequency_penaltyOPTIONAL- The frequency penalty applied to repeated tokens.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Models
List the Eden AI models available to the current API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_modelsControl Create Chat Completion
Create a non-streaming Eden AI OpenAI-compatible chat completion. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_chat_completionVerify with Create Chat Completion
Create a non-streaming Eden AI OpenAI-compatible chat completion. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_chat_completionSAFETY BOUNDARY
Operate Eden AI with explicit limits
- Authorize Eden 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 Eden AI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Eden AI task completed successfully.
CONNECTION MODEL
API key
Eden AI API key used with the Authorization Bearer header. Create or manage keys in your Eden AI account at https://app.edenai.run/settings/api-keys.
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
- 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 Eden AI.