Skip to main content
Glama

Related Servers

Alternatives to shaarli-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with Shiori, a self-hosted bookmark and read-it-later manager, for managing bookmarks and tags.
      13
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Enables AI assistants to interact with a Shlink URL shortening instance, allowing creation, listing, retrieval, and deletion of short URLs, as well as tag management.
      5
      4
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables searching and managing Raindrop.io bookmarks via the official REST API, including listing collections, retrieving bookmarks, and creating or updating bookmarks.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to a self-hosted Linkding bookmark manager through its REST API, enabling bookmark, tag, bundle, asset, and profile operations with confirm-gated writes and dry-run previews.
      26
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables managing bookmarks via the Linkwarden API with token-frugal tools for listing collections and links, adding/moving/deleting links, and creating collections.
      7
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables to manage and analyze a Shlink URL-shortener instance with tools for short URLs, visits, tags, domains, redirect rules, QR codes, and Mercure integration.
      23
      18 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools are cleanly separated by resource: instance info/history, links, and tags. Each tool's description enumerates its actions, so an agent can easily pick the right tool and action without overlap.

    Naming Consistency5/5

    All tools follow a consistent shaarli_<resource> pattern in snake_case, with plural resource nouns where appropriate. The convention is predictable and easy to remember.

    Tool Count5/5

    Three tools is well-scoped for a Shaarli API wrapper, grouping operations by resource rather than exposing dozens of tiny endpoints. Each tool earns its place and covers a distinct domain area.

    Completeness4/5

    The surface covers the main lifecycle: info/history, full link CRUD plus search, and tag list/get/rename/delete. Minor gaps like explicit tag creation or additional link metadata operations are small and can be worked around.