@omnisocials/mcp-server 1.28.0 → 1.31.0

package/README.md

@@ -109,13 +109,13 @@ OmniSocials accepts the following channel IDs in `create_post`, `create_and_publ
 | `tiktok` | TikTok | Posts and reels |
 | `pinterest` | Pinterest | Pins (requires `board_id`) |
 | `x` | X (Twitter) | Posts, chained threads via `x.thread_parts` |
-| `threads` | Threads | Posts, chained threads via `threads.thread_parts` |
+| `threads` | Threads | Posts, chained threads via `threads.thread_parts`, location tagging via `threads.location_id` (rolling out) |
 | `bluesky` | Bluesky | Posts, chained threads via `bluesky.thread_parts` |
 | `mastodon` | Mastodon | Posts, chained threads via `mastodon.thread_parts` |
 
 ## Available Tools
 
-### Posts (7 tools)
+### Posts (12 tools)
 
 | Tool | Description |
 |------|-------------|
@@ -126,7 +126,11 @@ OmniSocials accepts the following channel IDs in `create_post`, `create_and_publ
 | `update_post` | Update a draft or scheduled post |
 | `delete_post` | Delete a post |
 | `publish_post` | Publish a draft or scheduled post now |
-| `search_locations` | Find an Instagram location to tag (returns place IDs for `location_id`) |
+| `retry_post` | Retry the failed platforms of a failed or partially failed post |
+| `approve_post` | Approve the current step of a post's approval workflow (the connected user must be a listed approver for that step) |
+| `reject_post` | Reject a post's approval workflow, stopping it immediately |
+| `search_locations` | Find an Instagram or Threads location to tag (Instagram place IDs for `location_id`, Threads location ids for `threads.location_id`; Threads also searches by latitude/longitude) |
+| `search_instagram_audio` | Search Instagram's licensed music catalog for a track to attach to a Reel |
 
 ### Media & folders (6 tools)
 
@@ -184,14 +188,15 @@ Apply a set when creating a post: `create_post` / `create_and_publish_post` acce
 | `delete_webhook` | Delete a webhook |
 | `rotate_webhook_secret` | Rotate a webhook's signing secret |
 
-### Social Inbox (4 tools)
+### Social Inbox (5 tools)
 
 | Tool | Description |
 |------|-------------|
-| `list_inbox_conversations` | List conversations — Instagram/Facebook DMs, comments, mentions, LinkedIn company-page comments/mentions, TikTok video comments, and X DMs (opt-in); filter by platform, type, or unread |
+| `list_inbox_conversations` | List conversations — Instagram/Facebook DMs, comments, mentions, LinkedIn company-page comments/mentions, TikTok video comments, YouTube video comments, X DMs (opt-in), and Threads replies on your posts plus mentions (rolling out); filter by platform, type, or unread |
 | `get_inbox_conversation` | Get a conversation's full message history |
 | `mark_inbox_read` | Mark all incoming messages in a conversation as read |
 | `reply_to_inbox` | Reply to a DM, comment, or mention (existing conversations only) |
+| `hide_inbox_reply` | Hide or unhide a reply on one of your Threads posts (Threads only for now) |
 
 Requires an API key with the opt-in `inbox:read` / `inbox:write` scopes — enable "Social Inbox access" when you create the key.
 
