codex-meshy-multiview
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MESHY_API_KEY | No | Your Meshy API key. If set, this takes precedence over MESHY_API_KEY_FILE. | |
| MESHY_API_KEY_FILE | No | Path to a private UTF-8 file containing only the Meshy API key. Used when MESHY_API_KEY is not set. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meshy_doctorA | Check whether local Meshy credentials are configured, without exposing them or calling the API. |
| meshy_plan_multiviewA | Validate four image paths/HTTPS URLs and preview redacted requests. No paid task is submitted. |
| meshy_start_multiviewA | Submit one PAID textured Multi-Image to 3D task using four views; return the saved run directory. Local images are sent to Meshy. Continue this run with meshy_advance_workflow. Do not repeat start after an uncertain submission; inspect tasks and recover its ID. |
| meshy_advance_workflowA | Check progress once and submit PAID adaptive low-poly remesh when generation succeeds. Returns promptly without polling. Saved IDs prevent resubmitting completed stages. An uncertain submission requires recovery, never a repeat submission or a new run. |
| meshy_workflow_statusA | Read a saved workflow and its next step. Local only; does not refresh remote task status. |
| meshy_download_workflowA | Download completed model and texture artifacts into the saved run directory; submits no paid tasks. |
| meshy_recover_submissionA | Attach a verified existing task ID after an uncertain submission. Never creates a task. Inspect Meshy task history first and select the task belonging to this exact run and stage. |
| meshy_list_tasksA | List up to 100 existing Meshy tasks for inspection or uncertain-submission recovery; read only. |
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 8 tools
Each tool has a distinct role in the workflow, and the paid-task boundaries are clearly marked. There is mild potential confusion between meshy_advance_workflow and meshy_workflow_status, but the local-vs-remote distinction is clearly described.
All tools share a consistent meshy_ prefix and use snake_case, which is easy to follow. Minor deviations like meshy_doctor (noun) and meshy_workflow_status (noun_noun) break the otherwise verb_object pattern.
Eight tools is well-scoped for a 3D generation workflow: credential check, planning, paid submission, workflow advancement, status, download, recovery, and task listing. No tool feels redundant or unnecessary.
The core lifecycle from planning through submission, remesh, status, and download is covered, including a recovery path for uncertain submissions. Minor gaps exist around cancellation, cleanup, or credential configuration, but agents can complete the main workflow without dead ends.