Yorai MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | The host the HTTP server binds to (HTTP mode only). | 127.0.0.1 |
| PORT | No | The port the HTTP server listens on (HTTP mode only). | 3333 |
| MCP_SECRET | No | Secret used in HTTP (remote) mode, appended to the MCP URL path (e.g. https://host/mcp/<MCP_SECRET>). Required when running the HTTP server (dist/http.js); minimum 24 characters. Generate with `openssl rand -hex 24`. | |
| PUBLIC_URL | No | Public HTTPS URL of the server (HTTP mode only). When set, enables yorai_upload_link so files can be uploaded from a phone/browser. | |
| YORAI_API_KEY | Yes | Your Yorai API key, which can be created at https://yorai.id/app/api. | |
| YORAI_BASE_URL | No | The base URL of the Yorai API. | https://yorai.id/api/v1 |
| YORAI_DOWNLOAD_DIR | No | The directory where generated outputs are saved by yorai_download_file. | ~/Downloads/yorai |
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 |
|---|---|
| yorai_balanceA | Check available and held Yorai credits (1 credit = IDR 1,000). |
| yorai_list_modelsA | List models in the Yorai catalog with their starting price. Filter by category (chat, image, video, audio), type or provider slug. |
| yorai_get_modelA | Get one model's generation types, exact input names/options/limits, linkage rules and prices. Call before quoting or creating a job. |
| yorai_quoteA | Price a request without starting a job or holding credits. Returns credits, upTo and line items. Free. |
| yorai_create_jobA | Start an image/video/audio generation. SPENDS CREDITS. The server quotes first and refuses if the hold exceeds max_credits. Returns the job; then poll yorai_get_job. Pass the same idempotency_key when retrying an ambiguous failure so you are not charged twice. |
| yorai_get_jobA | Get a job's status and outputs. Set wait_seconds (max 55) to poll until it finishes or the wait ends. Status: queued, running, succeeded, failed. |
| yorai_list_jobsB | List recent jobs, newest first. Use next_cursor for more. |
| yorai_cancel_jobA | Cancel a queued job and release its credit hold. Running jobs cannot be cancelled (409). |
| yorai_upload_fileA | Upload an image (PNG/JPEG/WebP ≤30 MB), video (MP4/MOV/WebM ≤95 MB, 2–60 s) or audio (MP3/WAV/M4A/AAC/OGG ≤95 MB) and get a file ID for job inputs. Give either a public https URL (the server downloads it) or a local path on the machine running this MCP server. |
| yorai_download_fileC | Save a Yorai file (e.g. a job output id) to disk on the machine running this MCP server. Yorai purges results after 14 days. Default folder: YORAI_DOWNLOAD_DIR or ~/Downloads/yorai. |
| yorai_chatB | Run a text chat model from the Yorai catalog (OpenAI chat.completion format, no streaming, text only). Spends a small amount of credits. |
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 11 tools
Each tool targets a clearly distinct action/resource: catalog lookup, quoting, job lifecycle, file transfer, balance, and chat. The only potential overlap between quote and create_job is explicitly resolved by the descriptions.
All tools use snake_case with a consistent yorai_ prefix and mostly follow verb_noun form. A few names like yorai_balance, yorai_quote, and yorai_chat are bare actions/nouns, but they remain predictable and readable.
The 11 tools form a well-scoped surface covering the necessary operations without obvious redundancy. Each tool earns its place across catalog, billing, jobs, files, and chat.
The surface covers model discovery, pricing, job creation/polling/listing/cancellation, file upload/download, balance checking, and text chat. Core workflows have no obvious dead ends; minor extras like file listing or deletion are not essential for the stated purpose.