Skip to main content
Glama

Related Servers

Alternatives to ai-bookmark-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Fully local, privacy-first MCP server that turns exported X/Twitter bookmarks into a searchable, enriched knowledge base for Claude Desktop and Claude Code.
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A local MCP server that gives saved bookmarks a lifecycle with time-based layers (pending, watching, kept, lapsed), so they get decided on instead of accumulating. It aggregates bookmarks from your browsers, drips them into a daily queue, and supports keep/watch/drop decisions, restore, and undo.
      7
      34 npm
      MIT
    • 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
    • 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

    TDQS

    C2/5.0

    Scored across 20 tools

    Disambiguation2/5

    Multiple aliases (e.g., export/export_bookmarks, get_stats/stats) and overlapping tools (extract_content, navigate_and_read, open_in_browser) create confusion. Agents may struggle to select the correct tool.

    Naming Consistency2/5

    Inconsistent naming: some tools use verb_noun (check_browser_connection, get_bookmark_content) while others use single verbs (classify, merge). Aliases further break patterns.

    Tool Count3/5

    20 tools is borderline high for a bookmark server. Many are aliases, inflating the count. Core functionality could be served with fewer tools.

    Completeness2/5

    Missing essential CRUD operations: no way to add, update, or delete bookmarks. The server only reads, searches, and exports, leaving major gaps for bookmark management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues