wallabag
Related Servers
Alternatives to wallabag
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP clients to search, organize, and read preserved article text from a Linkwarden bookmark manager, supporting both read and write operations with safety confirmations.2889 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP 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.89 npm34 PyPI1MIT
- AlicenseNot gradedqualityAmaintenanceEnables searching, reading, annotating, and managing a Zotero library from any MCP client.AGPL 3.0

Locket MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables interaction with a read-later and link sharing social feed app, allowing users to manage links, bookmarks, and share through web, API, and MCP.86-- AlicenseAqualityAmaintenanceEnables MCP clients to read a Forgejo, Codeberg, or Gitea instance—including users, repositories, issues, pull requests, search, notifications, comments, reviews, and Actions runs—with opt-in, time-boxed guarded writes for repository, branch, issue, pull request, comment, migration, push-mirror, and workflow operations.591MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to securely interact with the BlogWarp REST API via Streamable HTTP, providing read-only access to posts, notifications, timeline, conversations, and following, plus mutating operations such as drafting, publishing, replying, following, and marking notifications read with explicit confirmation.MIT
TDQS
Scored across 6 tools
Most tools map to distinct Wallabag resources, but wallabag_entries duplicates tag operations (get_tags, post_tags, delete_tags) that also belong under wallabag_tags. wallabag_search also overlaps with filtered entry listing via wallabag_entries.get, leaving real ambiguity about which tool to choose.
All tool names follow a predictable wallabag_<resource> lowercase snake_case pattern with a uniform prefix. The only minor inconsistency is mixing plural resource nouns (entries, tags, annotations) with singular ones (config, info, search).
Six top-level tools bundle many API operations into coherent resource groups, which is well-scoped for a Wallabag server. This avoids both an overly thin surface and an unwieldy one-tool-per-endpoint explosion.
The core lifecycle is covered: entries CRUD/list/search, annotations CRUD, tags, config, and info. However tag operations are split across entry and tag tools, and account/user or export-style operations are absent or unclear, leaving minor gaps.