MCP
Warlok MCP Integration
Warlok MCP server exposes generation tools for agent runtimes over stdio.
The MCP package is published as @warlok-net/mcp-server. Agents can run it over stdio with WARLOK_API_URL and WARLOK_API_KEY, or call the HTTP tool surface at GET /api/v1/mcp/tools + POST /api/v1/mcp/call.
Install + Run
pnpm dlx @warlok-net/mcp-server@latestAgent Config (JSON)
You can also generate this automatically using warlok mcp print-config --format json.
{
"mcpServers": {
"warlok": {
"command": "pnpm",
"args": ["dlx", "@warlok-net/mcp-server@latest"],
"env": {
"WARLOK_API_URL": "https://api.warlok.net",
"WARLOK_API_KEY": "<your_key>"
}
}
}
}Core Tool Names
generate_3d_model
get_model_status
list_models
get_model_download_url
delete_modelCharacter Packs (source preview)
generate_character_pack takes image_url (or a local image_pathover stdio) and derives separate body, head, hair, garment, footwear and held-prop meshes from that one image. get_model_status then carries a pack block with per-part status and URLs, and get_model_download_url lists one download per part. It reserves several credits (unused parts refunded). Parts are unrigged visual candidates; fitting and rigging happen outside Warlok. Use export_character_pack, poll pack.delivery until ready, then get_model_download_url for the original components and reconstruction guide. Built stdio source 0.1.2 is ahead of npm; use the live HTTP tool schema.
{
"name": "ranger-pack",
"image_url": "https://example.com/ranger.png"
}