Skip to main content
Glama
yomi

yomi

Official
by RikaiDev

Related Servers

Alternatives to yomi

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, search, and reply to personal LINE messages, including end-to-end-encrypted chats and media, all decrypted locally.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to work LINE Official Account Manager chats like a customer-support person, including listing, reading, searching, viewing profiles and attachments, and optionally sending replies with human approval while remaining read-only by default.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools to read and send messages through LINE Desktop via MCP, supporting manual or automatic sending without official LINE API tokens.
      118 npm
      127
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools to read and send LINE messages by automating the LINE Desktop application, with macOS OCR-based reading and idle-aware scheduling.
      118 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run LINE Official Accounts through natural language — sending broadcasts, Flex and tappable Rich Messages, building rich menus, managing coupons, audiences, insights, LIFF apps, and LINE Shopping storefronts. Includes zero-hosting image handling with pre-delivery verification, quota and quiet-hour guardrails, Thai localization, and multi-account support across stdio or HTTP transports.
      339 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and descriptions actively disambiguate the tricky clusters (get_unread_digest vs list_conversations vs get_insight; find_contact vs list_contacts; search_stickers vs list_stickers). The only real overlaps are the explicitly-flagged legacy alias get_message_image vs get_message_media and collect_messages vs search_messages' auto-collect, both of which are documented so an agent won't misselect.

    Naming Consistency5/5

    Nearly every tool follows a clean snake_case verb_noun pattern (get_*, list_*, send_*, search_*, create_/rename_/invite_/kick_/leave_group, block_/unblock_contact). The send_* family, group-management family, and privacy family are each internally uniform. Only 'login' / 'login_complete' deviate slightly, which is negligible.

    Tool Count3/5

    41 tools is heavy and sits well above the comfortable 3-15 range, largely because seven distinct send_* variants (message/image/file/audio/video/location/contact/sticker) plus a full login pair inflate the surface. Each tool is genuinely distinct and earns its place in a rich LINE domain, but some consolidation (e.g. a single send_media with a type param) would be reasonable.

    Completeness5/5

    The surface covers the full lifecycle: auth (login/login_complete), conversation listing/search/digest/insight, message fetch and media download, all outbound message types, group CRUD and membership, contact add/block/find, reactions/unsend, stickers, and a complete privacy denylist lifecycle (exclude/include/list/policy). No obvious dead ends for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data