Karakuri MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEEDDANCE2.0_API_KEY | Yes | API key for PiAPI Seedance video generation. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_seedance_taskB | Create a video generation task using PiAPI Seedance 2. |
| get_seedance_taskA | Get the status and result of a PiAPI task. |
| download_fileA | Download a file from a URL to the local downloads directory. |
| get_audit_logsA | Retrieve recent execution audit logs of this MCP server. Shows who called which tool and when. |
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 4 tools
Each tool serves a distinct purpose: creating a video task, checking its status, downloading a file, and viewing audit logs. There is no overlap or ambiguity in their roles.
All tool names follow a consistent verb_noun pattern (create_seedance_task, get_seedance_task, download_file, get_audit_logs). The naming is predictable and clearly conveys each tool's function.
With only 4 tools, the server is lean but well-scoped for its purpose: submitting a generation request, polling for results, downloading output, and auditing usage. Each tool earns its place.
The core video generation workflow is covered: create task, get task status, and download the result. Missing a list/cancel feature is a minor gap, but the primary lifecycle is complete.