skip to content
xmarkVol. MMXXVI
docsblog
sign insign upjoin
Plate ∗.for builders

xmark for builders.

Your bookmarks are a stack-decisions journal.

You save threads about the tools you use — choices, gotchas, performance benchmarks, post-mortems. xmark turns that into a queryable record of how the industry thinks about your stack.

Questions that work

"What did I save about Postgres vs SQLite for small teams?"

— what happens: Returns the comparative threads with citations.

"Threads where someone reversed their position on [framework]."

— what happens: Semantic search picks up reversal language: "I was wrong about", "changed my mind on".

"What gotchas did people post about [tool] last quarter?"

— what happens: Time-windowed search across the bookmark history.

A workflow that works

  1. 01.Bookmark intentionally — when you save, take a half-second to notice why.
  2. 02.Search xmark before locking a stack decision.
  3. 03.Use the REST API to feed bookmarks into your team's wiki or Slack.
  4. 04.The MCP server lets your IDE-side agent query your own bookmark library.

Most builders use xmark inside Claude Code via the MCP server. It's a one-line install.

Sign up — $5/month →

ready to get started?

sign up in seconds. free to start, no credit card required.

get started freesign in
xmark

built by jclvsh

support

email feedbacktwitter @jclvsh

legal

privacy policyterms of servicedata deletion

© 2026 xmark. all rights reserved.