MCP tool reference
This page describes the 15 tools in the 1.6.1 OAuth remote MCP release. The connected server’stools/list is authoritative. Local stdio does not expose prepare_upload or get_upload; its upload_file also accepts paths within explicitly allowed directories.
The name and arguments examples describe MCP tool calls, not REST request bodies. An example does not authorize a paid generation.
search_models
recommend_models
search_docs
get_model
Requiredmodel: a string of 1–128 characters, using a returned canonical ID or supported alias.
estimate_cost
max_cost_usd argument and does not produce the CLI’s local quote_id. MCP budget checks belong to generation tools. media_seconds does not set output duration or fill unknown reference-video multipliers.
generate_image, generate_video, generate_audio
Choose the tool matching the output type. They share these top-level arguments:
Inspect the model and inputs, estimate the complete request, disclose limitations, and obtain explicit cost approval before calling. This is an illustrative call shape:
get_task
list_tasks
get_task_usage
check_balance
No arguments:upload_file
prepare_upload
Requiredfile_name: string with an extension used to determine media type. Optional upload_path: relative directory.
get_upload
Requiredupload_id, from the original prepare result:
Results and errors
Tools return readable text and structuredContent; failures can include isError/error/next_step. Completed media can include resource_link and an optional image thumbnail. Hosts differ in content-block support. The original URL remains the delivery reference; previews are not guaranteed in every host. Check tool errors and business fields such as input_valid, estimate status, and task.status. HTTP 200 alone does not establish generation success. Submission timeout may follow task creation and is not proof of no charge. A failed query is not proof that the original task failed.Task progress and results
Use balance and model queries for free connection verification. Use get_task/list_tasks for existing tasks, then deliver original URLs and reported actual costs. The workflow guide covers references, recovery, saving, and gray previews. A display problem must not trigger another paid generation.MCP protocol and backend APIs
The remote endpoint is
https://mcp.evolink.ai/mcp. Passport provides OAuth; the server requests https://api.evolink.ai and the file service. MCP URLs, platform /v1 routes, documentation, and llms.txt are separate entry points.
Initialize and call tools
Let the host or MCP SDK handle initialize, protocol versions, Accept, authentication, sessions, and content blocks. Read tools/list after initialization, then call tools/call:Tools and backend operations
Model parameters belong in arguments.input and are converted to REST requests by the server. media_seconds is a billing hint; max_cost_usd only checks estimates before submission. Published 1.6.1 has no final settlement cap and does not automatically consume complete account quotes merely because new pricing APIs exist.