Skip to main content
Glama

SeeVido Prompt MCP

A deterministic, read-only MCP server for English or Chinese video prompts, reference-aware sequences, diagnosis, and canonical SeeVido resources. It does not generate media, call model providers, access accounts, compare live prices, or spend credits.

Tools

  • build_video_prompt

  • plan_reference_sequence

  • diagnose_video_prompt

  • get_seevido_resources

All tools declare read-only MCP annotations and require no API key.

Related MCP server: opensora2-prompt-mcp

Install

{
  "mcpServers": {
    "seevido": {
      "command": "npx",
      "args": ["-y", "github:gpt-img-2/seevido-prompt-mcp"]
    }
  }
}

Or run locally with pnpm install, pnpm build, and node dist/index.js. Set SEEVIDO_APP_BASE_URL only when canonical resource links should use another origin.

The companion OpenClaw Skill is at openclaw/seevido-video-prompt-architect. This is an independent prompt-design utility, not official documentation for any model provider.

Development

pnpm validate

License

MIT

Available Tools

4 tools
build_video_promptBuild a SeeVido video promptB
Read-onlyIdempotent

Turn a rough idea into a deterministic English or Chinese prompt pack with motion, camera, lighting, reference roles, and continuity controls.

Inputs: idea (required), style, camera, motion, +7 more.

diagnose_video_promptDiagnose a video promptA
Read-onlyIdempotent

Check English or Chinese prompts for scene, motion, camera, lighting, continuity, and preserved reference tokens.

Inputs: prompt (required).

get_seevido_resourcesGet SeeVido resourcesA
Read-onlyIdempotent

Return canonical SeeVido prompting, workflow, model-orientation, or safety resources without fetching external content.

Inputs: topic.

plan_reference_sequencePlan a reference-aware video sequenceB
Read-onlyIdempotent

Create a deterministic 1–6 shot sequence with reference roles, timing, continuity anchors, and intended end frames.

Inputs: idea (required), shotCount, cameraStyle, referenceRoles, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: building prompts, planning sequences, diagnosing prompts, and retrieving resources. There is no overlap in functionality, so an agent can clearly identify which tool to use for a given task.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern in snake_case (build_video_prompt, plan_reference_sequence, diagnose_video_prompt, get_seevido_resources). The verbs clearly describe the action and the nouns the target, making the naming predictable and uniform.

    Tool Count5/5

    With exactly 4 tools, the server is well-scoped and each tool earns its place for the domain of video prompt engineering. This is within the ideal 3-15 range and not excessive for the functionality offered.

    Completeness4/5

    The tools cover the core lifecycle of video prompt creation: building, planning sequences, diagnosing, and obtaining resources. Minor gaps exist, such as no tool for editing or deleting existing prompts, but these are not essential for the server's apparent purpose and agents can work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers