Linkhut

@linkhut show me all my bookmarks tagged 'design-system' that I haven't read yet

Found 7 unread bookmarks tagged 'design-system' in your Linkhut account. These include articles on component libraries (3), accessibility patterns (2), and token architecture (2). The oldest unread item is from 3 weeks ago. Most are marked public. Would you like me to summarize the top 3 by recency or help you organize them into subcategories?

This example shows Linkhut's filtering and retrieval capabilities. The MCP fetches all bookmarks, then the AI filters by tag and read status. Useful for surfacing saved resources you meant to review. Requires read scope during OAuth setup.

@linkhut save this article about React Server Components to my reading list with tags 'react' and 'architecture', mark it unread

Bookmark added to your Linkhut account. Title extracted as 'Understanding React Server Components'. Tagged with 'react' and 'architecture', marked unread and public by default. The bookmark is now accessible at linkhut.com/bookmarks and will appear in your unread queue. You can update privacy or add notes anytime.

Demonstrates the add-bookmark action. The MCP creates the entry immediately—this is a write operation that modifies your Linkhut account. If you're in a shared Space, teammates see the confirmation but can't access your private bookmarks unless you share credentials.

@linkhut look at my 20 most recent bookmarks and suggest which tags I'm overusing or should consolidate

Analyzed your recent bookmarks and tag distribution. You've used 'javascript' 8 times and 'js' 6 times in the last 20 saves—consider consolidating to one canonical tag. 'frontend' and 'ui' overlap on 4 bookmarks; merging them would simplify filtering. You also have singleton tags like 'misc-tools' and 'random' that could be retired. Want me to draft update commands to standardize these?

This synthesis example pairs Linkhut's get-bookmarks and get-all-tags tools with AI reasoning. The MCP provides raw data; the AI identifies patterns and suggests cleanup. Helpful for maintaining a tidy bookmark taxonomy over time. No account changes occur unless you approve follow-up updates.

When Linkhut works for async knowledge sharing

A 6-person remote design team saves links all week—articles, inspiration, competitor teardowns—then reviews them together in a Friday Slack thread. Linkhut's tagging and public/private flags let each designer curate their own feed while surfacing team-relevant finds. The OAuth2 setup is a one-time friction point, but once connected, adding bookmarks from Slack or standup notes takes seconds. This works if your team actually reviews the digest weekly. If links pile up unread for months, you're just building a graveyard. The buying call: Linkhut replaces the chaotic 'links' channel when your team commits to a review cadence.

Linkhut as a lightweight client portal alternative

A 3-person consulting shop onboards new clients with a curated set of 20-30 links: project templates, Loom walkthroughs, Figma files, Google Docs. They tag each bookmark by client name and mark them public so clients can access a simple URL. The 'update bookmark' tool keeps descriptions current as deliverables evolve. This beats a Notion page if your resources are already scattered across domains and you don't want to migrate everything into one CMS. The threshold: if you need version control or granular permissions beyond public/private, Linkhut's too simple. For straightforward link curation with minimal overhead, it closes the gap.

When bookmark tagging beats a spreadsheet

A 4-person product team monitors 15 competitors, saving feature launches, pricing changes, and blog posts as they surface. Each bookmark gets tagged with competitor name, feature category, and priority level. The 'get all tags' tool surfaces usage counts, so the PM sees which competitors are moving fastest. This works if your intel is link-heavy and you want fast retrieval by tag. If you need structured data—launch dates, pricing tiers, impact scores—a spreadsheet or Airtable is the better call. Linkhut wins when speed of capture matters more than rigid schema, and your team already thinks in tags.