hermoso 0.1.160 → 0.1.161

package/README.md

@@ -5,7 +5,7 @@ scripts. Research the ads already winning in a market, generate finished image &
 composited in, copy + CTA included), publish them to your own social channels, and build & manage the ad
 campaigns behind them — all over [MCP](https://modelcontextprotocol.io) tools, a CLI, or installable Claude skills.
 
-**716 tools.** `tools/list` is always the authoritative set; `hermoso_capabilities` (free) returns the live model
+**718 tools.** `tools/list` is always the authoritative set; `hermoso_capabilities` (free) returns the live model
 catalog with exact per-render credit costs plus the full capability map.
 
 **What it connects to.** Ad platforms: Meta, Google Ads, TikTok Ads, LinkedIn Ads, Reddit Ads, X Ads,
@@ -119,7 +119,7 @@ block entirely if you signed in above; it is there for CI, where the process can
 
 Then ask your agent: *“Generate an image ad with Hermoso.”*
 
-### What the 716 tools cover
+### What the 718 tools cover
 
 **Ad spy / research** — `find_competitors`, `competitor_teardown`, `pull_competitor_ads`, `research_ads`; the
 Meta / Google / LinkedIn ad libraries (`search_meta_ads`, `search_google_ads`, `search_linkedin_ads`); organic

package/mcp/client.mjs

@@ -177,6 +177,31 @@ export function forgetWorkspaceScope() {
   const ctx = mcpCtx.getStore();
   if (ctx) delete ctx._storeSuffix;
 }
+// ── WHICH PROVIDERS THIS WORKSPACE HAS ACTUALLY CONNECTED (2026-08-26) ───────────────────────────────────────────
+// Read ONCE per session, at `initialize`, and handed to registerTools so the roster it advertises carries only
+// tools the caller can actually use — see mcp/roster-scope.mjs for the law and applyToolGates for the seam.
+//
+// `/api/connectors/providers` and NOT `/api/connectors`: the full route does a live-token label backfill and a
+// per-provider scope-drift read, i.e. outbound provider calls, and this sits on the handshake every client makes.
+// The lean route answers from the store alone and resolves the workspace exactly the way the Studio's own
+// connector read does (brand-shared from the owner's scope + personal from the caller's).
+//
+// NEVER THROWS, AND THAT IS THE WHOLE CONTRACT. A read that fails for any reason — an older server with no such
+// route, a store blip, no bearer at all — returns `readOk:false`, which makes toolHeldBackByConnectors answer
+// false for every tool and ships the FULL roster. A failed read must never be able to remove a paying customer's
+// tools ([[failed-read-is-not-empty]]); the cost of being wrong in this direction is a slightly larger roster.
+//
+// DELIBERATELY NOT MEMOIZED. It is one call per session; caching it would be the one way a user who connects an
+// account and reconnects their client still does not see the tools, and on the hosted twin a module-level cache
+// would be a cross-tenant leak besides.
+export async function connectedProviders() {
+  try {
+    const r = await apiGet('/api/connectors/providers');
+    const list = Array.isArray(r?.providers) ? r.providers : null;
+    if (!list) return { connected: new Set(), readOk: false }; // a shape we do not recognise is a failed read
+    return { connected: new Set(list.filter((p) => typeof p === 'string' && p)), readOk: true };
+  } catch { return { connected: new Set(), readOk: false }; }
+}
 // Upload raw file BYTES to /api/upload (150MB, persists → returns {url,kind,bytes}). Overrides the JSON content-type so
 // the server reads the raw body. Lets an agent post ARBITRARY user files (not just Hermoso renders).
 export async function apiUpload(p, buf, { contentType = 'application/octet-stream', fileName = '' } = {}) {

package/mcp/hermoso-mcp.mjs

@@ -9,7 +9,7 @@
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import { registerTools, MCP_INSTRUCTIONS, parseToolScope } from './tools.mjs';
-import { API_BASE } from './client.mjs';
+import { API_BASE, connectedProviders } from './client.mjs';
 
 // instructions = the full capability map (ad spy · create · raw model playground · account) — one source of truth
 // in tools.mjs, shared with the hosted connector (http.mjs), so every surface tells agents the same breadth.
@@ -27,7 +27,14 @@ const server = new McpServer({ name: 'hermoso-mcp', version: '1.0.0' }, {
 // people's configs today. Renaming a variable someone already set is how a working setup goes quiet.
 const _scope = parseToolScope(process.env.HERMOSO_TOOLS || process.env.HEIST_TOOLS);
 if (_scope.error) { console.error(`[hermoso-mcp] ${_scope.error}`); process.exit(1); }
-registerTools(server, { only: _scope.groups });
+// AND SCOPED TO WHAT THIS WORKSPACE HAS CONNECTED, not only to the groups asked for (2026-08-26). A tool bound to
+// a provider nobody has connected can only answer `401 {connector:'<p>'}`, so listing it costs the caller context
+// on every turn and buys them nothing — and a roster far past the 30-50 tool accuracy cliff is what makes a model
+// pick the wrong tool. ONE read, here at startup; it NEVER throws and a failed read ships the FULL roster
+// ([[failed-read-is-not-empty]]). Awaited before registerTools because the gate reads it at registration time —
+// wiring it after would leave `readOk:false`, the gate would fail open, and the change would be silently inert.
+const _conn = await connectedProviders();
+registerTools(server, { only: _scope.groups, connectors: _conn });
 
 const transport = new StdioServerTransport();
 await server.connect(transport);

package/mcp/http.mjs

@@ -17,7 +17,7 @@ import { randomUUID } from 'node:crypto';
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js';
 import { registerTools, MCP_INSTRUCTIONS, parseToolScope } from './tools.mjs';
-import { mcpCtx } from './client.mjs';
+import { mcpCtx, connectedProviders } from './client.mjs';
 
 // Mount the remote connector onto the Express app. No-op unless explicitly enabled + auth-backed.
 // `verifyBearer(token) -> {userId, accountId, email} | null` MUST be supplied by the caller (the real auth seam).
@@ -209,6 +209,10 @@ export function mountRemoteMcp(app, { verifyBearer, publicBaseUrl } = {}) {
     // `widgetHost` withholds the two commerce tools from ChatGPT (see registerTools). It is passed HERE as well
     // as on the session path because OpenAI's own tool scanner reads this anonymous discovery roster — gating
     // only the authenticated path would leave both tools listed in the submission.
+    // NO `connectors` HERE, DELIBERATELY. There is no authorization on this request, so there is no workspace to
+    // scope to and nothing honest to read — and a registry crawler or an agent deciding whether to connect MUST
+    // see the real catalog, not a zero-connector one. registerTools treats an absent `connectors` exactly like a
+    // failed read: full roster. Do not "fix" this by reading the workspace off the request; it is forgeable.
     registerTools(server, { only: scope?.groups, widgetHost: isWidgetHost(clientInfoOf(req.body), req) }); // metadata only — tools/list never invokes a handler, and tools/call can't reach here
     const transport = new StreamableHTTPServerTransport({ sessionIdGenerator: undefined, enableJsonResponse: true });
     res.on('close', () => { try { transport.close(); server.close(); } catch {} });
@@ -247,8 +251,22 @@ export function mountRemoteMcp(app, { verifyBearer, publicBaseUrl } = {}) {
       const scope = scopeFor(req, res);
       if (scope === false) return; // unknown group — already answered 400, and nothing was allocated
       sweepSessions(); // make room before allocating, so the cap is a ceiling and not a suggestion
+      // ── WHAT THIS CALLER CAN ACTUALLY USE (2026-08-26) ────────────────────────────────────────────────────────
+      // One free store read, on the ONE request per session that mints the roster, so the tools we advertise are
+      // the tools their workspace can call. A connector-bound tool for an unconnected provider can only answer
+      // `401 {connector:'<p>'}`; carrying it costs the caller context every turn and pushes the roster further
+      // past the 30-50 tool accuracy cliff. The MCP spec permits exactly this and nothing looser — the tool set
+      // "MAY vary by the authorization presented on the request … since credentials are per-request input, not
+      // connection state" (rev 2026-07-28, Tools ▸ Capabilities) — which is why it is keyed to the BEARER and not
+      // to the connection or to a query parameter.
+      //
+      // INSIDE `mcpCtx.run`, because that store is what puts this caller's token on the outbound /api call. Read
+      // it outside and it would go out unauthenticated, answer 401, and — correctly, by its own contract — fail
+      // OPEN with the full roster, so the whole change would be silently inert. Never throws; see
+      // connectedProviders() ([[failed-read-is-not-empty]]).
+      const connectors = await mcpCtx.run({ token, remote: true, client: rememberedClient(req) }, () => connectedProviders());
       const server = new McpServer({ name: 'hermoso', version: '1.0.0' }, { instructions: MCP_INSTRUCTIONS });
-      registerTools(server, { only: scope.groups, widgetHost: isWidgetHost(entry?.client || clientInfoOf(req.body), req) }); // the SAME tools as stdio (minus any the caller scoped out) — and every /api call they make carries this user's token
+      registerTools(server, { only: scope.groups, connectors, widgetHost: isWidgetHost(entry?.client || clientInfoOf(req.body), req) }); // the SAME tools as stdio (minus any the caller scoped out) — and every /api call they make carries this user's token
       const transport = new StreamableHTTPServerTransport({
         // CSPRNG, per the spec's SHOULD for session ids (Math.random() is not one).
         sessionIdGenerator: () => 'sess_' + randomUUID().replace(/-/g, ''),

package/mcp/roster-scope.mjs

@@ -0,0 +1,125 @@
+// ── THE CONNECTOR SCOPE — ONE LAW, TWO SURFACES (2026-08-26) ─────────────────────────────────────────────────────
+//
+// WHICH CONNECTOR A TOOL NEEDS, and therefore whether carrying it in a roster buys the caller anything. Shipped
+// first for the Studio chat (lib/studio-roster.mjs, which re-exports every symbol below), and lifted here so the
+// MCP twins can apply the IDENTICAL decision. It lives in mcp/ rather than lib/ for one mechanical reason: the
+// published npm package (cli/) ships `cli/mcp/**` and nothing else, so `./roster-scope.mjs` is the only path that
+// resolves from BOTH mcp/tools.mjs and its byte-identical cli/mcp/tools.mjs twin.
+//
+// WHY GATE ON THE CONNECTION AT ALL. A connector-bound tool for a provider the account has not connected can only
+// ever answer `401 {connector:'<p>'}` — "not connected has ONE shape". Carrying it buys the caller nothing, costs
+// them context on every turn, and actively harms them: a roster many times past the 30–50 tool accuracy cliff is
+// exactly what makes a model pick the wrong tool. The MCP spec (rev 2026-07-28, Tools ▸ Capabilities) blesses this
+// precise shape and no other: the tool set "MUST NOT vary per-connection or as a side effect of other requests on
+// the connection. The set MAY vary by the authorization presented on the request — for example, returning only the
+// tools the caller's granted scopes permit — since credentials are per-request input, not connection state."
+//
+// FIVE SAFETY PROPERTIES, each mutation-tested, because the failure mode of getting this wrong is INVISIBLE — a
+// silently missing tool reads as the model refusing, not as a bug:
+//
+//   1. **A failed connector read is never a refusal.** `readOk:false` holds back NOTHING. An unreadable store must
+//      never manufacture a capability loss ([[failed-read-is-not-empty]]).
+//   2. **An UNMAPPED tool is never held back.** The rules below are an allow-list of things we can justify, not a
+//      classifier. Anything this module cannot confidently attribute to a connector stays in the roster — which is
+//      what makes adding a tool safe: tool N+1 keeps working, it just does not get the saving.
+//   3. **Every provider named here must exist in the live connector registry.** A typo'd provider id would match
+//      nothing in `connected` and silently drop its whole family FOREVER, on every account. The check asserts the
+//      rule table against server.js's own CONNECTOR_INFO keys.
+//   4. **Research is never gated** — see NEVER_GATE below, and note the measured result on the MCP roster: of the
+//      18 tools in the `research` group, the `core` group and the `workspace` group, ZERO are connector-mapped.
+//   5. **A tool we did not register is not ours to filter.** Both callers hand these functions OUR tool names only;
+//      a user's own MCP server may call something `search_youtube_transcripts` and it must never be touched.
+//
+// Pure by design so the checks RUN these functions rather than reading the source. NO IMPORTS: the cli twin is
+// rsync'd into a published package that has no lib/ and no repo around it.
+// RESEARCH IS NEVER GATED, AND THIS LIST IS THE REASON THE WHOLE CHANGE IS SAFE.
+//
+// The ad libraries and organic social search run on OUR ScrapeCreators key, not on the user's connection — a brand
+// with nothing connected can and must still spy on its competitors' Meta ads. But their NAMES look exactly like
+// connector tools: `search_meta_ads` contains `_meta_`, `search_youtube` contains `youtube`. Six of the nine would
+// have been silently gated by the rules below, which would have broken the product's single most-used feature for
+// every new account — the exact users this change exists to protect.
+//
+// DERIVED, NOT HAND-LISTED. `tools/studio-roster-check.mjs` asserts this set is a SUPERSET of server.js's own
+// `SC_WINDOW_TOOLS` — the set the route already uses to decide which tools take a ScrapeCreators balance window.
+// So a tenth SC-backed tool added there fails the suite rather than quietly losing research for zero-connector
+// accounts. Anything ScrapeCreators pays for, the user reaches without connecting anything.
+//
+// NOTE what is deliberately NOT here: `search_instagram_hashtag`, `instagram_profile`, `search_threads_keyword`,
+// `discover_tiktok_creators`, `tiktok_creator_info`. Those read the PLATFORM's data through the USER'S token
+// (Business Discovery, the Threads API, TikTok's Creator Marketplace) — free to us, but impossible without the
+// connection, so gating them is correct.
+export const NEVER_GATE = new Set([
+  'search_meta_ads', 'search_google_ads', 'search_linkedin_ads', 'search_tiktok',
+  'search_instagram', 'search_youtube', 'search_reddit', 'search_threads', 'scrapecreators_fetch',
+]);
+
+// Tool-name → connector provider. ORDERED: the first match wins, so the more specific pattern must come first.
+//
+// THE ORDER IS LOAD-BEARING AND IS THE EASIEST THING TO GET WRONG. Six platforms hold TWO independent connections —
+// posting and ads are separate consents with separate tokens (CLAUDE.md records this explicitly for TikTok: "IT IS
+// A SEPARATE CONNECTION FROM THE `tiktok` POSTING CONNECTOR", and the same split is real for X, Pinterest, Reddit,
+// Snapchat and Microsoft). So `*_tiktok_ads_*` must be tested BEFORE the bare `tiktok` rule, or every ads tool
+// would be gated on the posting connector and a user with TikTok Ads connected but not TikTok posting would lose
+// the whole ads family they are paying for.
+export const TOOL_PROVIDER_RULES = [
+  // ── ads platforms that are their OWN connection (must precede the posting rules below) ──
+  [/_tiktok_ads_|^tiktok_ads_/, 'tiktok_ads'],
+  [/_x_ads_|^x_ads_/, 'x_ads'],
+  [/_pinterest_ads_|^pinterest_ads_/, 'pinterest_ads'],
+  [/_reddit_ads_|^reddit_ads_/, 'reddit_ads'],
+  [/_snapchat_ads_|^snapchat_ads_/, 'snapchat_ads'],
+  [/_microsoft_ads_|^microsoft_ads_|_microsoft_merchant_/, 'microsoft_ads'],
+  [/_apple_ads_|^apple_ads_/, 'apple_ads'],
+  [/_openai_ads_|^openai_ads_/, 'openai_ads'],
+  // Google Ads owns Merchant Center + the Ads↔Analytics link (both are Google Ads API surfaces, not GA4 ones).
+  [/_google_ads_|^google_ads_|_merchant_|^merchant_|^list_merchant_|link_google_ads_to_analytics/, 'google_ads'],
+  // ── LinkedIn: ads and posting share ONE connection (the Advertising API grant carries w_organization_social —
+  //    see [[linkedin-connector-live]]), so both families gate on the single `linkedin` provider. ──
+  [/linkedin/, 'linkedin'],
+  // ── Meta: ads management AND FB/IG posting are one connector ([[meta-integration]]). Threads is separate. ──
+  [/^threads_|_thread$|_threads_|^(list|search|reply_to|repost|delete|hide)_thread/, 'threads'],
+  [/_meta_|^meta_|_meta$|instagram|whatsapp/, 'meta'],
+  // ── analytics / measurement, each its own connection ──
+  [/_analytics_|^analytics_(realtime|report)$|analytics_compatibility|analytics_stream/, 'google_analytics'],
+  [/mixpanel/, 'mixpanel'],
+  [/tag_manager/, 'google_tag_manager'],
+  [/search_console/, 'google_search_console'],
+  [/bing_webmaster/, 'bing_webmaster'],
+  [/posthog/, 'posthog'],
+  [/amplitude/, 'amplitude'],
+  // ── posting-only channels ──
+  [/youtube/, 'youtube'],
+  [/google_business|business_location/, 'google_business'],
+  [/_drive_|^list_drive|^get_drive|^create_drive|^save_to_drive$|_doc$|^read_doc|^create_doc|^update_doc|^append_to_doc|sheet/, 'google_drive'],
+  [/onedrive/, 'microsoft_onedrive'],
+  [/bluesky/, 'bluesky'],
+  [/telegram/, 'telegram'],
+  [/^post_to_tiktok$|^tiktok_|_tiktok_/, 'tiktok'],
+  [/^post_to_x$|^delete_x_post$|^send_x_dm$|^list_x_dms$|^x_(mentions|post)/, 'x'],
+  [/pinterest/, 'pinterest'],
+  [/reddit/, 'reddit'],
+  [/snapchat/, 'snapchat'],
+];
+
+// The provider a tool needs, or null when this module cannot attribute it. null ⇒ NEVER dropped (property 2).
+export function toolProvider(name) {
+  const n = String(name || '');
+  if (!n) return null;
+  if (NEVER_GATE.has(n)) return null;   // research runs on our key — checked FIRST, before any pattern can claim it
+  for (const [re, provider] of TOOL_PROVIDER_RULES) if (re.test(n)) return provider;
+  return null;
+}
+// THE ONE DECISION, and the only one either surface is allowed to make. `conn` is `{connected, readOk}` — the
+// shape both the Studio route's connector read and the MCP transports' `/api/connectors/providers` read produce.
+//
+// Returns TRUE only when we KNOW the read succeeded AND we can attribute the tool to a provider AND that provider
+// is not connected. Every other answer is FALSE, i.e. keep it — which is properties 1 and 2 expressed as the
+// default rather than as two branches somebody could forget to write.
+export function toolHeldBackByConnectors(name, conn) {
+  if (!conn || !conn.readOk) return false;                       // property 1 — fail OPEN on an unreadable store
+  const p = toolProvider(name);
+  if (p === null) return false;                                  // property 2 — unmapped is never held back
+  const on = conn.connected instanceof Set ? conn.connected : new Set(conn.connected || []);
+  return !on.has(p);
+}

package/mcp/tools.mjs

@@ -11,6 +11,10 @@ import { ResourceTemplate } from '@modelcontextprotocol/sdk/server/mcp.js';
 // The UTF-16 well-formedness law — see wellFormedServer() below for why it is applied here, and
 // ./well-formed.mjs for why that specifier is the only one that can work in a byte-identical twin.
 import { wellFormedValue, wellFormedString } from './well-formed.mjs';
+// WHICH CONNECTOR A TOOL NEEDS — the same table and the same decision the Studio chat applies (lib/studio-roster.mjs
+// re-exports every symbol from here). `./roster-scope.mjs` is the only specifier that resolves in a byte-identical
+// twin, for the same reason ./well-formed.mjs is. See applyToolGates() for the seam and roster-scope.mjs for the law.
+import { toolHeldBackByConnectors } from './roster-scope.mjs';
 
 const JOB_TIMEOUT = +(process.env.HERMOSO_JOB_TIMEOUT_MS || process.env.HEIST_JOB_TIMEOUT_MS || 10 * 60 * 1000);
 const abs = (u) => (u && u.startsWith('/') ? API_BASE + u : u); // /generated/x.mp4 → clickable absolute URL
@@ -189,6 +193,19 @@ export const MCP_INSTRUCTIONS = [
   '• RAW MODELS, prompt only: generate_image / generate_video with useBrand:false, generate_voice, generate_text, upload_file (any local or external file becomes a URL every publish, schedule and ad tool accepts).',
   '• PUBLISH & SCHEDULE to the user\'s OWN accounts: post_to_meta (+Threads), post_to_x, post_to_linkedin, post_to_tiktok, post_to_youtube, post_to_pinterest, post_to_reddit, post_to_bluesky, post_to_telegram, post_to_google_business; schedule_post, list_scheduled, reschedule_post, cancel_scheduled; list_connectors, list_connector_accounts, set_connector_accounts.',
   '• ADS on eleven platforms, their accounts and their money: create_meta_campaign / _adset / _ad, create_google_ads_campaign / _ad_group / _ad and the TikTok, LinkedIn, Pinterest, Reddit, Microsoft and OpenAI equivalents; meta_insights, google_ads_report and the per-platform reports. Everything is created PAUSED and read back before it is described.',
+  // ── YOUR ROSTER IS NOT THE PRODUCT (2026-08-26) ──────────────────────────────────────────────────────────────
+  // The roster is scoped to the accounts this workspace has connected, because a tool for an unconnected provider
+  // can only answer 401. That is a saving, and it has ONE failure mode, which this line exists to prevent: an
+  // agent reads its roster as the boundary of what exists and tells the user we do not support their platform
+  // ([[prompt-rosters-go-stale]] — our own prose has already refused shipped capability on five surfaces).
+  //
+  // TWO CONSTRAINTS DECIDE ITS POSITION AND ITS LENGTH, and both are real budgets someone else is paying.
+  // POSITION: immediately AFTER the ADS bullet, because some hosts truncate this string to ~2KB and all five areas
+  // plus "ADS on eleven platforms" must stay inside that window — put it above and it evicts the ads bullet, which
+  // causes the exact failure it exists to stop. LENGTH: §2d of agent-surface-guidance-check caps the whole string,
+  // so it says only what is NEW and points at nothing already named below — `list_connectors`, `Workspace ▸
+  // Connectors`, `?connect=<provider>` and the CLI escape hatch are all already in here, further down.
+  'A tool NOT in your roster is filtered out — that account is not connected here. Never say Hermoso lacks a platform.',
   // SECOND LINE, before the capability map: those four jobs read as four STAGES, and by the time an agent has
   // scrolled the map it has already decided Hermoso is a funnel it must enter at the top. See INDEPENDENCE above.
   // NOT REPEATED HERE ANY MORE: the head above states independence in its own first sentence, and every byte
@@ -1894,13 +1911,21 @@ const makeEnableToolsHandler = (ctx) => async ({ groups }) => {
   if (unknown.length) return { content: [{ type: 'text', text: `Unknown tool group${unknown.length > 1 ? 's' : ''}: ${unknown.join(', ')}. Valid: ${TOOL_GROUP_NAMES.join(', ')} — or 'all'.` }], isError: true };
   const active = ctx.enabledGroups, groupOf = ctx.groupOf, handles = ctx.handleOf;
   const added = expand.filter((g) => !active.has(g));
-  let n = 0;
+  let n = 0, heldBack = 0;
   for (const g of added) {
     active.add(g);
     for (const [name, grp] of Object.entries(groupOf)) {
       if (grp !== g) continue;
       const h = handles[name];
-      if (h) { try { h.enable(); n++; } catch {} }
+      if (!h) continue;
+      // THE GROUP FLIP MUST NOT UNDO THE CONNECTOR GATE (2026-08-26). Enabling a group is a statement about SIZE —
+      // "I am willing to carry these schemas" — not a claim that the workspace has connected eleven ad platforms.
+      // A blind `h.enable()` here would have re-listed every tool applyToolGates had just held back, so the saving
+      // would survive exactly until the first `enable_tools(['ads'])`. Counted, not silently skipped: the reply
+      // says how many and why, because a group that turns on "8 tools" when the agent expected 240 with no
+      // explanation is the [[prompt-rosters-go-stale]] failure — the agent concludes the capability is missing.
+      if (toolHeldBackByConnectors(name, ctx.conn)) { heldBack++; continue; }
+      try { h.enable(); n++; } catch {}
     }
   }
   const enabled = TOOL_GROUP_NAMES.filter((g) => active.has(g));
@@ -1922,14 +1947,28 @@ const makeEnableToolsHandler = (ctx) => async ({ groups }) => {
   // NOT DELETED, deliberately. It still works on stdio and in the CLI, where the client re-lists, and deleting it
   // there would remove the only in-session route to the two opt-in groups. Made honest, not removed.
   const fixedRoster = hostRendersWidgets();
+  // NEVER "that platform is not supported". The tools exist, are built and are live; they are simply not listed for
+  // an account that has not connected the platform yet, because they could only answer 401. Say that, and say where
+  // the one-click fix is — the failure this sentence prevents is an agent telling a user we cannot run their ads.
+  const held = heldBack
+    ? ` ${heldBack} more tool${heldBack === 1 ? ' is' : 's are'} built and ready but not listed because their account is not connected in this workspace yet — Hermoso supports them all; connect the account under Workspace ▸ Connectors (https://app.hermoso.ai/?connect=<provider>, or list_connectors to see what is linked) and they appear.`
+    : '';
   const route = 'reconnect with `?tools=all` on the server URL, or run the `hermoso` CLI, which reaches every'
     + ' tool with no roster at all.';
-  const note = added.length
-    ? (fixedRoster
-      ? `Switched on ${added.join(', ')} server-side — but THIS host fixed its tool list when the connection was made and will not pick up the ${n} new tool${n === 1 ? '' : 's'} until it reconnects, so do not expect to see them in this conversation. To use them, ${route} Active groups: ${enabled.join(', ')}.`
-      : `Switched on ${added.join(', ')} — ${n} more tool${n === 1 ? '' : 's'} are callable now. If they do not appear your client has cached its tool list, in which case ${route} Active groups: ${enabled.join(', ')}.`)
-    : `Already on: ${expand.join(', ')}. Nothing changed. Active groups: ${enabled.join(', ')}.`;
-  return ok(note, { enabled, added, toolsAdded: n, note, rosterFixedForThisConnection: fixedRoster });
+  // A CACHED CLIENT AND AN UNCONNECTED ACCOUNT ARE DIFFERENT DIAGNOSES, AND ONLY ONE OF THEM IS EVER TRUE HERE
+  // (2026-08-26). The two branches below tell an agent that if the tools do not appear, its client cached the
+  // roster — correct when we really did enable something. When nothing was enabled BECAUSE nothing is connected,
+  // that sentence sends the agent to reconnect its client, which provably cannot help, and the reconnect it is
+  // told to try will produce the identical roster. So the zero-added case answers with the real cause and the
+  // real fix instead, and says the platforms exist. Same law as the read-back rule: report the measurement.
+  const note = !added.length
+    ? `Already on: ${expand.join(', ')}. Nothing changed. Active groups: ${enabled.join(', ')}.`
+    : (n === 0 && heldBack
+      ? `Switched on ${added.join(', ')} server-side, but nothing new is listed:${held} Active groups: ${enabled.join(', ')}.`
+      : fixedRoster
+        ? `Switched on ${added.join(', ')} server-side — but THIS host fixed its tool list when the connection was made and will not pick up the ${n} new tool${n === 1 ? '' : 's'} until it reconnects, so do not expect to see them in this conversation. To use them, ${route}${held} Active groups: ${enabled.join(', ')}.`
+        : `Switched on ${added.join(', ')} — ${n} more tool${n === 1 ? '' : 's'} are callable now. If they do not appear your client has cached its tool list, in which case ${route}${held} Active groups: ${enabled.join(', ')}.`);
+  return ok(note, { enabled, added, toolsAdded: n, toolsAwaitingConnection: heldBack, note, rosterFixedForThisConnection: fixedRoster });
 };
 
 // The per-session scope every roster needs, whether it was built or replayed. ONE builder so the two paths cannot
@@ -1937,13 +1976,33 @@ const makeEnableToolsHandler = (ctx) => async ({ groups }) => {
 function newToolScope(opts) {
   const asked = opts.only ? new Set(opts.only) : new Set(DEFAULT_TOOL_GROUPS);
   asked.add('core'); // discovery/credits/billing/jobs must exist in EVERY roster or the connection is unusable
-  return { enabledGroups: asked, groupOf: Object.create(null), handleOf: Object.create(null) };
+  // `connectors` is `{connected:Set<provider>, readOk:boolean}` from the transport's own free read, or absent.
+  // ABSENT AND `readOk:false` BEHAVE IDENTICALLY, and that is the fail-open law rather than a convenience:
+  // toolHeldBackByConnectors answers false for both, so an unreadable store, an anonymous discovery handshake and
+  // a transport that has not been taught to read yet all advertise the FULL roster ([[failed-read-is-not-empty]]).
+  return {
+    enabledGroups: asked, groupOf: Object.create(null), handleOf: Object.create(null),
+    conn: opts.connectors || null,
+    widgetHost: !!opts.widgetHost,
+  };
 }
-// The two reasons a registered tool is held back. Applied identically on both paths, for the same reason.
+// THE THREE REASONS A REGISTERED TOOL IS HELD BACK. Applied identically on the build path, the replay path and
+// `enable_tools`, from ONE function, because a gate applied at two of the three is a gate a group flip undoes.
+//
+// (3) IS THE CONNECTOR GATE (2026-08-26). A connector-bound tool for a provider this workspace has not connected
+// can only ever answer `401 {connector:'<p>'}`, so carrying it buys the caller nothing and costs them context on
+// every turn — and a roster many times past the 30–50 tool accuracy cliff is what makes a model pick the wrong
+// tool. The MCP spec (rev 2026-07-28, Tools ▸ Capabilities) permits exactly this and nothing looser: the set
+// "MUST NOT vary per-connection or as a side effect of other requests on the connection. The set MAY vary by the
+// authorization presented on the request … since credentials are per-request input, not connection state."
+// DISABLED, NEVER SKIPPED, like the other two — the handler still exists, so connecting the account and
+// reconnecting reveals it with no code path of its own, and `tools/call` on it still answers its real 401
+// rather than the SDK's "unknown tool".
 function applyToolGates(h, name, group, ctx, opts) {
   if (!h) return;
   if (!ctx.enabledGroups.has(group)) { try { h.disable(); } catch {} }
   if (WITHHELD_FROM_WIDGET_HOSTS.has(name) && opts.widgetHost) { try { h.disable(); } catch {} }
+  if (toolHeldBackByConnectors(name, ctx.conn)) { try { h.disable(); } catch {} }
 }
 
 // Replay the cached canon onto a fresh server. This is the whole hot path for every session after the first.
@@ -2122,7 +2181,13 @@ function buildTools(rawServer, opts = {}, sink = null) {
         const h = t.registerTool(name, defForHost(name, finalDef, opts.widgetHost), handler);
         handleOf[name] = h;
         // DISABLED, NOT SKIPPED — see (1) above. `disable()` is the SDK's own call and removes it from tools/list.
-        if (h && !enabledGroups.has(group)) { try { h.disable(); } catch {} }
+        //
+        // ONE GATE FUNCTION, NOT A SECOND COPY OF THE RULES (2026-08-26). This branch and the widget branch below
+        // used to be spelled out here AND inside applyToolGates, which replayTools calls — two implementations of
+        // the same law, on the two paths a session can take. That is how the build path and the replay path come to
+        // disagree, and it is invisible when they do: the first session in a process takes one, every session after
+        // it takes the other. The third (connector) gate would have had to be written twice for the same reason.
+        applyToolGates(h, name, group, ctx, opts);
         // WITHHELD FROM ONE HOST, for that host's rules rather than ours (2026-08-23).
         // OpenAI's plugin policy permits commerce only in PHYSICAL goods: "selling digital products or services,
         // including subscriptions, digital content, tokens, or credits, is not allowed." buy_credits hands back a
@@ -2141,7 +2206,9 @@ function buildTools(rawServer, opts = {}, sink = null) {
         // rather than only its `enabled:true` branch, because a tool whose declared schema can arm a charge is what a
         // commerce reviewer reads, not the branch it happens to take; turning auto-reload OFF stays available in the
         // app and on every other surface.
-        if (h && WITHHELD_FROM_WIDGET_HOSTS.has(name) && opts.widgetHost) { try { h.disable(); } catch {} }
+        // (The disable itself now lives in applyToolGates above, with the other two gates. This comment stays HERE
+        // because it explains WHICH tools are in WITHHELD_FROM_WIDGET_HOSTS and why, which is the part that has to
+        // be read next to the roster rather than next to the mechanism.)
         return h;
       };
       const v = Reflect.get(t, p);
@@ -3597,6 +3664,12 @@ function buildTools(rawServer, opts = {}, sink = null) {
       poll: z.object({ options: z.array(z.string()), durationMinutes: z.number().optional() }).optional().describe('X — attach a poll: {options:["…","…"], durationMinutes}. 2–4 options of at most 25 characters each; voting runs 5–10080 minutes (7 days), default 1440. X makes a poll MUTUALLY EXCLUSIVE with media, so an item carrying an image or video is refused — schedule the poll as its own X-only post.'),
       replySettings: z.enum(['following', 'mentionedUsers', 'subscribers', 'verified']).optional().describe('X — who may reply. Omit for everyone, which is the right default for a brand post.'),
       madeWithAi: z.boolean().optional().describe('X — X’s AI-media label on this post. Opt-in: X treats it as the poster’s own claim about their media, so it is never set on the user’s behalf.'),
+      // THE THREE X FIELDS `xPost` HAS ACCEPTED SINCE THE DAY THEY LANDED AND NOTHING COULD SCHEDULE (2026-08-26).
+      // Same publisher-can/scheduler-cannot shape as SCHED_ID_FIELDS and the five Threads options one channel over:
+      // reachable when you publish NOW, unreachable when you schedule, and invisible until the parity sweep named it.
+      xQuotePostId: z.string().optional().describe('X — the numeric id of an X post this one QUOTES: the last part of its URL. X renders that post inside yours and it stands alone on your own timeline, which is what makes a quote different from a reply. NAMED xQuotePostId, NOT quotePostId, because `quotePostId` on this same schedule belongs to THREADS — a schedule going to both channels would otherwise be silently ambiguous. Billed at X’s higher LINK rate, because X appends the quoted post’s t.co URL to yours.'),
+      communityId: z.string().optional().describe('X — publish into an X COMMUNITY instead of the main timeline: the number in the community’s own URL (x.com/i/communities/<id>). The connected account must be a MEMBER of it; X answers a non-member and a non-existent id with the same refusal and does not separate them.'),
+      paidPartnership: z.boolean().optional().describe('X — label the post a PAID PARTNERSHIP, the same disclosure Hermoso already ships for TikTok. OPT-IN ONLY: set it when the post is sponsored, gifted or otherwise paid for, and never assume it on the user’s behalf.'),
       collaborators: z.array(z.string()).optional().describe('INSTAGRAM \u2014 a COLLAB post: up to 3 Instagram usernames invited to CO-AUTHOR it, so it appears on their profile too once they accept, with both handles in the header and the engagement shared. Handles only ("hermosoai"); a leading @ is fine. Instagram must be one of the `channels` \u2014 asking for collaborators on a schedule Instagram is not on is REFUSED now rather than discovered when it fires, and the other channels in a mixed schedule simply publish without co-authors. THE INVITE IS SENT WHEN THE POST FIRES, not when you schedule it, and it is PENDING until the other account accepts in their notifications; check with instagram_collaborators afterwards rather than telling the user it is live on both profiles.'),
       trialReel: z.enum(['MANUAL', 'SS_PERFORMANCE']).optional().describe('INSTAGRAM TRIAL REEL \u2014 publish this Reel to NON-FOLLOWERS ONLY at first, so a hook can be tested on a cold audience without spending it on the people who already follow the brand; Instagram shows it to followers only if it graduates. MANUAL = the creator graduates it by hand in the Instagram app; SS_PERFORMANCE = Instagram graduates it automatically if it performs. REELS ONLY and INSTAGRAM ONLY: an image, a carousel, or a Facebook/Threads channel is REFUSED BY NAME rather than quietly published as an ordinary post \u2014 a trial that silently goes to every follower is the exact opposite of what was asked for, so Instagram must be one of the `channels` and the item must carry a video. Omit it for a normal Reel.'),
       // ── WHICH ACCOUNT (server-side SCHED_ID_FIELDS). Every one of these is an answer the publish helper REFUSES
@@ -3687,6 +3760,9 @@ function buildTools(rawServer, opts = {}, sink = null) {
       poll: z.object({ options: z.array(z.string()), durationMinutes: z.number().optional() }).optional().describe('X — replaces the poll; an empty options list removes it.'),
       replySettings: z.enum(['following', 'mentionedUsers', 'subscribers', 'verified']).optional().describe('X — who may reply; "" goes back to everyone.'),
       madeWithAi: z.boolean().optional().describe('X — the AI-media label; false turns it off.'),
+      xQuotePostId: z.string().optional().describe('X — the post this one QUOTES; an empty string removes the quote. Named apart from the Threads `quotePostId` on this same schedule.'),
+      communityId: z.string().optional().describe('X — the community to publish into; an empty string goes back to the main timeline.'),
+      paidPartnership: z.boolean().optional().describe('X — the paid-partnership label; false turns it off.'),
       collaborators: z.array(z.string()).optional().describe('INSTAGRAM \u2014 replaces the WHOLE collab list (up to 3 usernames); an explicit [] removes the co-authors and the post goes out as an ordinary single-author post. Only takes effect if the post has not fired yet \u2014 an invite already sent cannot be withdrawn from here.'),
       trialReel: z.enum(['MANUAL', 'SS_PERFORMANCE', '']).optional().describe('INSTAGRAM \u2014 replaces the trial-reel setting on a queued Reel (MANUAL or SS_PERFORMANCE); an explicit "" turns the trial off and it goes out as an ordinary Reel. Only takes effect while the post is still queued \u2014 a Reel already published cannot be converted into a trial.'),
       boardId: z.string().optional().describe('PINTEREST — move the Pin to a different board (list_pinterest_boards)'),
@@ -4042,14 +4118,18 @@ function buildTools(rawServer, opts = {}, sink = null) {
       paginationToken: z.string().optional().describe('nextToken from a previous call, to page further back. There is no since/until filter at X — this is the only way to walk history.'),
       eventTypes: z.array(z.string()).optional().describe('MessageCreate (default), ParticipantsJoin, ParticipantsLeave. The join/leave events carry no message and are billed like any other, so the default is messages only.'),
     },
-    outputSchema: { account: z.string().optional(), count: z.number().optional(), nextToken: z.string().nullable().optional(), costCredits: z.number().optional(), historyNote: z.string().optional(), events: z.array(z.any()).optional(), conversations: z.array(z.any()).optional() },
+    outputSchema: { account: z.string().optional(), count: z.number().optional(), nextToken: z.string().nullable().optional(), costCredits: z.number().optional(), historyNote: z.string().optional(), events: z.array(z.any()).optional(), conversations: z.array(z.any()).optional(), emptyReason: z.string().optional(), emptyNote: z.string().optional(), xLooked: z.boolean().nullable().optional(), xErrors: z.array(z.any()).optional() },
     annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: true },
   }, wrap(async (a) => {
     const d = await apiGet('/api/x/dms', { maxResults: a.maxResults, conversationId: a.conversationId, participantId: a.participantId, paginationToken: a.paginationToken, eventTypes: (a.eventTypes || []).join(',') });
     const cost = `Cost ${d.costCredits ?? '?'} credits.`;
     // AN EMPTY READ IS REPORTED WITH THE WINDOW, NOT AS SILENCE. "No DMs" and "no DMs in the 30 days X will serve"
     // are different facts, and only one of them is something we actually know.
-    if (!d.count) return ok(`No direct messages for ${d.account || 'that account'} in what X returned. ${d.historyNote || ''} ${cost}`.trim(), d);
+    // AN EMPTY READ NOW SAYS WHICH KIND OF EMPTY IT WAS. X can answer 200 with a top-level errors[] and no data
+    // \u2014 a resource this token may not see, an app whose X permission level excludes Direct Messages \u2014 and for a
+    // day that was reported as an empty inbox on an account with a DM in it. `emptyNote` names the three cases
+    // apart; it is absent when events came back, so a normal answer is unchanged.
+    if (!d.count) return ok(`No direct messages came back for ${d.account || 'that account'}. ${d.emptyNote || ''} ${d.historyNote || ''} ${cost}`.replace(/\s+/g, ' ').trim(), d);
     const rows = (d.conversations || []).map((c) => `${c.needsReply ? '•' : '✓'} ${c.with || 'someone'} (${c.conversationId}) — ${String(c.lastMessage || '').replace(/\s+/g, ' ').slice(0, 160)}${c.needsReply ? '  ← waiting on a reply' : '  (you replied last)'}`);
     return ok(`${d.count} message${d.count === 1 ? '' : 's'} across ${rows.length} conversation${rows.length === 1 ? '' : 's'} for ${d.account}. ${cost}\n${rows.join('\n')}\n\n${d.historyNote || ''}`.trim(), d);
   }));
@@ -5064,25 +5144,64 @@ function buildTools(rawServer, opts = {}, sink = null) {
       to: z.string().optional().describe('the recipient\u2019s Bluesky handle, e.g. alice.bsky.social. Ignored when convoId is given.'),
       text: z.string().describe('the message, up to 1000 characters'),
       replyToMessageId: z.string().optional().describe('reply to a specific message in the conversation'),
+      dryRun: z.boolean().optional().describe('CHECK FIRST, SEND NOTHING. Asks Bluesky whether a DM to `to` would be delivered at all and returns canChat plus the reason when it would not \u2014 that account has DMs off, only accepts them from people it follows, has blocked this one, is suspended, or does not exist. Free, and the message is NOT sent. Use it before writing a long DM to someone who has never been messaged, so a refusal costs nothing instead of arriving after the words were written. `text` is still validated for length so a dry run cannot pass on a message the real send would refuse.'),
     },
-    outputSchema: { convoId: z.string().optional(), messageId: z.string().optional(), sentAt: z.string().optional(), text: z.string().optional(), to: z.string().optional(), delivered: z.boolean().optional() },
+    outputSchema: { convoId: z.string().optional(), messageId: z.string().optional(), sentAt: z.string().optional(), text: z.string().optional(), to: z.string().optional(), delivered: z.boolean().optional(), dryRun: z.boolean().optional(), sent: z.boolean().optional(), canChat: z.boolean().optional(), reason: z.string().optional(), note: z.string().optional() },
     annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: true },
   }, wrap(async (a) => {
     const d = await apiPost('/api/bluesky/dm', a);
+    // A DRY RUN MUST NEVER RENDER AS A SEND. The send sentence below reads "Sent the DM ..." and would be a
+    // plain falsehood about a call that deliberately delivered nothing.
+    if (d.dryRun) return ok(d.note || `Pre-flight only \u2014 nothing was sent. canChat: ${d.canChat === true}.`, d);
     return ok(`${d.delivered ? 'Sent' : 'Bluesky accepted but returned no message id for'} the DM${d.to ? ` to ${d.to}` : ''} \u2014 conversation ${d.convoId}${d.sentAt ? `, recorded at ${d.sentAt}` : ''}.\n\u201c${d.text}\u201d`, d);
   }));
   server.registerTool('mark_bluesky_convo_read', {
-    title: 'Mark a Bluesky conversation as read',
-    description: 'Clear the unread count on one Bluesky DM conversation, optionally only up to a specific message. Useful after triaging an inbox so the next list_bluesky_convos does not surface the same thread again. Reports the unread count Bluesky reads back, not the one requested.',
+    title: 'Mark Bluesky conversations as read',
+    description: 'Clear the unread count on Bluesky DMs \u2014 ONE conversation, or the WHOLE ACCOUNT when convoId is omitted (Bluesky\u2019s own mark-all, narrowable with status to just the message requests or just the accepted threads). Useful after triaging an inbox so the next list_bluesky_convos does not surface the same threads again. Reports the unread count \u2014 or the number of conversations \u2014 Bluesky reads back, not the one requested. Free.',
     inputSchema: {
-      convoId: z.string().describe('from list_bluesky_convos'),
+      convoId: z.string().optional().describe('from list_bluesky_convos. OMIT to mark EVERY conversation on the account read.'),
       messageId: z.string().optional().describe('mark read only up to this message; omit to clear the whole conversation'),
+      status: z.enum(['request', 'accepted']).optional().describe('mark-all only: narrow it to just the message requests, or just the accepted conversations. Omit to clear both. An unknown value is refused rather than dropped \u2014 a dropped one would clear everything when you asked to clear only the requests.'),
     },
-    outputSchema: { convoId: z.string().optional(), unread: z.number().optional(), with: z.string().optional() },
+    outputSchema: { convoId: z.string().optional(), unread: z.number().optional(), with: z.string().optional(), all: z.boolean().optional(), status: z.string().optional(), updatedCount: z.number().nullable().optional(), note: z.string().optional() },
     annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: true },
   }, wrap(async (a) => {
     const d = await apiPost('/api/bluesky/mark-read', a);
-    return ok(`Conversation with ${d.with || d.convoId} now reads ${d.unread} unread.`, d);
+    return ok(d.all ? (d.note || 'Marked read.') : `Conversation with ${d.with || d.convoId} now reads ${d.unread} unread.`, d);
+  }));
+  // \u2500\u2500 THE CONVERSATION ACTIONS (2026-08-26) \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500
+  // We LISTED a conversation as a message REQUEST and offered no way to accept it, and reported it as MUTED with
+  // no way to mute or unmute it \u2014 a state drawn on the screen with no handle behind it. Seven lexicons behind
+  // ONE tool rather than seven tools: this roster is past 700 and 30-50 is where instruction-following starts to
+  // degrade, and the repo already spells this pattern manage_meta_post / manage_linkedin_post.
+  server.registerTool('manage_bluesky_convo', {
+    title: 'Accept, mute, lock, leave or prune a Bluesky DM conversation',
+    description: 'Act on one Bluesky DM conversation. ACCEPT a message request \u2014 Bluesky holds DMs from people the account does not follow in a separate requests folder, and until one is accepted it stays there. MUTE / UNMUTE it. LOCK / UNLOCK it (no new messages). LEAVE it. Or DELETE one message from THIS account\u2019s view. TWO THINGS TO SAY OUT LOUD BEFORE USING THEM: deleting is FOR SELF ONLY \u2014 the other person still sees the message, because Bluesky offers no delete-for-everyone in chat \u2014 and leaving a conversation cannot be undone from here. Accepting a request that was already accepted is reported as such rather than as a change, because Bluesky says so by returning no revision. Free, and it needs the same PRIVILEGED app password as every other Bluesky DM tool. Get a convoId from list_bluesky_convos.',
+    inputSchema: {
+      action: z.enum(['accept', 'mute', 'unmute', 'lock', 'unlock', 'leave', 'deleteMessage']).describe('what to do to the conversation'),
+      convoId: z.string().describe('from list_bluesky_convos'),
+      messageId: z.string().optional().describe('required for deleteMessage \u2014 from read_bluesky_dm'),
+    },
+    outputSchema: { action: z.string().optional(), convoId: z.string().optional(), messageId: z.string().optional(), accepted: z.boolean().optional(), alreadyAccepted: z.boolean().optional(), left: z.boolean().optional(), deletedForSelf: z.boolean().optional(), muted: z.boolean().optional(), unread: z.number().optional(), with: z.string().optional(), status: z.string().optional(), note: z.string().optional() },
+    annotations: { readOnlyHint: false, destructiveHint: true, openWorldHint: true },
+  }, wrap(async (a) => {
+    const d = await apiPost('/api/bluesky/convo-action', a);
+    return ok(d.note || `${a.action} done on ${a.convoId}.`, d);
+  }));
+  server.registerTool('react_to_bluesky_dm', {
+    title: 'React to a Bluesky direct message',
+    description: 'Add or remove an emoji reaction on one message in a Bluesky DM \u2014 the light acknowledgement that does not need a written reply, and the thing to reach for when someone says \u201cthanks\u201d and a paragraph back would be worse than a thumbs-up. A REACTION IS EXACTLY ONE EMOJI: that is Bluesky\u2019s own rule, so a word or a phrase is refused here rather than by the service (where it comes back as an opaque ReactionInvalidValue). Reports the reactions Bluesky reads the message back carrying, not the one requested. Free.',
+    inputSchema: {
+      convoId: z.string().describe('from list_bluesky_convos'),
+      messageId: z.string().describe('from read_bluesky_dm'),
+      value: z.string().describe('exactly one emoji, e.g. \uD83D\uDC4D'),
+      remove: z.boolean().optional().describe('true to take the reaction off instead of putting it on'),
+    },
+    outputSchema: { convoId: z.string().optional(), messageId: z.string().optional(), value: z.string().optional(), removed: z.boolean().optional(), reactions: z.array(z.string()).optional(), text: z.string().optional(), note: z.string().optional() },
+    annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: true },
+  }, wrap(async (a) => {
+    const d = await apiPost('/api/bluesky/react', a);
+    return ok(d.note || `Reaction ${a.value} ${a.remove ? 'removed' : 'added'}.`, d);
   }));
   server.registerTool('tiktok_creator_info', {
     title: 'Read the connected TikTok creator’s posting options',

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "hermoso",
-  "version": "0.1.160",
+  "version": "0.1.161",
   "mcpName": "io.github.hermoso-ai/hermoso",
-  "description": "AI ad studio and marketing MCP server with 716 tools. Research the ads already running in any market, generate finished image, video and UGC avatar ads, publish and schedule them to your own channels, build and manage the ad campaigns behind them, and read what they achieved. AD PLATFORMS: Meta, Google Ads, TikTok Ads, LinkedIn Ads, Reddit Ads, X Ads, Pinterest Ads, Snapchat Ads, Microsoft Advertising, Apple Search Ads and ChatGPT Ads, plus product feeds in Google Merchant Center. PUBLISHING AND SCHEDULING: Facebook, Instagram, Threads, TikTok, YouTube, X, LinkedIn, Pinterest, Bluesky and Telegram. AD RESEARCH: the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Threads and Reddit. ANALYTICS: Google Analytics 4, Google Search Console and every connected platform's own post and campaign insights. Also brand onboarding, 50+ image and video generation models, ad scoring, competitor teardowns, Google Drive and OneDrive, a CLI and installable Claude skills.",
+  "description": "AI ad studio and marketing MCP server with 718 tools. Research the ads already running in any market, generate finished image, video and UGC avatar ads, publish and schedule them to your own channels, build and manage the ad campaigns behind them, and read what they achieved. AD PLATFORMS: Meta, Google Ads, TikTok Ads, LinkedIn Ads, Reddit Ads, X Ads, Pinterest Ads, Snapchat Ads, Microsoft Advertising, Apple Search Ads and ChatGPT Ads, plus product feeds in Google Merchant Center. PUBLISHING AND SCHEDULING: Facebook, Instagram, Threads, TikTok, YouTube, X, LinkedIn, Pinterest, Bluesky and Telegram. AD RESEARCH: the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Threads and Reddit. ANALYTICS: Google Analytics 4, Google Search Console and every connected platform's own post and campaign insights. Also brand onboarding, 50+ image and video generation models, ad scoring, competitor teardowns, Google Drive and OneDrive, a CLI and installable Claude skills.",
   "type": "module",
   "bin": {
     "hermoso": "bin/hermoso.mjs"