Your agents are first-class users of your board. Ask Claude Code “where’s staging Datadog?” and it answers from your own bookmarks — no copy-pasting, no separate index.
claude mcp add --transport http tabhelm \
https://azbitemtneyfpghhzknk.supabase.co/functions/v1/mcp \
--client-id 08b802b0-8870-44f5-89d0-37aed5899c71 \
--callback-port 8080 There’s no client secret to paste — the exchange is secured by PKCE rather than a shared password.
Adding it doesn’t sign you in yet — nothing happens until you first use it.
/mcp to sign in/mcp Inside Claude Code. The first call opens your browser: sign in to TabHelm, then a consent screen names what’s asking and where your access would go. Approve it and you’re done — it stays connected and refreshes quietly from then on, so this is a one-time step.
Run /mcp again. tabhelm should now be listed as
connected, with eight tools. Then just ask it something — “what do you
know about my TabHelm?” is a good opener.
search_bookmarks | Find a bookmark by title, URL or note. Understands "last week". |
get_bookmark | Full detail for one bookmark, including why you saved it. |
list_board | Your tabs and cards, with counts — the shape of your board. |
list_launch_sets | Each card as a named set of links, ready to open. |
suggest_placement | Where a new link belongs, with a reason and a confidence. |
save_bookmark | Save a URL. Saving one you already have fills gaps instead of duplicating. |
move_bookmark | File a bookmark into a card, or back to the inbox. |
update_bookmark | Change a title, note or URL. |
Nothing can be deleted. An agent can save, file and edit, but there is no delete tool at all — so the worst case is a tidy-up you disagree with, not lost bookmarks. Launch sets hand back their links rather than opening tabs, because opening a tab is something your browser does, not a server.
--callback-port 8090 — it’s registered too. The
port has to be one we know about in advance, so only these two work.