The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Corent listing page.
Give any AI agent the ability to generate images and videos through the Corent API — one key, automatic model routing, provider fallback built in.
| Tool | What it does |
|---|---|
plan | Describe a request in plain language; Corent returns the plan (image vs video, tier, settings) + cost estimate, without generating |
create | Describe what you want + a spend ceiling; Corent decides everything and generates it (the "zero decisions" path) |
generate_image | Text → image, synchronous, returns a permanent URL |
generate_video | Text (or image) → video, async job |
get_job | Poll a job until completed |
get_balance | Remaining account balance |
get_status | Live tier health |
The plan and create tools are the agent-native path: an agent says
what it wants ("a 10s vertical clip of a sunrise for TikTok") and Corent picks
image-vs-video, the tier, aspect ratio, and duration — the agent never manages
models. create enforces a per-call spend ceiling so an autonomous agent can't
overspend.
Get an API key at corent.tech, then add to your MCP client config:
For Claude Code: claude mcp add corent -e CORENT_API_KEY=co_live_... -- npx -y corent-mcp
The hosted server at https://mcp.corent.tech/mcp uses the Streamable HTTP
transport. Pass your API key in the Authorization header — this is the way
to authenticate:
X-Corent-Api-Key: co_live_... is accepted as an equivalent header.
Smithery note: for compatibility with Smithery, the hosted server also accepts the key via query parameters (
?corent_api_key=...or Smithery's base64?config=). Avoid this form anywhere else — URLs can be logged by proxies, gateways, and access logs, which would expose your key. Prefer the Authorization header.