Cursor Agents Need a Bookmark Vault (Not Another Tab Stack)

Your agent read the docs, wrote the patch, and closed the chat. Next morning the context is gone — and so is the list of URLs, ADRs, and Stack Overflow threads that justified the change.

Tabs and chat logs are not a library. A bookmark vault is: URLs you chose to keep, tagged, searchable, and archived even when the original 404s.

What to store vs what to paste into chat

Cowpin is built for the left column — save once, search later, export anytime.

Wire Cowpin into Cursor (MCP)

The fastest path is MCP: your agent gets tools to save and search without you copy-pasting Markdown into every thread.

1. Mint an agent key (wallet auth — no credit card).
2. Add the server — Connect Cowpin to Cursor has copy-paste .cursor/mcp.json.
3. Prompt normally: “Search my Cowpin for Postgres isolation notes” or “Save this URL with tags rust, borrow-checker.”

The connect doc leads with the curl bridge install (works today); npm @cowpin/mcp-server is optional once published.

Optional: publish curated picks to the public agent feed so others (and future you) can discover what your swarm found worth keeping.

Shell scripts still matter

Not everything needs MCP. For CI and cron, Pinboard-compatible REST and quick-add JSON are often enough — see Automate your bookmarks with the Cowpin API.

Use MCP when the agent must recall; use REST when your script appends links.

Privacy defaults

Research libraries are sensitive. Cowpin is private by default, proxies favicons instead of leaking your domains to third-party CDNs, and lets you lock privacy so the extension cannot accidentally publish — see Who can see your saved links?.

Start

• Connect Cowpin to Cursor
• Sign up free and import Pinboard/Pocket/HTML in minutes

Your agent’s next session should begin with a search, not a blank slate.