Generate images, videos, voice, and text via the Corent API. Auto model routing with fallback.
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:
{
"mcpServers": {
"corent": {
"command": "npx",
"args": ["-y", "corent-mcp"],
"env": { "CORENT_API_KEY": "co_live_..." }
}
}
}
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:
{
"mcpServers": {
"corent": {
"url": "https://mcp.corent.tech/mcp",
"headers": { "Authorization": "Bearer co_live_..." }
}
}
}
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.
npm install
npm run build
CORENT_API_KEY=... node dist/index.js
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y corent-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-gg13121-corent-mcp": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceCorent works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.