Corent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CORENT_API_KEY | Yes | Your Corent API key (obtained from corent.tech) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate an image from a text prompt. Returns a permanent public URL. Synchronous: typically completes in 2-20 seconds. Costs a few cents, billed to the Corent account. Failed generations are never billed. |
| generate_videoA | Start generating a video from a text prompt (optionally animating a source image). Asynchronous: returns a job id immediately; poll get_job until status is 'completed'. Video costs more than images (tens of cents to a few dollars depending on tier). Failed generations are never billed. |
| get_jobA | Check the status of a generation job (mainly videos). When completed, the response includes the permanent media URL and the cost. Read-only and free. |
| get_balanceA | Get the Corent account's remaining balance in cents. Useful before starting expensive video generations. Read-only and free. |
| get_statusA | Get live operational status of Corent's generation tiers (operational/degraded). Read-only and free; useful to pick a healthy tier. |
| planA | Preview how Corent would handle a plain-language request WITHOUT generating anything (costs a fraction of a cent). Corent decides whether it's an image or video, which tier, aspect ratio, and duration, and returns the plan plus an estimated cost. Use this to decide or confirm cost before spending. If the request is something Corent can't generate (audio, text, 3D, editing, real-world actions), can_fulfill is false with a reason. |
| createA | Describe what you want in plain language and Corent plans AND generates it — choosing image vs video, tier, aspect ratio, and duration for you (the 'zero decisions' path). You MUST pass max_cost_cents as a spend ceiling; if the estimated cost exceeds it, nothing is generated and you're told the estimate so you can raise the ceiling. Image results come back with a URL; video results come back as a job id to poll with get_job. Failed generations are never billed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct purpose: 'create' handles combined planning and generation, 'generate_image' and 'generate_video' are direct generation for specific media, 'plan' provides cost estimation without execution, and the 'get_*' tools retrieve account and status info. There is no overlap.
Tool names follow a verb_noun pattern (e.g., generate_image, get_balance), with the exception of 'create' and 'plan' which are single verbs. Despite this minor deviation, the naming is mostly consistent and intuitive.
Seven tools cover core functionality—generation, planning, balance, job tracking, and status—without unnecessary duplication or bloat. The count is well-scoped for the domain.
Essential workflows are covered: plan, generate (image/video), monitor jobs, check balance, and system status. Missing features like job cancellation or history are minor gaps; the surface supports the primary use cases.