Skip to main content
Glama
@ezquill/mcp-server

@ezquill/mcp-server

by EasyModeOnly

Related Servers

Alternatives to @ezquill/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to search canon works, lock timeline-scoped rules and character seals, audit plots for out-of-character or canon-breaking content before writing, and generate divergent worldbuilding hooks.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search lore, resolve entities and aliases, query what characters know or keep secret, retrieve timelines, and propose lore or scenes into a staging area without altering the author's canon.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects compatible AI assistants to Memuaria so they can retrieve account and book information, check memory or story draft status, and prepare changes for user review while personal data remains in the Memuaria cloud service.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI assistants read and search a personal library of documents, inspect review cards and feedback, send notes to the user's phone, and suggest edits as proposals the user accepts or rejects in their apps.
      GPL 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to a creator workspace so users can read their posts, calendar, Link in Bio page, media and analytics through natural language. It can only read data and prepare proposed changes, which a person must review and approve in the app before anything is published.
      MIT

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: project listing/detail/search, outline vs. scene, entity list/detail, timeline, feedback, and auth. There is little risk of an agent selecting the wrong tool for a given intent.

    Naming Consistency5/5

    All tools use a consistent lowercase snake_case verb_noun pattern: list_projects, get_project, search_project, get_outline, read_scene, list_entities, get_entity, get_timeline, list_feedback. authenticate and sign_out are the only exceptions but they are auth actions and still read predictably.

    Tool Count5/5

    Eleven tools is well within the ideal range for this domain. Each tool covers a distinct need without unnecessary duplication, and the auth tools are justified for a service that requires sign-in.

    Completeness4/5

    The read-side surface is thorough: projects, outline, scenes, entities, timeline, and feedback are all covered. The only notable gap is the absence of any create/update/delete operations, but that appears intentional for a read-only writing-project assistant.