@@ -218,6 +223,56 @@ Full API docs: [docs.omnisocials.com](https://docs.omnisocials.com)
 
 ## Changelog
 
+### 1.31.0 (2026-08-30)
+
+- **Added: write access to approvals.** New tools `approve_post` and `reject_post`. Both act on a post's approval workflow (`approval_status: "pending"`, post status `in_approval`) and only succeed if the connected user is a listed approver for the workflow's CURRENT step — steps approve in order. Approving the final step finalizes the post (`scheduled` or `posting`); rejecting stops the whole workflow immediately (`rejected`), with an optional `comment` shown to the requester. Previously `approval_status` was read-only via `get_post` / `list_posts`. Same on the companion server (`mcp.omnisocials.com`).
+
+### 1.30.0 (2026-08-30)
+
+- **Added: media on inbox messages.** Instagram and Facebook DM messages (images, videos, voice messages, and story mentions) now carry an `attachment` object (`url`, `type`) in `get_inbox_conversation`. Incoming attachment URLs are re-hosted on our own CDN so they stay valid indefinitely. `reply_to_inbox` gains optional `attachment_url` / `attachment_type` to send media on a Facebook or Instagram DM reply; `text` is optional when an attachment is set. Same on the companion server (`mcp.omnisocials.com`).
+
+### 1.29.0 (2026-08-29)
+
+- **Added: YouTube comments in the Social Inbox.** `list_inbox_conversations` accepts `platform: "youtube"` and returns YouTube video comment threads (comments only; YouTube has no DMs). `reply_to_inbox` can reply to YouTube comments. YouTube has no comment webhooks, so each channel is checked for new comments once per day; a new comment can take up to a day to appear. Same on the companion server (`mcp.omnisocials.com`).
+
+### 1.28.0 (2026-08-23)
+
+- **Added: Threads (Meta) chained threads.** `create_post`, `create_and_publish_post`, and `update_post` accept a new `threads` option object with `thread_parts`, the same shape as the existing `x`, `bluesky`, and `mastodon` thread support: an array of 2 to 25 `{ text, media_ids?, media_urls? }` parts, 500 characters per part, up to 10 media per part (images and videos can be mixed in one carousel). Parts after the first publish as replies to the previous part. When `thread_parts` is set, the Threads caption is taken from part 1. On `update_post`, `threads.thread_parts: null` reverts the post to a single Threads post. `get_post` renders a `### Threads Thread` section, `list_posts` previews a Threads chain the same way it previews X/Bluesky/Mastodon threads, and the analytics `thread_parts` counter covers Threads. Same on the companion server (`mcp.omnisocials.com`).
+
+### 1.27.0 (2026-08-22)
+
+- **Added: every metric the platforms report.** `get_post_analytics` and `get_posts_analytics` now render the full per-platform metric set with labels: link clicks, profile visits, follows from the post, pin and outbound clicks, video views, engaged views, average and total watch time, watched percentage, completion rate, skip rate, replays, subscribers gained and lost, duration, plus breakdown rows for reactions by type, clicks by type, traffic sources (YouTube), where the video was seen and viewer types (TikTok), Instagram story navigation and completion, Google Business impressions by surface. Items a platform cannot measure carry `metrics_unavailable` and a note instead of zeros.
+- **Added: account day values and audience data.** `get_account_analytics` details now list views, reach, engagement, profile views, link clicks, new and lost followers, accounts engaged, video views, minutes watched, Pinterest monthly views, Google Business rating, reviews, calls, direction requests, website clicks and bookings, and the row's `period`. The raw response also carries `demographics` and `online_followers` when the platform provides them. LinkedIn profile rows keep the lifetime total under `impressions_lifetime`; `impressions_period` is gone.
+- **Changed: `get_best_times` blends in when the audience is online.** New `basis` values `own_data_and_audience` and `audience` (Instagram, TikTok Business), and the response carries `audience_online` (hour to followers online). Tool description and footer text updated. Same on the companion server (`mcp.omnisocials.com`).
+- **Fixed:** a `reactions` breakdown object no longer turns the likes total into `NaN` in `get_posts_analytics`.
+
+### 1.26.0 (2026-08-22)
+
+- **Added: TikTok first comments.** The `tiktok` option object on `create_post`, `create_and_publish_post`, and `update_post` accepts `first_comment` (max **150 characters**, TikTok's own comment limit). It is posted through the TikTok Business API right after the video publishes, so the workspace's TikTok channel must have comments enabled (the "Enable comments" authorization on the channel card); without it `first_comment_result.status` is `failed` with an explanatory error. The video must be public with comments allowed. TikTok sometimes returns the final video id a few minutes after publish — then `first_comment_result.pending` is `true` and the comment posts automatically once the id resolves. `get_post` renders TikTok in the `### First comment` section. Same on the companion server (`mcp.omnisocials.com`).
+- **Added: TikTok watch-depth metrics.** `get_post_analytics`, `get_posts_analytics`, and `get_recent_platform_posts` now include `average_time_watched` (seconds), `full_video_watched_rate`, `total_time_watched` (seconds), `favorites`, and `reach` for TikTok videos when the workspace enabled TikTok comments. Workspaces that enabled comments before this release must click "Unlock watch-time analytics" on the TikTok channel card once (one extra TikTok consent for the `video.insights` scope). Tool descriptions updated accordingly.
+
+### 1.25.0 (2026-08-21)
+
+- **Added: multi-slide stories.** `create_post`, `create_and_publish_post`, and `update_post` now treat every media item on a `type: "story"` post as one slide (1 to 10). Instagram and Facebook have no multi-slide story container, so each slide publishes as its own story, in the order given; more than 10 returns 400. The tool descriptions tell the model to ask which media and in what order, and that story videos are capped at 60 seconds per slide. `get_post` renders a `### Story Slides` section with every slide's own URL (the `published_urls` block keeps the first slide), and `get_post_analytics` shows a per-slide table under the platform totals for multi-slide stories. Same on the companion server (`mcp.omnisocials.com`).
+
+### 1.24.0 (2026-08-20)
+
+- **Added: LinkedIn multi-image style (`carousel_as_images`).** The `linkedin` and `linkedin_page` option objects on `create_post`, `create_and_publish_post`, and `update_post` accept a new `carousel_as_images` boolean. By default a LinkedIn post with 2+ images publishes as LinkedIn's swipeable PDF document carousel; set `carousel_as_images: true` to publish the images as a plain multi-image gallery instead. Independent per channel (profile vs company page). Ignored for 0-1 images, videos, and polls. On `update_post` the flag merges: `true` sets it, `false`/`null` reverts to the document carousel, omitted keeps the current value. `get_post` echoes the flag inside each channel's options and renders a note when a post opts out of the document carousel. Same on the companion server (`mcp.omnisocials.com`).
+
+### 1.23.0 (2026-08-20)
+
+- **Changed: X thread parts now teach the weighted character count.** The `thread_parts[].text` description explains that X's 280 limit is a weighted count: every link counts as 23 characters, and every emoji or non-Latin symbol (rocket, ellipsis, CJK) counts as 2, so text that looks under 280 can still be over. Models trimming generated copy are told to leave headroom instead of cutting to exactly 280 raw characters. Backed by the server-side weighting fix (verified against the official twitter-text library), which also maps X's vague 403 to a message naming the character-limit cause. Same on the companion server (`mcp.omnisocials.com`).
+- **Changed: per-platform mixed-media rules in `create_post` / `create_and_publish_post` / `update_post` descriptions.** Instagram and Threads carousels CAN mix images and videos in one carousel (a May 2025 blanket block was removed); Facebook, LinkedIn Profile, LinkedIn Page, X, Bluesky, and Mastodon cannot mix and now reject mixed batches at create time with a message naming the platform (previously the API published the video and silently dropped the images). Pinterest note clarified: a video splits off into its own video pin. Same on the companion server (`mcp.omnisocials.com`).
+- **Changed: npm keywords expanded** (scheduling plus every platform name) so MCP registries and npm search can find the server.
+
+### 1.22.0 (2026-08-13)
+
+- **Added: TikTok comments in the Social Inbox.** `list_inbox_conversations` accepts `platform: "tiktok"` and TikTok video comments now appear alongside the other platforms (comments only — TikTok has no DM or mention conversations here). `reply_to_inbox` replies to TikTok comments: text-only, capped at **150 characters** (the platform's own limit; longer text returns a validation error), and the posted reply can take a few minutes to become publicly visible while TikTok's spam review clears it. Requires the workspace's TikTok channel to have comments enabled (the "Enable comments" authorization on the TikTok channel card). A 401 `reauth_required` on reply means that authorization expired — re-enable comments on the channel. Same tools on the companion server (`mcp.omnisocials.com`).
+
+### 1.21.0 (2026-08-12)
+
+- **Added: LinkedIn polls.** `create_post`, `create_and_publish_post`, and `update_post` accept a new `linkedin_poll` parameter, keyed by channel: `{ linkedin?: { question (max 140 chars), options (2-4 entries, max 30 chars each), duration }, linkedin_page?: {...} }` where `duration` is one of `ONE_DAY`/`THREE_DAYS`/`SEVEN_DAYS`/`FOURTEEN_DAYS`. `linkedin` (personal profile) and `linkedin_page` (company page) each carry an **independent** poll — set both keys to post a different poll to each. A poll is mutually exclusive with media and a link share on that channel's post — a poll silently takes priority over both at publish time, so don't combine them. On `update_post`, the object replaces wholesale (send the full state for both channels); set a channel's key to `null` to clear that channel's poll and revert it to a normal post. `get_post` now renders a `### LinkedIn Profile Poll` and/or `### LinkedIn Page Poll` section (question, options, duration) when either channel is one. Same on the companion server (`mcp.omnisocials.com`).
+
 ### 1.20.0 (2026-08-04)
 
 - **Engagement rate now matches the dashboard:** `get_post_analytics` / `get_posts_analytics` previously summed likes + comments + shares only, dropping LinkedIn link clicks and X quotes/bookmarks from engagement. Both tools now use the same normalization as the dashboard and `get_analytics_overview`; rates are suppressed below 10 impressions and capped at 100%.

package/build/client.d.ts

@@ -1,4 +1,4 @@
-import type { Account, AnalyticsOverview, AccountAnalyticsEntry, ApiPost, ApiResponse, AudioSearchResult, BestTimesResult, HashtagSet, LocationSearchResult, MediaCheckResult, MediaCompatibility, MediaFolder, MediaItem, PdfUploadResult, PostAnalytics, PublishPostResult, RecentPlatformPost, RetryPostResult, InboxConversation, InboxMessage, Webhook } from "./types.js";
+import type { Account, AnalyticsOverview, AccountAnalyticsEntry, ApiPost, ApiResponse, AudioSearchResult, BestTimesResult, HashtagSet, LocationSearchResult, MediaCheckResult, MediaCompatibility, MediaFolder, MediaItem, PdfUploadResult, PostAnalytics, PublishPostResult, RecentPlatformPost, RetryPostResult, ApprovePostResult, RejectPostResult, InboxConversation, InboxMessage, Webhook } from "./types.js";
 export declare function fetchImageAsBase64(url: string): Promise<{
     data: string;
     mimeType: string;
@@ -117,6 +117,11 @@ export interface ThreadsPostOptions {
     /** Provide 2 to 25 parts to publish as a thread. Omit for a single post.
      * When set, the Threads caption is taken from part 1. */
     thread_parts?: ThreadsThreadPartInput[];
+    /** Threads location id from search_locations with platform "threads"
+     * (NOT a Facebook Place ID). Tagged on the post; on a multi-post thread
+     * the tag goes on the first post. Needs the threads_location_tagging
+     * permission on the Threads connection. */
+    location_id?: string | null;
 }
 /**
  * Update-side variant: `thread_parts: null` clears the thread (revert to a
@@ -124,6 +129,9 @@ export interface ThreadsPostOptions {
  */
 export interface ThreadsPostOptionsUpdate {
     thread_parts?: ThreadsThreadPartInput[] | null;
+    /** New Threads location id, or null to remove the tag. Omit to leave the
+     * existing tag untouched. */
+    location_id?: string | null;
 }
 /** Non-sponsored LinkedIn poll: question + 2-4 options + duration. */
 export interface LinkedInPollFields {
@@ -236,7 +244,12 @@ export declare class OmniSocialsClient {
     deletePost(id: string): Promise<ApiResponse<unknown>>;
     publishPost(id: string): Promise<ApiResponse<PublishPostResult>>;
     retryPost(id: string): Promise<ApiResponse<RetryPostResult>>;
-    searchLocations(query: string): Promise<LocationSearchResult>;
+    approvePost(id: string): Promise<ApiResponse<ApprovePostResult>>;
+    rejectPost(id: string, comment?: string): Promise<ApiResponse<RejectPostResult>>;
+    searchLocations(query?: string, platform?: "instagram" | "threads", coords?: {
+        latitude?: number;
+        longitude?: number;
+    }): Promise<LocationSearchResult>;
     validateLocation(id: string): Promise<ApiResponse<unknown>>;
     searchInstagramAudio(query?: string, type?: "music" | "original_sound"): Promise<AudioSearchResult>;
     listMedia(params?: {
@@ -358,4 +371,5 @@ export declare class OmniSocialsClient {
         attachment_url?: string;
         attachment_type?: string;
     }): Promise<ApiResponse<InboxMessage>>;
+    hideInboxMessage(messageId: string, hide?: boolean): Promise<ApiResponse<InboxMessage>>;
 }

package/build/client.js

@@ -272,13 +272,34 @@ export class OmniSocialsClient {
     async retryPost(id) {
         return this.request("POST", `/posts/${id}/retry`);
     }
-    // Locations (Instagram place tagging). NOT the standard envelope — see
-    // LocationSearchResult (degraded-path `error` is a plain string).
-    async searchLocations(query) {
-        return this.request("GET", "/locations/search", undefined, {
-            q: query,
+    // Approves the CURRENT step of the post's approval workflow. The API key's
+    // owner must be a listed approver for that step (steps approve in order) —
+    // otherwise the request returns a `forbidden` error.
+    async approvePost(id) {
+        return this.request("POST", `/posts/${id}/approve`);
+    }
+    // Rejects the post's approval workflow, stopping it immediately (not just
+    // the current step). Same approver requirement as approvePost.
+    async rejectPost(id, comment) {
+        return this.request("POST", `/posts/${id}/reject`, {
+            ...(comment ? { comment } : {}),
         });
     }
+    // Locations (Instagram or Threads place tagging). NOT the standard
+    // envelope; see LocationSearchResult: Instagram's degraded-path `error` is
+    // a plain string next to `data`; Threads answers with `locations` and a
+    // { code, message } `error` object when the search could not run.
+    // Threads accepts either a text query or a latitude/longitude pair.
+    async searchLocations(query, platform = "instagram", coords) {
+        const params = { platform };
+        if (query)
+            params.q = query;
+        if (coords?.latitude !== undefined)
+            params.latitude = String(coords.latitude);
+        if (coords?.longitude !== undefined)
+            params.longitude = String(coords.longitude);
+        return this.request("GET", "/locations/search", undefined, params);
+    }
     async validateLocation(id) {
         return this.request("GET", "/locations/validate", undefined, { id });
     }
@@ -413,4 +434,9 @@ export class OmniSocialsClient {
     async replyToInboxConversation(conversationId, data) {
         return this.request("POST", `/inbox/conversations/${encodeURIComponent(conversationId)}/reply`, data);
     }
+    // Hide/unhide a reply on one of the workspace's Threads posts (Threads
+    // only for now). `hide: false` unhides. Needs the inbox:write scope.
+    async hideInboxMessage(messageId, hide = true) {
+        return this.request("POST", `/inbox/messages/${encodeURIComponent(messageId)}/hide`, { hide });
+    }
 }

package/build/index.js

@@ -29,7 +29,7 @@ const sessionState = { activeIndex: 0 };
 const getActiveClient = () => workspaceClients[sessionState.activeIndex].client;
 const server = new McpServer({
     name: "OmniSocials",
-    version: "1.28.0",
+    version: "1.29.0",
 });
 // Register all tools - pass getter function so tools always use the active workspace's client
 registerPostTools(server, getActiveClient);

package/build/tools/inbox.js

@@ -5,12 +5,14 @@ const PLATFORM_EMOJI = {
     facebook: "📘",
     linkedin: "💼",
     tiktok: "🎵",
+    youtube: "▶️",
     x: "🐦",
+    threads: "🧵",
 };
 export function registerInboxTools(server, getClient) {
-    server.tool("list_inbox_conversations", "List social inbox conversations (Instagram/Facebook DMs, comments, mentions, LinkedIn company-page comments/mentions, TikTok video comments, and X DMs where the workspace has opted into X DMs), newest activity first. Cursor-paginated: pass the returned cursor to get the next page.", {
+    server.tool("list_inbox_conversations", "List social inbox conversations (Instagram/Facebook DMs, comments, mentions, LinkedIn company-page comments/mentions, TikTok video comments, YouTube video comments, X DMs where the workspace has opted into X DMs, and Threads replies on the workspace's posts plus mentions), newest activity first. Threads conversations are comment (replies on the workspace's posts) and mention only, need a Threads connection with the reply-reading permission, and are currently rolling out (disabled on production until Meta approves the permission). Cursor-paginated: pass the returned cursor to get the next page.", {
         platform: z
-            .enum(["instagram", "facebook", "linkedin", "tiktok", "x"])
+            .enum(["instagram", "facebook", "linkedin", "tiktok", "x", "youtube", "threads"])
             .optional()
             .describe("Filter to one platform"),
         type: z
@@ -108,7 +110,17 @@ export function registerInboxTools(server, getClient) {
             const who = m.direction === "outgoing"
                 ? "→ You"
                 : `← ${m.sender?.name || m.sender?.username || "Them"}`;
-            md += `**${who}** _(${formatDateTime(m.timestamp)})_\n${m.text || ""}\n\n`;
+            // The message id is what hide_inbox_reply takes, so always render it.
+            const flags = [`id ${m.id}`];
+            if (m.hidden === true)
+                flags.push("hidden on Threads");
+            md += `**${who}** _(${formatDateTime(m.timestamp)})_ \`${flags.join(" · ")}\`\n${m.text || ""}\n`;
+            if (m.attachment?.url) {
+                md += `📎 [${m.attachment.type}] ${m.attachment.url}\n`;
+            }
+            if (m.permalink)
+                md += `${m.permalink}\n`;
+            md += `\n`;
         }
         if (result.pagination?.next_cursor) {
             md += `_More messages — call again with cursor "${result.pagination.next_cursor}"._`;
@@ -138,14 +150,25 @@ export function registerInboxTools(server, getClient) {
             ],
         };
     });
-    server.tool("reply_to_inbox", "Reply to an existing inbox conversation (DM, comment, or mention) on Instagram, Facebook, LinkedIn, TikTok, or X. You can only reply to conversations that already exist. Meta direct-message replies must be within the platform's 24-hour messaging window. TikTok replies are comments only, text-only, and capped at 150 characters; they can take a few minutes to appear on TikTok while they pass spam review. X replies are DM-only and use 2 prepaid credits per send (X's API fee passed through at cost) — a 402 insufficient_credits error means the organisation needs to top up at https://app.omnisocials.com/credits; relay that link to the user rather than retrying. Each workspace can send up to 1,000 replies per day.", {
+    server.tool("reply_to_inbox", "Reply to an existing inbox conversation (DM, comment, or mention) on Instagram, Facebook, LinkedIn, TikTok, X, YouTube, or Threads (Threads replies are on the workspace's posts and mentions; a 401 reauth_required means the Threads connection must be reconnected to grant the reply permission; the reply publishes as a native Threads reply). You can only reply to conversations that already exist. Meta direct-message replies must be within the platform's 24-hour messaging window. TikTok replies are comments only, text-only, and capped at 150 characters; they can take a few minutes to appear on TikTok while they pass spam review. YouTube replies are comments only. X replies are DM-only and use 2 prepaid credits per send (X's API fee passed through at cost) — a 402 insufficient_credits error means the organisation needs to top up at https://app.omnisocials.com/credits; relay that link to the user rather than retrying. Each workspace can send up to 1,000 replies per day. attachment_url/attachment_type let you send media on a Facebook or Instagram DM (text is optional when an attachment is set — an attachment-only DM is allowed); other platforms are text-only.", {
         conversation_id: z.string().describe("The conversation ID to reply to"),
         text: z
             .string()
-            .describe("The reply text (max 2000 characters; TikTok comments max 150)"),
-    }, { title: "Reply to Inbox Message", readOnlyHint: false, destructiveHint: false, openWorldHint: true }, async ({ conversation_id, text }) => {
+            .optional()
+            .describe("The reply text (max 2000 characters; TikTok comments max 150). Optional when attachment_url is set."),
+        attachment_url: z
+            .string()
+            .optional()
+            .describe("Media URL to send (Facebook and Instagram DMs only)"),
+        attachment_type: z
+            .enum(["image", "video", "audio", "file"])
+            .optional()
+            .describe("Required if attachment_url is set"),
+    }, { title: "Reply to Inbox Message", readOnlyHint: false, destructiveHint: false, openWorldHint: true }, async ({ conversation_id, text, attachment_url, attachment_type }) => {
         const result = await getClient().replyToInboxConversation(conversation_id, {
-            text,
+            text: text ?? "",
+            attachment_url,
+            attachment_type,
         });
         if (result.error) {
             return {
@@ -167,4 +190,36 @@ export function registerInboxTools(server, getClient) {
             ],
         };
     });
+    server.tool("hide_inbox_reply", "Hide (or unhide) a reply someone left on one of the workspace's Threads posts, as the post owner. Threads only for now, and only incoming top-level replies can be hidden (Threads does not allow hiding nested replies). The message keeps its place in the conversation; its `hidden` flag flips. Use the message id shown by get_inbox_conversation. Errors: 400 unsupported_platform (not an incoming Threads reply), 400 not_hideable (nested reply, or Threads refused), 401 reauth_required (the Threads connection lacks the reply permission; reconnect Threads under Settings → Organisation → Workspaces). Threads inbox features are currently rolling out (disabled on production until Meta approves the permission). Requires the inbox:write scope.", {
+        message_id: z
+            .string()
+            .describe("The inbox message id of the reply (from get_inbox_conversation)"),
+        hide: z
+            .boolean()
+            .optional()
+            .describe("true (default) hides the reply; false unhides it"),
+    }, async ({ message_id, hide }) => {
+        const result = await getClient().hideInboxMessage(message_id, hide ?? true);
+        if (result.error) {
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: `Error (${result.error.code}): ${result.error.message}`,
+                    },
+                ],
+            };
+        }
+        const hidden = result.data?.hidden === true;
+        return {
+            content: [
+                {
+                    type: "text",
+                    text: hidden
+                        ? `Reply \`${message_id}\` is now hidden on Threads.`
+                        : `Reply \`${message_id}\` is now visible on Threads again.`,
+                },
+            ],
+        };
+    });
 }

package/build/tools/posts.js

@@ -370,6 +370,12 @@ export function registerPostTools(server, getClient) {
         // Instagram extras, echoed top-level by the API to mirror create_post.
         if (p.location_id)
             md += `| **IG location** | \`${p.location_id}\` |\n`;
+        // Threads location tag read-back (threads.location on the Post).
+        const threadsLoc = p.threads?.location;
+        if (threadsLoc?.id) {
+            const locBits = [threadsLoc.name, threadsLoc.city, threadsLoc.country].filter(Boolean).join(", ");
+            md += `| **Threads location** | ${locBits ? `${locBits} ` : ""}\`${threadsLoc.id}\` |\n`;
+        }
         if (Array.isArray(p.collaborators) && p.collaborators.length) {
             md += `| **IG collaborators** | ${p.collaborators.map((c) => `@${c}`).join(", ")} |\n`;
         }
@@ -694,8 +700,9 @@ Do NOT call this tool without media when creating stories, reels, Instagram post
             thread_parts: z.array(MASTODON_THREAD_PART).min(2).max(25).optional().describe("Publish as a chained Mastodon thread instead of a single status. Provide 2–25 parts; each is posted in order as a native reply to the previous status (in_reply_to_id). Attach media to any part via media_ids (from upload_media) or media_urls — max 4 per part. For a single status, omit thread_parts and use content."),
         }).optional().describe("Mastodon options"),
         threads: z.object({
+            location_id: z.string().nullable().optional().describe("Tag a location on the Threads post. Use an `id` from search_locations with platform \"threads\" (Threads location ids are NOT Facebook Place IDs, so never reuse the Instagram location_id here). On a multi-post thread the tag goes on the first post. Needs the workspace's Threads connection to have the threads_location_tagging permission; the API returns a clear 400 asking to reconnect Threads when it is missing, and a clear 400 while location tagging is still rolling out (disabled in this environment). On update_post, pass null to remove the tag."),
             thread_parts: z.array(THREADS_THREAD_PART).min(2).max(25).optional().describe("Publish as a chained Threads (Meta) thread instead of a single post. Provide 2 to 25 parts; parts after the first are posted as replies to the previous part. Each part holds up to 500 characters and up to 10 media (images and videos can be mixed) via media_ids (from upload_media) or media_urls. When set, the Threads caption is taken from part 1 and content is ignored for Threads. For a single post, omit thread_parts and use content."),
-        }).optional().describe("Threads (Meta) options"),
+        }).optional().describe("Threads (Meta) options: thread mode via `thread_parts`, location tag via `location_id`."),
         google_business: GOOGLE_BUSINESS_OPTIONS,
     }, { title: "Create Post", readOnlyHint: false, destructiveHint: false, openWorldHint: false }, async (params) => {
         const result = await getClient().createPost({ ...params, source: "mcp" });
@@ -841,8 +848,9 @@ Do NOT call without required media — it will fail.`, {
             thread_parts: z.array(MASTODON_THREAD_PART).min(2).max(25).optional().describe("Publish as a chained Mastodon thread (2–25 parts). Each is posted in order as a native reply (in_reply_to_id). Attach media to any part via media_ids or media_urls — max 4 per part."),
         }).optional().describe("Mastodon options"),
         threads: z.object({
+            location_id: z.string().nullable().optional().describe("Tag a location on the Threads post. Use an `id` from search_locations with platform \"threads\" (Threads location ids are NOT Facebook Place IDs, so never reuse the Instagram location_id here). On a multi-post thread the tag goes on the first post. Needs the workspace's Threads connection to have the threads_location_tagging permission; the API returns a clear 400 asking to reconnect Threads when it is missing, and a clear 400 while location tagging is still rolling out (disabled in this environment). On update_post, pass null to remove the tag."),
             thread_parts: z.array(THREADS_THREAD_PART).min(2).max(25).optional().describe("Publish as a chained Threads (Meta) thread (2 to 25 parts). Parts after the first are posted as replies to the previous part. Each part holds up to 500 characters and up to 10 media (images and videos can be mixed) via media_ids or media_urls. The Threads caption is taken from part 1."),
-        }).optional().describe("Threads (Meta) options"),
+        }).optional().describe("Threads (Meta) options: thread mode via `thread_parts`, location tag via `location_id`."),
         google_business: GOOGLE_BUSINESS_OPTIONS,
     }, { title: "Create and Publish Post", readOnlyHint: false, destructiveHint: false, openWorldHint: true }, async (params) => {
         const result = await getClient().createAndPublishPost({ ...params, source: "mcp" });
@@ -954,8 +962,9 @@ Do NOT call without required media — it will fail.`, {
             thread_parts: z.array(MASTODON_THREAD_PART).min(2).max(25).nullable().optional().describe("Replace the Mastodon thread shape on this post. Pass an array (2–25 parts) to update/create the thread (attach media to any part via media_ids or media_urls; max 4 per part), or `null` to revert to single-status mode."),
         }).optional().describe("Mastodon options"),
         threads: z.object({
+            location_id: z.string().nullable().optional().describe("Tag a location on the Threads post. Use an `id` from search_locations with platform \"threads\" (Threads location ids are NOT Facebook Place IDs, so never reuse the Instagram location_id here). On a multi-post thread the tag goes on the first post. Needs the workspace's Threads connection to have the threads_location_tagging permission; the API returns a clear 400 asking to reconnect Threads when it is missing, and a clear 400 while location tagging is still rolling out (disabled in this environment). On update_post, pass null to remove the tag."),
             thread_parts: z.array(THREADS_THREAD_PART).min(2).max(25).nullable().optional().describe("Replace the Threads (Meta) thread shape on this post. Pass an array (2 to 25 parts, 500 characters per part) to update/create the thread (attach up to 10 media to any part via media_ids or media_urls; images and videos can be mixed), or `null` to revert to single-post mode."),
-        }).optional().describe("Threads (Meta) options"),
+        }).optional().describe("Threads (Meta) options: thread mode via `thread_parts`, location tag via `location_id`."),
         google_business: GOOGLE_BUSINESS_OPTIONS,
     }, { title: "Update Post", readOnlyHint: false, destructiveHint: false, openWorldHint: false }, async ({ id, ...data }) => {
         const result = await getClient().updatePost(id, data);
@@ -1049,32 +1058,152 @@ The retry runs asynchronously (usually within a few minutes). Poll \`get_post\`
             content: [{ type: "text", text: md }],
         };
     });
-    server.tool("search_locations", `Search for an Instagram location to tag on a post. Use this whenever the user wants to post WITH a place/location (e.g. "post this at my dealership", "tag the café"). It returns matching real venues with their addresses and a location ID.
+    server.tool("approve_post", `Approve the current step of a post's approval workflow. Only works on a post with \`approval_status: "pending"\` (post status \`in_approval\`) — check \`get_post\` first.
+
+IMPORTANT: this only succeeds if the connected user is a listed approver for the workflow's CURRENT step — steps approve in order, so being an approver on a later step is not enough yet. A \`forbidden\` error means the user isn't (or isn't yet) an approver for this step; tell them who needs to approve instead, don't retry.
+
+If this is the workflow's last step, the post is finalized immediately: it moves to \`scheduled\` (future time) or \`posting\` (due now/in the past). If steps remain, the post stays \`in_approval\` and the next step's approvers are notified — call this again once they've approved, or use \`reject_post\` to stop the workflow instead.`, {
+        id: z.string().describe("The post ID to approve (must have approval_status 'pending')"),
+    }, { title: "Approve Post", readOnlyHint: false, destructiveHint: false, openWorldHint: true }, async ({ id }) => {
+        const result = await getClient().approvePost(id);
+        if (result.error) {
+            return {
+                content: [{ type: "text", text: `Error (${result.error.code}): ${result.error.message}` }],
+            };
+        }
+        const p = result.data;
+        if (!p) {
+            return {
+                content: [{ type: "text", text: "Approval recorded. Check its status with get_post." }],
+            };
+        }
+        let md = `## Approval Recorded\n\n`;
+        md += `| Field | Value |\n`;
+        md += `|-------|-------|\n`;
+        md += `| **ID** | \`${p.id}\` |\n`;
+        md += `| **Status** | ${capitalize(p.status || "in_approval")} |\n`;
+        md += `| **Approval status** | ${capitalize(p.approval_status || "pending")} |\n`;
+        if (p.message)
+            md += `\n${p.message}\n`;
+        return {
+            content: [{ type: "text", text: md }],
+        };
+    });
+    server.tool("reject_post", `Reject a post's approval workflow. Only works on a post with \`approval_status: "pending"\` (post status \`in_approval\`) — check \`get_post\` first.
+
+IMPORTANT: this only succeeds if the connected user is a listed approver for the workflow's CURRENT step (same requirement as \`approve_post\`). Unlike approval, a rejection stops the WHOLE workflow immediately, not just the current step — the post's status becomes \`rejected\` and it will not publish. Pass \`comment\` to explain why; it's shown to the requester and other approvers in the post's review thread.`, {
+        id: z.string().describe("The post ID to reject (must have approval_status 'pending')"),
+        comment: z
+            .string()
+            .max(2000)
+            .optional()
+            .describe("Optional reason for the rejection, shown to the requester and other approvers."),
+    }, { title: "Reject Post", readOnlyHint: false, destructiveHint: false, openWorldHint: true }, async ({ id, comment }) => {
+        const result = await getClient().rejectPost(id, comment);
+        if (result.error) {
+            return {
+                content: [{ type: "text", text: `Error (${result.error.code}): ${result.error.message}` }],
+            };
+        }
+        const p = result.data;
+        let md = `## Post Rejected\n\n`;
+        md += `| Field | Value |\n`;
+        md += `|-------|-------|\n`;
+        md += `| **ID** | \`${p?.id || id}\` |\n`;
+        md += `| **Status** | Rejected |\n`;
+        md += `\n_The approval workflow has stopped. This post will not be published unless it's edited and resubmitted for approval._`;
+        return {
+            content: [{ type: "text", text: md }],
+        };
+    });
+    server.tool("search_locations", `Search for a location to tag on a post. Use this whenever the user wants to post WITH a place/location (e.g. "post this at my dealership", "tag the café"). It returns matching real venues with their addresses and a location ID.
 
-Flow: call this with the place name → present the options to the user → once they pick, pass that result's \`id\` as \`location_id\` on create_post / create_and_publish_post / update_post. Only Instagram supports location tagging.
+Pick the platform with \`platform\`: "instagram" (default) or "threads". The two use DIFFERENT ids (a Facebook Place ID is not a Threads location id), so search with the platform you will tag. If the user wants both, search twice.
+
+Flow (Instagram): call with the place name → present the options to the user → once they pick, pass that result's \`id\` as \`location_id\` on create_post / create_and_publish_post / update_post.
+Flow (Threads): same, but pass the \`id\` as \`threads.location_id\`. Threads can also search by coordinates: pass latitude + longitude instead of a query. On a multi-post thread the tag goes on the first post.
 
 Notes:
 - Use a SPECIFIC venue name. Searching a broad brand ("Starbucks") returns individual store locations, not the brand page.
-- If the user already gives you a numeric Facebook Place ID, you can pass it straight to create_post as \`location_id\`; it's validated at publish time and an invalid one returns a clear error.
-- If results come back empty with a permission note, the workspace's Facebook app can't search arbitrary places — tell the user to use their own business Page's ID.`, {
+- Instagram: if the user already gives you a numeric Facebook Place ID, you can pass it straight to create_post as \`location_id\`; it's validated at publish time and an invalid one returns a clear error. If results come back empty with a permission note, the workspace's Facebook app can't search arbitrary places; tell the user to use their own business Page's ID.
+- Threads: needs the workspace's Threads connection to have the location permission; if the result says to reconnect Threads, tell the user to reconnect it under Settings → Organisation → Workspaces. Threads location tagging is currently rolling out, so the search can also answer that it is not available yet.`, {
         query: z
             .string()
-            .describe("Place name to search (min 2 chars) — a dealership, café, venue, etc."),
-    }, { title: "Search Locations", readOnlyHint: true, destructiveHint: false, openWorldHint: true }, async ({ query }) => {
-        const result = await getClient().searchLocations(query);
+            .optional()
+            .describe("Place name to search (min 2 chars): a dealership, café, venue, etc. Required for instagram; for threads pass either query or latitude + longitude."),
+        platform: z
+            .enum(["instagram", "threads"])
+            .optional()
+            .describe("Which platform the location will be tagged on. Defaults to instagram. Use threads to get a Threads location id for threads.location_id."),
+        latitude: z
+            .number()
+            .min(-90)
+            .max(90)
+            .optional()
+            .describe("Threads only. Search places around this point; pass together with longitude instead of query."),
+        longitude: z
+            .number()
+            .min(-180)
+            .max(180)
+            .optional()
+            .describe("Threads only. Pass together with latitude."),
+    }, { title: "Search Locations", readOnlyHint: true, destructiveHint: false, openWorldHint: true }, async ({ query, platform, latitude, longitude }) => {
+        const target = platform === "threads" ? "threads" : "instagram";
+        if (!query && target !== "threads") {
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: 'Pass a place name to search (query). Coordinates are only supported with platform "threads".',
+                    },
+                ],
+            };
+        }
+        if (target === "threads" && !query && (latitude === undefined || longitude === undefined)) {
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: "Pass a place name (query), or both latitude and longitude.",
+                    },
+                ],
+            };
+        }
+        const result = await getClient().searchLocations(query, target, latitude !== undefined || longitude !== undefined
+            ? { latitude, longitude }
+            : undefined);
+        const label = query ? `"${query}"` : `${latitude}, ${longitude}`;
+        if (target === "threads") {
+            const locations = result?.locations || [];
+            if (!locations.length) {
+                // Threads answers with a { code, message } error object when the
+                // search could not run (not_available, threads_not_connected,
+                // threads_reauth_required, platform_error).
+                const err = result?.error;
+                const why = (typeof err === "string" ? err : err?.message) ||
+                    `No Threads locations found for ${label}. Try a more specific place name.`;
+                return { content: [{ type: "text", text: why }] };
+            }
+            let md = `## Threads locations matching ${label}\n\nAsk the user which one, then use its ID as \`threads.location_id\`:\n\n`;
+            md += `| # | Name | Address | City | Country | threads.location_id |\n|---|------|---------|------|---------|---------------------|\n`;
+            locations.forEach((p, i) => {
+                md += `| ${i + 1} | ${p.name || "-"} | ${p.address || "-"} | ${p.city || "-"} | ${p.country || "-"} | \`${p.id}\` |\n`;
+            });
+            return { content: [{ type: "text", text: md }] };
+        }
         const places = result?.data || [];
         if (!places.length) {
             // The degraded path returns `error` as a plain string; the object form
             // only appears on transport failures — render its message.
             const err = result?.error;
             const why = (typeof err === "string" ? err : err?.message) ||
-                `No taggable locations found for "${query}". Try a more specific venue name, or pass a known Facebook Place ID directly as location_id.`;
+                `No taggable locations found for ${label}. Try a more specific venue name, or pass a known Facebook Place ID directly as location_id.`;
             return { content: [{ type: "text", text: why }] };
         }
-        let md = `## Locations matching "${query}"\n\nAsk the user which one, then use its ID as \`location_id\`:\n\n`;
+        let md = `## Instagram locations matching ${label}\n\nAsk the user which one, then use its ID as \`location_id\`:\n\n`;
         md += `| # | Name | Address | location_id |\n|---|------|---------|-------------|\n`;
         places.forEach((p, i) => {
-            md += `| ${i + 1} | ${p.name} | ${p.address || "—"} | \`${p.id}\` |\n`;
+            md += `| ${i + 1} | ${p.name} | ${p.address || "-"} | \`${p.id}\` |\n`;
         });
         return { content: [{ type: "text", text: md }] };
     });

package/build/types.d.ts

@@ -28,7 +28,7 @@ export interface InboxParticipant {
 }
 export interface InboxConversation {
     conversation_id: string;
-    platform: "instagram" | "facebook" | "linkedin" | "tiktok" | "x";
+    platform: "instagram" | "facebook" | "linkedin" | "tiktok" | "x" | "youtube" | "threads";
     type: "dm" | "comment" | "mention";
     participant: InboxParticipant;
     unread_count: number;
@@ -57,6 +57,18 @@ export interface InboxMessage {
     is_replied: boolean;
     reaction: string | null;
     parent_comment_id: string | null;
+    /** Threads replies only: true when the reply is hidden on Threads (flip it
+     * with hide_inbox_reply). null for every other platform. */
+    hidden?: boolean | null;
+    /** Link to the reply or mentioning post on the platform, when known. */
+    permalink?: string | null;
+    /** Media sent with this message, when present. Incoming Instagram/Facebook
+     * DM images, videos, voice messages, and story mentions are re-hosted on
+     * our CDN so the URL stays valid indefinitely. */
+    attachment?: {
+        url: string;
+        type: "image" | "video" | "audio" | "file";
+    } | null;
     sender: InboxParticipant;
     post: {
         id: string | null;
@@ -207,6 +219,21 @@ export interface RetryPostResult {
     platforms?: string[];
     message?: string;
 }
+/** `data` of POST /posts/:id/approve (backend/routes/api/v1/posts.js). */
+export interface ApprovePostResult {
+    id: string;
+    /** The post's status after this call: `in_approval` (more steps remain), `scheduled`, or `posting`. */
+    status: string;
+    approval_status: "pending" | "approved";
+    message?: string;
+}
+/** `data` of POST /posts/:id/reject (backend/routes/api/v1/posts.js). */
+export interface RejectPostResult {
+    id: string;
+    status: "rejected";
+    approval_status: "rejected";
+    message?: string;
+}
 /** One place from GET /locations/search
  * (@openapi block in backend/routes/api/v1/locations.js). */
 export interface LocationPlace {
@@ -217,12 +244,30 @@ export interface LocationPlace {
     city?: string | null;
     country?: string | null;
 }
-/** GET /locations/search envelope — NOT the standard data/error envelope:
- * on the documented degraded path (no Facebook account / missing permission)
- * `error` is a human-readable STRING next to an empty `data`; the standard
- * { code, message } object appears only on transport/HTTP failures. */
+/** One place from GET /locations/search?platform=threads. Threads location
+ * ids are NOT Facebook Place IDs; use them as `threads.location_id`. */
+export interface ThreadsLocationPlace {
+    /** Threads location id: use as `threads.location_id`. */
+    id: string;
+    name?: string | null;
+    address?: string | null;
+    city?: string | null;
+    country?: string | null;
+    latitude?: number | null;
+    longitude?: number | null;
+}
+/** GET /locations/search envelope: NOT the standard data/error envelope.
+ * platform=instagram (default): `data` holds LocationPlace rows; on the
+ * documented degraded path (no Facebook account / missing permission)
+ * `error` is a human-readable STRING next to an empty `data`.
+ * platform=threads: `locations` holds ThreadsLocationPlace rows, and when
+ * the search could not run `error` is a { code, message } OBJECT with code
+ * one of not_available | threads_not_connected | threads_reauth_required |
+ * platform_error. The standard { code, message } object also appears on
+ * transport/HTTP failures. */
 export interface LocationSearchResult {
     data?: LocationPlace[];
+    locations?: ThreadsLocationPlace[];
     error?: string | {
         code: string;
         message: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omnisocials/mcp-server",
-  "version": "1.28.0",
+  "version": "1.31.0",
   "mcpName": "io.github.omnisocials/mcp-server",
   "description": "MCP server for OmniSocials API - manage social media posts, media, accounts, analytics, and webhooks",
   "type": "module",