LUCITRA AI Bookmark Organizer

Get started

Install once. Keep bookmark access under your control.

Start with the standalone Chrome extension. Add the local MCP companion only if you want Codex, Claude, or another approved client to work with your bookmarks.

macOS Node 20+ Chrome 138+ local by default

Requirements

What you need

Google Chrome

Chrome 138 or newer. Managed profiles may require the Web Store release.

Node.js

Node.js 20 or newer provides the local companion runtime and npx.

macOS

The automated Native Messaging installer currently supports macOS.

The MCP companion is optional.

Saving, organizing, asking questions, previewing moves, applying, and undoing all remain available without installing it.

01

Chrome extension

Install AI Bookmark Organizer

The Chrome Web Store listing will be the recommended path after approval. Until then, download the versioned GitHub release and load the unzipped directory.

Download extension ZIP
  1. Unzip ai-bookmark-organizer.zip.
  2. Open chrome://extensions.
  3. Enable Developer mode and select Load unpacked.
  4. Select the unzipped folder that directly contains manifest.json.
  5. Pin AI Bookmark Organizer from Chrome's extensions menu.
Managed Chrome can block unpacked extensions.

A ZIP cannot bypass organization policy. Use the Web Store build after approval.

02

Chrome identity

Copy the extension ID

On chrome://extensions, find AI Bookmark Organizer and copy its 32-character ID. The local Native Messaging host is restricted to this exact ID.

EXAMPLE FORMAT abcdefghijklmnopabcdefghijklmnop

An unpacked extension ID may differ between computers. The future Chrome Web Store release will provide one stable public ID.

03

Local companion

Run one npx setup command

Replace YOUR_EXTENSION_ID with the value from the previous step. The command installs an owner-only runtime and registers Chrome's local native host. 

npx --yes @lucitra/bookmark-agent-companion@1.2.0 setup \
  --extension-id YOUR_EXTENSION_ID
NO POSTINSTALL

The npm package has no dependencies or automatic install scripts.

EXPLICIT SETUP

System changes begin only when you invoke the visible setup command.

NO OPEN PORT

Chrome Native Messaging and an authenticated local socket connect the pieces.

04

Chrome approval

Restart Chrome and enable Agent Access

  1. Quit and reopen Chrome so it discovers the new native host.
  2. Open AI Bookmark Organizer and select Settings.
  3. Select Enable Agent Access and approve Native Messaging.
  4. Choose one bookmark folder or All bookmarks as the scope.
  5. Keep Read-only selected for the first connection.

Codex and Claude remain blocked until you select the matching provider and affirm the external-processing disclosure. Enabling the local bridge alone does not grant either provider access.

05

MCP client

Add bookmark tools to your agent

C

Codex

codex mcp add lucitra-bookmarks -- \
  npx --yes @lucitra/bookmark-agent-companion@1.2.0 \
  mcp --client codex

Then enable Codex under External AI processing in extension Settings.

CL

Claude Code

claude mcp add --transport stdio --scope user \
  lucitra-bookmarks -- \
  npx --yes @lucitra/bookmark-agent-companion@1.2.0 \
  mcp --client claude

Then enable Claude under External AI processing in extension Settings.

Start with a status check.

Ask your client: “Check my Lucitra bookmark agent status.”

06

Verification

Confirm the local installation

npx --yes @lucitra/bookmark-agent-companion@1.2.0 doctor

The command checks:

  • Local configuration and owner-only permissions
  • The copied dependency-free runtime
  • Chrome's Native Messaging manifest
  • The exact extension origin allowed by that manifest

doctor validates the installation. The MCP bookmarks_status tool validates the live Chrome connection and access policy.

Privacy boundary

What each mode can access

Mode Processing Approval
Standalone Chrome local AI or deterministic local rules Default; no companion required
Local MCP Approved bookmark metadata stays on the computer Agent Access + folder scope
Codex / Claude Approved metadata may reach the selected model provider Provider-specific disclosure and consent

Agent tools can search bookmark titles, URLs, hosts, and folder paths. They cannot fetch linked pages or delete bookmarks. Writes require a reviewed policy, an expiring prepared plan, and a matching client and folder scope.

Read the complete privacy policy

Lifecycle

Update or remove the companion

Update

Run setup with the newer published version and the same extension ID:

npx --yes @lucitra/bookmark-agent-companion@latest setup \
  --extension-id YOUR_EXTENSION_ID

Disconnect without uninstalling

In extension Settings, select Disable and revoke. Chrome removes the optional permission and external provider approvals.

Uninstall

npx --yes @lucitra/bookmark-agent-companion@1.2.0 uninstall

This removes the per-user Native Messaging registration, local authentication token, and copied runtime. It does not remove or change bookmarks.

Troubleshooting

Common setup issues

The npm package cannot be found

Confirm the package has been publicly released, your network can reach npm, and the command includes the full @lucitra/bookmark-agent-companion name.

Chrome says the companion is disconnected

Run doctor, restart Chrome, and verify that setup used the extension ID shown on the current computer.

The client says external provider access is not approved

Open extension Settings, select the matching Codex or Claude provider, read the disclosure, affirm consent, and save the access policy.

The client can search but cannot move bookmarks

Read-only is working as designed. Choose Allow reviewed changes only when you want the client to prepare and apply reversible organization plans.

Load unpacked is blocked by policy

Organization-managed Chrome profiles may require the public Chrome Web Store build. Local ZIP installation cannot bypass administrator policy.

Still stuck? Open a support issue.