Skip to main content
Glama
Sign In
emaki

emaki

by hanshs474
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to emaki

No user-submitted related servers found.

    Related Servers

    • MiniMax MCP JS

      leonie306
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients such as Claude Desktop and Cursor to generate images and videos, synthesize speech, clone voices, and design custom voices from descriptive prompts. It supports stdio, REST, and SSE transport modes with configurable API hosts, keys, and local or URL-based resource output.
      549 npm
      MIT

    • Axcel MCP

      aredamz
      A
      license
      B
      quality
      C
      maintenance
      Enables any MCP-compatible AI agent to generate videos and images from text or reference frames, chain scenes into seamless multi-scene films with sound and speech, and download finished media with manifests and previews. It also exposes account status, plan limits, history and library management through confirm-gated, safe-by-default operations.
      24
      34
      MIT

    • Imaginode

      Frankhoubre
      A
      license
      Not graded
      quality
      D
      maintenance
      Generate AI images and videos from Claude, Cursor or any MCP client: 48+ models on one account (Flux 2, Nano Banana 2, Seedream 5, Kling V3, Seedance 2.5, Veo 3.1), with the exact cost in credits returned on every call.
      1
      MIT

    • google-flow-mcp

      RohaanA
      A
      license
      C
      quality
      C
      maintenance
      Enables Claude, Cursor, or any MCP client to create consistent AI characters, generate Veo 3.1 and Omni videos, edit clips, build scenes, export MP4s, and chat with Google Flow's creative agent. Automates AI video production workflows such as reels, storyboards, and multi-shot stories through natural language, with credit guardrails and dry-run pricing.
      23
      10
      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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: credits reads balance, generate_video/generate_image produce different media types, and check_status polls async runs. No two tools can be reasonably confused for one another.

    Naming Consistency4/5

    Three of four tools follow a clean verb_noun pattern (generate_video, generate_image, check_status). The outlier is 'credits', a bare noun that breaks the pattern but remains unambiguous.

    Tool Count5/5

    Four tools is a tight, well-scoped surface for a generation service. Each earns its place: two generators, one async poller required by the async design, and one account query.

    Completeness4/5

    The generate-then-poll lifecycle is covered end to end, plus credit awareness. Minor gaps exist (no list/history of past runs, no cancel or delete for an in-flight run), but the core workflow has no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources