corent-mcp

Corent MCP Server

Give any AI agent the ability to generate images, videos, voice, and text 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
generate_speech	Text → spoken audio, synchronous
generate_text	Prompt → text from a frontier language model, synchronous, billed per token
list_models	The direct-access menu: every model that can be pinned by name, with quality and live status
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.

When the user names a specific model

All four generate_* tools also take an optional model: pin an exact model from list_models and Corent runs that one, never a substitute (if it can't deliver, the call fails and nothing is billed). Use it only when the user asked for a particular model by name — otherwise omit it and let Corent route to the best fit for the prompt, which is what the tiers are for.

generate_text is the language-model lane: it puts every frontier lab on the same key and the same bill, so an agent can get a named model's answer or a second opinion from another lab without the user holding that lab's account.

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 and supports OAuth: in claude.ai (Settings → Connectors → Add custom connector) just enter the URL with no key — you'll be sent to a Corent page to approve access. Your API key is verified once, sealed into an encrypted connection token, and never shown to the client. Revoking the key in your dashboard disconnects the client instantly.

Non-OAuth clients can instead pass an API key in the Authorization header:

{
  "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

The hosted entrypoint (dist/http.js) additionally needs MCP_TOKEN_SECRET (random string; encrypts OAuth tokens — rotating it logs every connector out) and optionally MCP_PUBLIC_URL (defaults to https://mcp.corent.tech).