Skip to main content
Glama
kartiksingh02777

creator-ops-mcp

by kartiksingh02777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to creator-ops-mcp

No user-submitted related servers found.

    Related Servers

    • ViralScout MCP

      TYKAIRO-AI
      F
      license
      B
      quality
      B
      maintenance
      Enables creators to analyze supplied short-form video transcripts and metadata into structured hook, retention, remix, script, content-gap, and creator-pack outputs without API keys or paid external services.
      8
      -

    • YouTube Transcript + Search

      tubeagentkit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to pull full transcripts from YouTube videos, search videos and channels, browse a channel's complete upload history, search within a single channel, and extract every video in a playlist through one hosted remote endpoint. It supports API-key or OAuth 2.1 sign-in with no local installation, returning metadata and paginated results with stable error codes.
      23
      MIT

    • youtube-signal-mcp

      alibabagini-cyber
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to retrieve YouTube transcripts, video info, channel video lists, and monitor channels for new uploads, with built-in prompt templates for summaries and industry signals—all without an API key.
      4
      MIT

    • tubescout

      not0lucky
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search YouTube like a database, retrieve transcripts and channel data, and mine videos for claims, numbers, and demand signals — without needing an API key.
      6
      42 npm
      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.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each of the four tools targets a clearly distinct output: ranked shorts candidates, chapter markers, SEO title/thumbnail matrix, and a compliance risk report. There is no plausible scenario where these overlap, and the descriptions reinforce the boundaries.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern (extract_*, generate_*, generate_*, audit_*), with verbs that accurately reflect each action. The naming is predictable and readable.

    Tool Count4/5

    Four tools is well-scoped for a transcript-processing creator-ops pipeline and each earns its place. It sits at the thin end, but nothing feels redundant or missing for the stated purpose.

    Completeness4/5

    The surface covers the core post-transcript workflow: shorts extraction, chapters, SEO metadata (titles, description, tags), and pre-publish compliance. Minor gaps exist, such as no transcript ingestion/preprocessing or analytics/publishing step, but the set is usable end to end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources