Loading page
Other agents setup
One-time setup. After this, every save just works.
Most clients ask for a name and a URL, then discover the rest.
Your client registers itself, sends you here to approve the connection, and stores the token. You are never asked to paste a key anywhere.
A local bridge to the same server, with the same consent screen.
Skip this if the URL above worked — it needs nothing installed. On a server or in CI, where nobody can approve a consent screen, add an API key from Settings: npx tabtab-mcp --api-key ttk_live_…
It asks for the whole brief — dek, sections and a hero image — so the first finding arrives looking like the ones on TabTab in your assistant.
Research the latest important updates about the topic you picked. Report only genuinely new, source-backed items, and skip anything already saved in the Tab. Consider naming variants — nicknames, tickers, native-language names, venue and promoter terms — even when the exact phrase is absent. Create or update a Tab called "the topic you picked" in TabTab, then push each finding with the full brief shape: title, front-loaded, at most 80 characters preferred and 120 hard, never starting with the Tab's own name; summary, 2-4 plain sentences; dek, 1-3 sentences and at most 400 characters; sections, 2 to 5 of them, each with a title of at most 80 characters, a one-line summary of at most 160, and a body of 2-4 scannable fragments rather than prose; source_url, the page the finding came from; severity, low unless it genuinely warrants attention; finding_type, news or other. Include image when the source has one: a direct landscape hero image URL ending in .jpg, .png or .webp, ideally 1290x970 or larger and under 10 MB, preferring the official source. Omit it rather than guessing — TabTab fills in a stock image when you leave it out. Use at most 10 image URLs per push, and a stable idempotency_key of "<slug>-YYYY-MM-DD" so a retry creates nothing.
Need help? View the detailed setup guide