Skip to main content
Glama
gpt-img-2

see-dance-2-prompt-mcp

by gpt-img-2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to see-dance-2-prompt-mcp

No user-submitted related servers found.

    Related Servers

    • chinavideoai

      gpt-img-2
      A
      license
      A
      quality
      C
      maintenance
      Enables deterministic, read-only creation of bilingual video prompts, timed reference-aware shot plans, and focused prompt diagnostics without API keys or external provider calls.
      4
      MIT

    • seevido

      gpt-img-2
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only tools to build English or Chinese video prompts, plan reference-aware sequences, diagnose prompts, and fetch canonical SeeVido resources without API keys.
      4
      MIT

    • C Dance Prompt MCP

      gpt-img-2
      A
      license
      A
      quality
      C
      maintenance
      Enables searching the public C Dance AI prompt gallery, inspecting complete prompts, comparing production workflows, and turning rough ideas into structured video prompt briefs.
      4
      MIT

    • Seedance 2.0 MCP Server

      rocnubie
      A
      license
      B
      quality
      C
      maintenance
      Provides read-only access to Seedance 2.0 AI video generator information including styles, pricing, documentation, and official links for MCP-compatible AI clients like Claude Desktop, Cursor, Windsurf, and Continue.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: building a prompt, planning a sequence, diagnosing issues, and fetching resources. There is no overlap in purpose, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, with clear action prefixes (build, plan, diagnose, get). The naming is uniform and predictable.

    Tool Count5/5

    Four tools is an appropriate scope for this domain, covering the core workflow without redundancy or excessive granularity. Each tool earns its place.

    Completeness5/5

    The toolset covers the full lifecycle: creating a prompt, planning sequences, diagnosing problems, and accessing resources. There are no obvious missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources