Corent vs Glif MCP Server
A side-by-side look at the Corent and Glif MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Corent for multimedia process work as a local process; choose Glif MCP Server for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Corent when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CORENT_API_KEY. - You want tools like
plan, create, generate_image.
Choose Glif MCP Server when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 51/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | CORENT_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 215 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Corent | View Glif MCP Server |
Tools & capabilities
Corent tools 7
planDescribe a request in plain language; Corent returns the plan (image vs video, tier, settings) + cost estimate, without generatingcreateDescribe what you want + a spend ceiling; Corent decides everything and generates it (the "zero decisions" path)generate_imageText → image, synchronous, returns a permanent URLgenerate_videoText (or image) → video, async jobget_jobPoll a job until completedget_balanceRemaining account balanceget_statusLive tier health
Glif MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Corent
{
"mcpServers": {
"corent-2": {
"command": "npx",
"args": [
"-y",
"corent-mcp"
],
"env": {
"CORENT_API_KEY": "YOUR_CORENT_API_KEY_HERE"
}
}
}
}
Glif MCP Server
{
"mcpServers": {
"glifxyz-glif-mcp-server": {
"url": "https://glif.app/api/mcp"
}
}
}
Frequently asked questions
Corent is categorized under Multimedia Process and uses a local stdio subprocess. Glif MCP Server belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick Corent for multimedia process work and Glif MCP Server for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Corent has no declared pricing — check the project's own site. Glif MCP Server is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add corent-2 and glifxyz-glif-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Corent has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Glif MCP Server has 57/100 (Good) with 5 views, 0 installs and 215 GitHub stars.