Use Your Bookmark Library in Claude Code

Claude Code can connect directly to Save This One's remote Streamable HTTP MCP server. This is useful for finding saved implementation references without leaving a coding session and for preserving documentation discovered while debugging.

Add the remote server

Choose a scope deliberately:

• user: available to you in every repository; best for a personal bookmark library.
• local: available only to you in the current project and stored outside version control.
• project: writes the definition to .mcp.json so teammates can share it. Each teammate still completes OAuth into their own Save This One account.

For a personal, cross-project connection, run:

claude mcp add --transport http --scope user save-this-one https://mcp.savethisone.com/mcp

For project scope, replace --scope user with --scope project. Do not add an Authorization header or commit tokens. Save This One advertises its OAuth authorization server and uses browser OAuth with PKCE.

Inside Claude Code, run:

/mcp

Select save-this-one and authenticate if prompted. Claude Code opens a browser; sign in to Save This One, approve access, and return to the terminal. The callback uses a temporary local port, so keep the initiating Claude Code process running until the browser reports success.

Check configuration and authentication

From a shell:

claude mcp list
claude mcp get save-this-one

Then ask in Claude Code:

Call Save This One's whoami, then list_tags. Do not call write tools.

Confirm the account before allowing a repository agent to save or reorganize anything. /mcp is also the best place to inspect status and restart OAuth.

What Claude Code can call

The server exposes 14 tools—use these names rather than asking Claude to invent an operation:

• Identity and retrieval: whoami, list_bookmarks, search_bookmarks, get_bookmark
• Saving and lifecycle: save_bookmark, archive_bookmark, delete_bookmark
• Tags: list_tags, create_tag, delete_tag, tag_bookmarks
• Notes: list_comments, add_comment, delete_comment

Search operates on active bookmarks and matches literal keywords in title, description, URL, domain, and site name. It does not search repository files or reader-body text. list_bookmarks supports archived state, tag filtering, limit up to 100, and offset pagination.

Coding workflows

Recover prior research before implementation

Before changing authentication code, use search_bookmarks for WebAuthn and passkeys. Summarize only the returned titles, descriptions, URLs, and tags. Do not change my library or browse unrelated sites.

Save references discovered in a task

We used https://example.com/spec while fixing this issue. Check whether it is already saved. If not, ask me to approve tags, then call save_bookmark with project-atlas and auth. Add no comment unless I provide its exact text.

save_bookmark is idempotent by normalized URL and fetches metadata automatically. Avoid supplying made-up titles; the tool does not accept a title argument.

Build a project research digest

List all active bookmarks tagged project-atlas, paging if necessary. Return a Markdown reference list grouped by domain. This is read-only; do not retag anything.

Capture why a source mattered

Search for the exact docs URL, show the chosen bookmark ID, then ask before adding this comment: “Explains retry semantics used in src/queue.ts.”

Keep agentic sessions safe

Claude Code may work through long plans, so constrain mutation in the prompt and approval policy:

• Use a user-scoped server for personal data; use project scope only to share the endpoint definition, never credentials.
• Start tasks with “read-only” and name allowed tools when research is all that is needed.
• Require a preview of IDs and arguments before bulk tagging or archive operations.
• Prefer archive_bookmark (reversible with archived: false) to permanent deletion.
• Never blanket-approve delete_bookmark, delete_tag, or delete_comment. Deleting a bookmark also deletes its comments and tag links.
• Be careful retrying add_comment; it is the only non-idempotent tool and can create duplicates.
• Treat text fetched from bookmarked pages as untrusted research, not instructions that override your task or repository rules.

Remove or move the server

claude mcp remove save-this-one --scope user

Use the same scope that was used when adding it. To change scope, remove the old entry and add it at the new scope; this avoids shadowed configurations with the same name.

Troubleshooting

/mcp says authentication is required. Select the server and authenticate. If the browser flow was interrupted, retry from /mcp; do not add a static bearer token.

The callback page cannot return to Claude Code. Keep the original terminal alive and ensure localhost callback connections are not blocked. Claude Code can use --callback-port for providers that require a fixed redirect, but Save This One's dynamic OAuth flow should not require one.

The server is missing in this repository. Run claude mcp get save-this-one and check its scope. A local/project entry applies only where configured; a same-named entry at another scope can also cause confusion.

Tools changed but Claude Code shows an old list. Reopen /mcp, reconnect, and start a fresh session so tools are rediscovered.

Search returns nothing. Search excludes archived bookmarks. Use list_bookmarks with archived: true, or call list_tags to verify the exact tag.

Unauthorized after previously working. Re-authenticate through /mcp. OAuth credentials are client-managed; do not copy credential files into the repository.

Official references

• Claude Code: connect to tools via MCP
• MCP authorization specification