Skip to main content
Glama
Fisher521

bookmarks-lifecycle

by Fisher521
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to bookmarks-lifecycle

No user-submitted related servers found.

    Related Servers

    • bookmarks-mcp

      Fisher521
      A
      license
      A
      quality
      A
      maintenance
      A local, read-only MCP server that makes bookmarks from browsers, read-later apps, and export files accessible to AI assistants, enabling search, triage, and summarization without sending data anywhere.
      8
      49 npm
      MIT

    • 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.
      71 npm
      MIT

    • chrome-bookmarks-mcp

      caelum29
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives Claude read/write access to Chrome bookmarks for agentic reorganization, including tree analysis, folder proposals, batch operations with snapshots, deduplication, and dead-link detection.
      1
      MIT

    • taste-mcp

      JVPVO
      F
      license
      Not graded
      quality
      B
      maintenance
      A stateless MCP server that lets AI coding agents consult a curated library of development bookmarks when making decisions. It provides read-only tools to search, inspect, and list curated items, plus a reusable decision prompt.
      1
      -

    • FeedRecall MCP Server

      Paoladev45
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns likes, bookmarks, and saved links into persistent project-aware memory, enabling AI agents to search, import, and process personal content through a local SQLite-backed MCP server.
      Apache 2.0
    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.3/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: intake scans, decide mutates, stats aggregates, undo/restore handle reversal. However, list_layer and today overlap somewhat in that today is essentially a specialized view of the pending layer with extra metadata, which could cause an agent to pick either when trying to see pending items.

    Naming Consistency2/5

    Tool names are a mix of single verbs (intake, decide, restore, undo), single nouns (stats, today), and one snake_case verb_noun (list_layer). There is no consistent verb_noun or action-oriented pattern, making the set feel stylistically inconsistent.

    Tool Count5/5

    Seven tools is well-scoped for a bookmark lifecycle server. Each tool addresses a distinct stage or operation (ingestion, viewing, deciding, stats, reversal), with no trivial or redundant tools.

    Completeness4/5

    The lifecycle is well covered: intake brings items in, today/list_layer expose them, decide moves them, restore/undo handle reversals, and stats provides feedback. Minor gaps include no direct way to edit item metadata outside of rescanning, but this does not block core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources