Skip to main content
Glama

Related Servers

Alternatives to mcp-ikaos-story

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables agents and scripts to drive a social publishing account through remote or local MCP tools: drafting, scheduling, approving and publishing posts, running durable background jobs with file attachments, and reading or editing Brand Memory, assets, and standing agents. Hosts can connect over OAuth with no API key, or run the stdio variant with a key for local disk tools.
      65
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients to a self-hosted photo library through its REST API, exposing assets, albums, people, search, and optional administrative toolsets with read-only defaults and confirm-gated writes. It supports stdio and localhost Streamable HTTP transports.
      66 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-oriented MCP server for Taranis AI, exposing the list_stories tool over stdio or Streamable HTTP for desktop AI assistants and developer tools.
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to start new Codex conversations and continue existing threads, exposing codex and codex-reply tools over stdio via the Codex app-server protocol.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local management of Pavo website accounts through a stdio MCP service, covering canvases, reference media, generation tasks, result downloads, and website assets. It also supports AI script episode planning plus character, scene, and prop asset management.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Local stdio MCP server for working on Intern-hosted sites through guarded Git checkouts. It enables authentication, site preparation, testing, validation, and publishing via coding harnesses like Codex and Claude Code.
      36 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: listing vs. single-story context, reading rules vs. content, saving vs. validating, and uploading vs. updating images. Even the two image tools are clearly separated by their roles in the upload/replace workflow.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern, such as list_stories, get_story_context, save_story_content, and validate_story. No mixed casings or stylistic deviations appear.

    Tool Count5/5

    Seven tools is a well-scoped set for a story management server. Each tool covers a meaningful part of the workflow without redundancy or excessive granularity.

    Completeness4/5

    The set covers listing, reading, creating/updating content, validating, and managing images, which handles the core story lifecycle. The main gap is the absence of an explicit delete operation for stories or images, though this may be intentional given the immutable/revision-oriented design.

    Maintenance

    ActivityStale
    ResponsivenessNo issues