npm corent-mcpstdioMITupdated 1mo ago
Give any AI agent the ability to generate images and videos through the Corent API — one key, automatic model routing, provider fallback built in.
What can you do with Corent?
Corent MCP Server
Give any AI agent the ability to generate images and videos through the Corent API — one key, automatic model routing, provider fallback built in.
Tools
| 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.
Setup
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
Hosted server (no install)
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.
Development
npm install
npm run build
CORENT_API_KEY=... node dist/index.js
Install
Add Corent to your client. Pick the one you use.
claude mcp add corent-mcp -- npx -y corent-mcpcodex mcp add corent-mcp -- npx -y corent-mcpamp mcp add corent-mcp -- npx -y corent-mcp{
"mcpServers": {
"corent-mcp": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"corent-mcp": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"corent-mcp","command":"npx","args":["-y","corent-mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"corent-mcp": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"corent-mcp": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"corent-mcp": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"corent-mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"corent-mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"corent-mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"corent-mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y corent-mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
5 tools
Corent exposes 5 tools to a connected agent.
- 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
Score
75 / 100
Good
- Documentation22/25
- Maintenance22/25
- Trust13/20
- Capability6/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 48 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 5 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.4.2Latest | Jul 18, 2026 |
| 0.3.1 | Jul 14, 2026 |
| 0.2.2 | Jul 6, 2026 |
| 0.2.1 | Jul 6, 2026 |