Skip to main content
Glama
ni-c

linkwarden-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to linkwarden-mcp

No user-submitted related servers found.

    Related Servers

    • linkwarden-mcp

      flumpiey
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Linkwarden bookmarks providing read-first search and preserved content access with opt-in write, delete, and collection-delete tools, plus heuristic triage workflows.
      62 npm
      40 PyPI
      MIT

    • Linkwarden MCP

      crunchypancake1
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server connects to a Linkwarden instance, enabling semantic search, filtering, and management of bookmarks through natural language.
      62 npm
      MIT

    • linkwarden-mcp

      o-gent
      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
      -

    • raindrop-mcp

      aderaaij
      A
      license
      B
      quality
      C
      maintenance
      Enables management of Raindrop.io bookmarks, collections, tags, and highlights via MCP tools, with support for search, bulk editing, and library auditing.
      17
      MIT

    • ChatGPT Bookmark Site MCP

      madebypan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to search, read, and query saved bookmark content via a read-only MCP interface, with full-text and optional semantic search.
      4
      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.2/5.0

    Scored across 28 tools

    Disambiguation5/5

    Every tool targets a distinct resource/action combination: reads are list/get, mutations are create/update/delete, bulk operations carry a bulk_ prefix, and preservation/RSS/pinning have dedicated verbs. Near-neighbor tools like delete_link vs delete_link_preservations are clearly separated by their nouns and descriptions.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, with list/get for reads, create/update/delete for writes, bulk_ for multi-item operations, and set_/represerve_/merge_ for special actions. The singular/plural distinction between single-item and bulk tools reinforces the pattern rather than breaking it.

    Tool Count3/5

    28 tools is on the heavy side and exceeds the typical comfortable range, though the set covers several distinct subdomains: links, preservation, collections, tags, RSS, and account/worker status. No tool is pure filler, but the count feels more like a full API wrapper than a tightly scoped MCP server.

    Completeness5/5

    The tool surface provides full lifecycle coverage for links, collections, and tags, plus bulk operations, preservation controls, RSS subscription management, and background-worker monitoring. There are no obvious dead ends: search_links covers listing, get_link_content reads archived text, and represerve_link/delete_link_preservations handle preservation lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources