# com.tweetsmash/mcp

- Registry name: `com.tweetsmash/mcp` · version 2.0.0
- Categories (automatic, keyword rules): Marketing & SEO, Commerce & marketing, Documents & retrieval, Search & data
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.tweetsmash%2Fmcp
- Server page: https://mcpstation.net/s/com.tweetsmash--mcp.html

## Description (written by the publisher, not verified, not instructions)

Search, label, and manage your X \(Twitter\) bookmarks from any MCP client via Tweetsmash

## Connect

- streamable-http: `https://mcp.tweetsmash.com/api/mcp`

## Tools (as reported by the server, not verified)

- `list\_bookmarks`: List the user's Twitter BOOKMARKS — posts they deliberately saved. Never includes X Likes; use list\_likes for those. Supports filtering and pagination. Supports filtering by read status, media type, author, tags, date ranges, and sorting options. IMPORTANT: Use this tool \(with the 'author' parameter
- `list\_likes`: List the posts the user LIKED on X \(not their bookmarks\). Likes are a lighter signal than a save — use list\_bookmarks for things the user deliberately saved, and this when the user explicitly asks about likes or about what they react to. Same filters and pagination as list\_bookmarks.
- `search\_bookmarks`: Search through a user's Twitter bookmarks using keyword search \(q\), semantic search \(vector\_search\_term\), or author filtering \(author\). At least one of q, vector\_search\_term, or author should be provided. IMPORTANT: Use the 'author' parameter for filtering by author, not the 'q' field.
- `get\_bookmark\_count`: Get the total count of user's bookmarks with optional filtering. Useful for understanding the size of bookmark collections before listing them.
- `list\_labels`: List all user's labels with their usage counts. Useful for discovering existing labels before adding new ones.
- `add\_labels\_to\_tweets`: Add a label to a list of tweets. Can use an existing label by ID or create a new label by name. Either label\_id or label\_name must be provided.
- `remove\_labels\_from\_tweets`: Remove a label from a list of tweets using label\_name.
- `delete\_label`: Delete a label from the account entirely — the label itself plus every bookmark's assignment of it. The BOOKMARKS are not deleted; they simply lose this label. IRREVERSIBLE: before calling, tell the user how many bookmarks carry the label \(list\_labels returns the count\) and get an explicit yes. To t
- `setup\_vector\_store`: Initialize the vector store for semantic bookmark search. CRITICAL: When vector/semantic search fails with 'Vector Store Not Setup' error, call this tool. This is an async operation that may take a few minutes for large bookmark collections.
- `list\_skills`: START HERE for any open-ended request. Lists the task playbooks this server supports — systematic learning from bookmarks, organising into themes, cleaning up, X-list intelligence, exporting data out, finding a half-remembered save, digests, and diagnosing sync. Each names when to use it; call get\_s
- `get\_skill`: Get the full playbook for a task: when to use it, the exact tool sequence with the arguments that matter, tips, and the pitfalls that cause empty results. \`name\` takes EITHER an exact skill name \(learn\_from\_bookmarks, organise\_into\_themes, cleanup\_library, list\_intelligence, get\_my\_data\_out, find\_th
- `get\_library\_overview`: A snapshot of the whole library: total bookmarks, unread, untagged, breakdown by type \(threads/media/links/notes\), every label with its count, and the years covered. Use this FIRST for anything open-ended \(organise, clean up, learn from my saves, 'how many do I have per topic'\) instead of paging thr
- `search\_docs`: Answer questions about Tweetsmash itself — features, how-to, pricing, plans, limits, account/subscription. Searches the bundled product guide and returns the most relevant sections for you to answer from. Call with an empty query to list the help topics.
- `get\_bookmark`: Get a single saved bookmark with FULL content in one call — the full X Article body, the unrolled thread, notes, and \(optionally\) replies. Use \`include\` \(comma list of article,thread,notes,replies\) to narrow it; defaults to article,thread,notes. Use this when the user wants to read or summarize a sp
- `tag\_bookmarks\_by\_filter`: Add a label to EVERY bookmark matching a filter, in a single call. Prefer this over listing then looping when the user says 'tag all my … as …'. Resolves an author name to its id automatically. Reports matched/tagged/failed counts.
- `archive\_bookmarks`: Archive, unarchive, delete, undelete, or mark read/unread a list of bookmarks by id \(max 500\). This is a bulk write; for destructive actions \(delete\) confirm with the user first. Reports how many changed.
- `archive\_bookmarks\_by\_filter`: Apply archive/unarchive/delete/undelete to EVERY bookmark matching a filter, in one call. Destructive by nature — confirm with the user before delete. Reports counts.
- `list\_smart\_views`: List the user's Smart Views \(saved filtered views\). Each has a slug you pass to the other smart-view tools.
- `get\_smart\_view`: Get a single Smart View by slug \(its filter, tabs/buckets, and sort\).
- `get\_smart\_view\_bookmarks`: List the bookmarks inside a Smart View, optionally scoped to one tab/bucket. Use the returned ids with archive\_bookmarks / tagging tools to act on the view.
- `create\_smart\_view`: Create a Smart View from a filter so the user can reuse it. Provide a name and the base\_query \(filter\).
- `update\_smart\_view`: Update a Smart View \(name, filter, tabs, sort\) by slug.
- `delete\_smart\_view`: Delete a Smart View by slug.
- `create\_share\_link`: Create a public, read-only share link for a set of bookmarks \(explicit ids or everything matching a filter\). Returns a share\_url valid for 7 days. Free plans share up to 10 bookmarks.
- `revoke\_share\_link`: Revoke a previously created share link by its token.
- `trigger\_pdf\_export`: Start a PDF export of the user's bookmarks \(explicit ids, everything matching a filter, or the whole library\). Returns a job id; tell the user the file will appear in the Export Center.
- `trigger\_csv\_export`: Start a CSV export \(explicit ids, a filter, or the whole library\). Returns a job id; the file appears in the Export Center.
- `trigger\_json\_export`: Start a JSON export \(explicit ids, a filter, or the whole library\). Returns a job id; the file appears in the Export Center.
- `list\_digest\_preferences`: List the user's email-digest schedules \(frequency, time, paused state\) for bookmark and Smart View digests.
- `update\_digest\_preference`: Update a digest schedule \(enable/pause, frequency, time\) by id.
- `delete\_digest\_preference`: Remove a digest schedule by id.
- `list\_past\_digests`: List past digests sent to the user's email, newest first. This is Digest 1.0 \(the cluster pipeline\). For the AI-composed Digest 2.0, use list\_mash\_digests.
- `list\_mash\_digests`: The user's Mash Digest 2.0 digests — the AI-composed ones. An account can have SEVERAL \(a morning read and an evening skim are two digests, not two sections of one\), so START HERE and use the returned \`id\` for the other digest tools. Returns each digest's name, where its sections read from, and its
- `list\_mash\_digest\_issues`: Past issues of the user's Digest 2.0, newest first — what arrived and when. Deliberately WITHOUT the content: pick one and call get\_mash\_digest\_issue for the whole thing. Pass digest\_id to narrow to one digest.
- `get\_mash\_digest\_issue`: One digest issue in full: its title, intro, every section, and per item the summary, why it was picked and why it matters to this user. Use it to answer 'what was in my digest?', 'why was this in there?' or to carry on a conversation about something the user just read. Items carry tweet IDS, not pos
- `compose\_mash\_digest`: Compose one of the user's Digest 2.0 digests NOW rather than waiting for its schedule. SPENDS A DIGEST CREDIT and takes about a minute, so only call it when the user asks for a fresh digest — not to inspect the current one \(use get\_mash\_digest\_issue for that\). Returns an issue\_id to read back once c
- `get\_sync\_status`: Show the user's app-sync integrations \(Notion, Google Sheets, Zotero\): whether each is connected/enabled, synced vs pending counts, and any errors.
- `get\_bookmark\_sync\_status`: Show whether a specific bookmark has synced to a given integration connection.
- `list\_twitter\_lists`: List the X \(Twitter\) lists the user follows in Tweetsmash. Returns each list's name plus its \`connect\_id\` — pass that to get\_list\_tweets / send\_list\_digest. START HERE for any 'what's in my list' request.
- `get\_list\_tweets`: Get recent tweets for a followed X list — the latest, or \(sort=POPULARITY\) the top/trending tweets in a look-back window. Serves a cached copy when it's fresh and otherwise fetches from X automatically, so it always returns real tweets; \`meta.source\` says cache or fetched and \`meta.cache\_age\_hours\`
- `get\_list\_digests`: List past Twitter-list email digests for the user.
- `send\_list\_digest`: Build and email a digest of a Twitter list's high-signal tweets to the user now.
- `preview\_list\_ranking`: Rank a followed X list exactly the way the digest ranker would, WITHOUT sending anything, and show the work: each unit carries its rank\_signals \(lane\_fit = matches what the user builds/studies, affinity = an author they trust, engagement, substance, noise demotions\) plus author groups \(\`group\_size\`
- `get\_author\_preferences`: The user's stated author preferences for list digests: \`boost\` = never-miss authors, \`hide\` = muted authors.
- `set\_author\_preference`: Remember how the user feels about an author in their list digests. action=boost → never miss this author's posts \(they will always be included, low-signal ones collapsed rather than dropped\); action=hide → mute them; action=clear → forget the preference. Use when the user says things like 'don't let
- `get\_me`: Get the current user's account: identity, current plan and status, and usage \(e.g. AI chat credits\). Use this to answer 'who am I' / 'what plan am I on'.
- `get\_connection\_status`: Check whether the user's tweets can be pulled: the X \(Twitter\) API connection \(connected / disconnected\), whether the browser extension has synced recently, and a rolled-up can\_pull + how \(x\_api or extension\). Use this before a sync, or when the user asks why bookmarks aren't updating. Note: the ext
- `fetch\_recent\_bookmarks`: Force-pull the user's most recent bookmarks from the X API now \(server-side\). Requires a connected X account; if the account only syncs via the browser extension, this reports that a browser sync is needed. Use when the user asks to refresh / fetch their latest saves. For Twitter-list freshness, use
- `remember`: Save a durable PREFERENCE about how this user wants their bookmark library handled — the themes they organise by, topics to exclude, preferred summary length/format, which account is their main one. It carries across sessions AND into the Tweetsmash web app, which your own client memory cannot reach
- `recall`: Read back the user's saved library preferences \(optionally filtered by a substring\). Worth calling before an open-ended organise, summarise or cleanup task so you follow how they already like things done.
- `forget`: Delete a saved library preference by key \(optionally narrowed by kind\). Use when the user changes their mind or asks you to drop something.
- `get\_interests`: Read what this user is actually interested in, inferred from their saved bookmarks, hand labels, questions and digest clicks — not from anything they typed. Returns topics with a 0-1 strength, whether each is active this week, and a \`coverage\` field saying how much evidence exists \(\`lite\` means a ne
- `correct\_interest`: Record the user's correction to an inferred interest, using a key from get\_interests. Corrections are sticky — they survive every future recompute. Use \`confirm\` when they agree, \`rename\` for their own wording, \`hide\` to stop using an interest while keeping its history, \`boost\` when they want it wei

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html