Skip to main content
Glama
fbwndrud

vibelore

by fbwndrud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to vibelore

No user-submitted related servers found.

    Related Servers

    • novel-mcp

      YinFY90
      A
      license
      A
      quality
      B
      maintenance
      Enables AI tools to collaboratively write novels by managing chapters, characters, and story state through commands like validate, context, draft, review, and approve.
      8
      MIT

    • Novel Workspace MCP

      LiZh132707
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI-driven long-form novel creation and management, including chapter generation, character and timeline tracking, semantic memory retrieval, version savepoints, and deep consistency checking across multiple projects through MCP tools, with support for local LM Studio or any OpenAI-compatible API.
      14
      MIT

    • canonkeeper-mcp

      zhangzhend0ng
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables long-form web novel writing workflows by ingesting chapters into a state database, running deterministic consistency checks, querying entity histories, replaying extraction results, and retrieving conflict reports via MCP tools.
      MIT

    • storyai

      jedikim
      A
      license
      B
      quality
      B
      maintenance
      Enables writers and AI agents to preserve continuity in long-form fiction by maintaining a narrative knowledge graph and exposing MCP tools for querying outlines, entities, references, and consistency diagnostics.
      14
      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 27 tools

    Disambiguation4/5

    Descriptions are unusually thorough and explicitly cross-reference sibling tools (e.g. lore_profile_status points to lore_status and lore_configure; lore_workflow_status points to lore_workflow_history), which strongly aids selection. However, the large cluster of status/getter tools (lore_status, lore_story_status, lore_profile_status, lore_writer_status, lore_arc_status, lore_snapshot_status, lore_workflow_status) and the five *_decide tools create real overlap risk, and the generic lore_decide (for lore_write approvals) sits confusingly alongside the entity-scoped deciders.

    Naming Consistency4/5

    Nearly all 27 tools use a consistent lore_<noun> / lore_<noun>_<verb> snake_case convention (lore_story_plan, lore_arc_decide, lore_writer_status). Minor deviations exist: bare-verb names like lore_write, lore_sync, lore_init, and the generic lore_decide breaks the otherwise predictable <entity>_decide pattern.

    Tool Count3/5

    At 27 tools this is heavy and pushes past the comfortable 3-15 range, so the surface is broad and requires the agent to hold a lot of context. A novel-orchestration domain with distinct lifecycle stages can plausibly justify it, but several status/decide variants inflate the count beyond the strict minimum.

    Completeness4/5

    The lifecycle is well covered: profile, init/create, story spine, writer skill, arc planning, writing, approval, sync of manual edits, rollback, snapshots, configuration, style anchoring, and a webtoon branch, with status tools for each artifact. Minor gaps remain (e.g. no restore tool from rollback archives, webtoon only exposes a single scene tool), but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources