Skip to main content
Glama
masaodev

chrome-bookmarks-mcp

by masaodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrome-bookmarks-mcp

No user-submitted related servers found.

    Related Servers

    • chrome-bookmarks-mcp

      sirwilliamiv
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to search, reorganize, and clean up Chrome bookmarks with an interactive review UI and real undo support across Chromium-based browsers.
      136 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

    • bookmarks-mcp

      lussey820
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to search, browse, add, and delete Chrome and Edge bookmarks through the MCP protocol, using a local FastMCP server that directly reads and modifies browser bookmark files.
      5
      -

    • Chrome Bookmarks MCP

      JoshuaRamirez
      A
      license
      A
      quality
      A
      maintenance
      Manages Chrome's synced bookmarks through an MCP server and Chrome extension, enabling operations like listing, searching, adding, moving, and deduplicating bookmarks.
      17
      136 npm
      MIT

    • Chrome Bookmark MCP Server

      mamba-mental
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server implementation that provides seamless integration between Chrome bookmarks and AI assistants. This server enables AI models to access, search, analyze, and manage Chrome bookmarks through a standardized protocol.
      2
      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/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct operation: status, tree navigation, search, retrieval, create, update, move, and removal (single vs. tree). The overlap between get_tree, get_children, and get is clearly delineated by their descriptions.

    Naming Consistency5/5

    All tools follow a uniform bookmarks_<verb> pattern, with verbs like get_tree, get_children, search, create, update, move, remove, and remove_tree. This makes the API predictable and easy to navigate.

    Tool Count5/5

    11 tools is well-scoped for a bookmark management server. Each tool covers a necessary part of the lifecycle without redundancy or bloat.

    Completeness5/5

    The surface covers the full bookmark lifecycle: create, read (tree/children/get/search/recent), update, move, and delete (single and tree). The status tool handles connectivity, leaving no obvious gaps for typical bookmark operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources