Skip to main content
Use EvoLink from your agent to generate images, video, music, and speech, discover models and costs, upload references, track tasks, and save originals. Choose a connection method, then follow its installation and free verification guide.

​
Choose a connection method

Codex CLI is your agent client; EvoLink CLI is the media tool it calls. They are different products. Each card recommends one route; CLI client guides also link to the native MCP alternative.

​
Choose your client

Claude

Remote MCP · browser sign-in

Codex

CLI · install where Codex runs

Claude Code

CLI · install the command and companion skill

ChatGPT

Remote MCP · add and authorize a connection

Cursor

CLI · use the terminal available to your agent

OpenClaw

CLI · install in the Gateway execution environment

Hermes

CLI · install where Hermes executes commands

EvoLink CLI

Detailed installation for terminals, SSH, and scripts

Other MCP clients

Generic Streamable HTTP and OAuth

Local MCP

stdio · run MCP tools locally

​
Verify before generating

1

Install and authenticate your chosen route

Follow the five-step CLI installation or your MCP client guide. Complete browser sign-in yourself. Keep Keys and tokens out of chat.
2

Query balance and models, and verify skills or tools

CLI users query balance, run doctor, and ask the agent to confirm skill discovery. MCP users actually call check_balance and search_models. Installed files or a tool list do not establish successful execution. These checks do not submit paid media tasks.
3

Review the plan and estimated cost before approving generation

Check the exact model and inputs, prepare references, and review the plan and estimate. After explicit approval, submit once, retain the task ID, and save originals. See CLI workflows or MCP workflows.

​
How the routes relate

CLI media requests follow Agent / terminal → CLI → platform API. Native MCP follows Agent → remote or local MCP → platform API. CLI media execution does not depend on remote MCP. Sign-in uses Passport; uploads and original downloads have separate file endpoints. Installation, sessions, and connection checks are separate. Same-account OAuth can currently share internal Key permissions and quotas. Use one route for the task. Recover unknown submissions through the original route rather than generating again through the other. These guides describe released CLI 0.8.1 and MCP 1.6.1. Development candidates are documented after release acceptance. Query the connected service for current tools and account-available models.