@omnisocials/mcp-server 1.49.0 → 1.50.0

package/README.md

@@ -202,6 +202,7 @@ Apply a set when creating a post: `create_post` / `create_and_publish_post` acce
 | `get_inbox_conversation` | Get a conversation's full message history with the post it belongs to; every message shows its `#id` |
 | `mark_inbox_read` | Mark all incoming messages in a conversation as read (also the durable skip for `get_next_unanswered`) |
 | `reply_to_inbox` | Reply to a DM, comment, or mention (existing conversations only); `message_id` picks the comment being answered; `include_next` returns the next unanswered item in the same call |
+| `like_inbox_comment` | Like or unlike a comment on one of your posts as the account (Facebook Page, LinkedIn Page, TikTok; Facebook allows a Like only) |
 | `hide_inbox_comment` | Hide or unhide a comment on one of your posts (Facebook, Instagram, TikTok, YouTube, Threads) |
 | `delete_inbox_comment` | Permanently delete a comment on one of your posts, with the replies under it (Facebook, Instagram, TikTok) |
 | `hide_inbox_reply` | Older name for `hide_inbox_comment`, kept for compatibility |
@@ -244,6 +245,10 @@ Full API docs: [docs.omnisocials.com](https://docs.omnisocials.com)
 
 ## Changelog
 
+### 1.50.0 (2026-10-27)
+
+- **Added: `like_inbox_comment`.** Like (or unlike with `like: false`) a Facebook, LinkedIn Page or TikTok comment as the connected account. Facebook allows a Like only. Inbox messages carry `liked`.
+
 ### 1.49.0 (2026-10-27)
 
 - **Added: the Threads topic.** `threads.topic_tag` on `create_post`, `create_and_publish_post` and `update_post` (one topic per post, 1 to 50 characters, spaces allowed, no period or ampersand; `null` removes it on update). `get_post` shows it.

package/build/client.d.ts

@@ -574,5 +574,6 @@ export declare class OmniSocialsClient {
         exclude?: string;
     }): Promise<ApiResponse<InboxNextUnanswered | null>>;
     hideInboxMessage(messageId: string, hide?: boolean): Promise<ApiResponse<InboxMessage>>;
+    likeInboxMessage(messageId: string, like?: boolean): Promise<ApiResponse<InboxMessage>>;
     deleteInboxMessage(messageId: string): Promise<ApiResponse<InboxDeleteResult>>;
 }

package/build/client.js

@@ -585,6 +585,12 @@ export class OmniSocialsClient {
     async hideInboxMessage(messageId, hide = true) {
         return this.request("POST", `/inbox/messages/${encodeURIComponent(messageId)}/hide`, { hide });
     }
+    // Like/unlike a comment as the connected account (Facebook Page, LinkedIn
+    // Page, TikTok). `like: false` removes the like. Needs the inbox:write
+    // scope.
+    async likeInboxMessage(messageId, like = true) {
+        return this.request("POST", `/inbox/messages/${encodeURIComponent(messageId)}/like`, { like });
+    }
     // Delete a comment on the platform and from the inbox (Facebook, Instagram,
     // TikTok; YouTube cannot delete other people's comments, hide instead).
     // Replies under it go too. Needs the inbox:write scope.

package/build/index.js

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

package/build/tools/inbox.js

@@ -61,6 +61,8 @@ function renderInboxMessages(msgs, highlightId) {
         }
         if (m.hidden)
             flags.push("hidden");
+        if (m.liked)
+            flags.push("liked");
         if (m.parent_comment_id)
             flags.push("reply to a comment");
         md += `**${who}** _(${formatDateTime(m.timestamp)})_ \`#${m.id}\`${flags.length ? " · " + flags.join(" · ") : ""}\n${m.text || ""}\n`;
@@ -88,7 +90,7 @@ function renderNextUnanswered(result) {
     md += renderInboxPost(item.message.post || c.post);
     md += renderInboxMessages(item.messages, item.message.id);
     md += `_${result.remaining || 0} more waiting._\n\n`;
-    md += `_Reply: reply_to_inbox with the conversation ID and message_id: "${item.message.id}" (add include_next: true to get the next one in the same call). Skip for good: mark_inbox_read. Comments: hide_inbox_comment / delete_inbox_comment with the message id._`;
+    md += `_Reply: reply_to_inbox with the conversation ID and message_id: "${item.message.id}" (add include_next: true to get the next one in the same call). Skip for good: mark_inbox_read. Comments: like_inbox_comment / hide_inbox_comment / delete_inbox_comment with the message id._`;
     return md;
 }
 export function registerInboxTools(server, getClient) {
@@ -154,7 +156,7 @@ export function registerInboxTools(server, getClient) {
         }
         return { content: [{ type: "text", text: md }] };
     });
-    server.tool("get_inbox_conversation", "Get the full message history of one inbox conversation, oldest first, with the post it belongs to (caption, link, image) for comment/mention threads. Each message shows its inbox id (#id): that id is what hide_inbox_comment and delete_inbox_comment take. Use the conversation_id from list_inbox_conversations. Replies sent from the native apps appear as outgoing messages too.", {
+    server.tool("get_inbox_conversation", "Get the full message history of one inbox conversation, oldest first, with the post it belongs to (caption, link, image) for comment/mention threads. Each message shows its inbox id (#id): that id is what like_inbox_comment, hide_inbox_comment and delete_inbox_comment take. Use the conversation_id from list_inbox_conversations. Replies sent from the native apps appear as outgoing messages too.", {
         conversation_id: z.string().describe("The conversation ID to fetch"),
         limit: z
             .number()
@@ -320,6 +322,28 @@ export function registerInboxTools(server, getClient) {
     // Older name from 1.28.0 (when hiding was Threads-only). Kept so existing
     // setups keep working; same call, same platforms as hide_inbox_comment.
     server.tool("hide_inbox_reply", "Older name for hide_inbox_comment, kept so existing setups keep working; prefer hide_inbox_comment. Same behaviour: hide (or unhide with hide: false) a comment someone left on one of the workspace's posts, as the post owner, on Facebook, Instagram, TikTok, YouTube or Threads. Takes the message id (the #id in the thread), not the conversation id. A 403 reconnect_required means the account must be reconnected in the dashboard to grant the comment-moderation permission.", hideCommentSchema, { title: "Hide Inbox Comment (older name)", readOnlyHint: false, destructiveHint: false, openWorldHint: true }, hideComment);
+    server.tool("like_inbox_comment", "Like (or remove the like from) a comment someone left on one of the workspace's posts, as the connected account: the Facebook Page, the LinkedIn Page or the TikTok account. Incoming Facebook, LinkedIn Page and TikTok comments only. Facebook allows a Like only: no app can add Love or another reaction, so say so when the user asks for one. Takes the message id (the #id shown by get_inbox_conversation and get_next_unanswered), not the conversation id. Liking an already liked comment succeeds and changes nothing. A like does not mark the comment as read or answered: to move past it in get_next_unanswered without a reply, use mark_inbox_read or exclude. Like only comments the user asked you to like, or that match a rule the user gave (for example 'like the positive comments'); never like in bulk on your own. A 403 reconnect_required or 401 reauth_required means the account must be reconnected in the dashboard; relay that to the user rather than retrying.", {
+        message_id: z
+            .string()
+            .describe("The inbox message id of the comment (the #id in the thread)"),
+        like: z
+            .boolean()
+            .optional()
+            .describe("true (default) to like, false to remove the like"),
+    }, { title: "Like Inbox Comment", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: true }, async ({ message_id, like }) => {
+        const result = await getClient().likeInboxMessage(message_id, like !== false);
+        if (result.error)
+            return errorResult(result.error);
+        const m = result.data;
+        return {
+            content: [
+                {
+                    type: "text",
+                    text: `Comment \`#${m?.id ?? message_id}\` on ${m?.platform || "the platform"} is now ${m?.liked ? "liked" : "not liked"}.`,
+                },
+            ],
+        };
+    });
     server.tool("delete_inbox_comment", "Permanently delete a comment someone left on one of the workspace's posts, on the platform and from the inbox. Facebook, Instagram and TikTok comments only (YouTube's API cannot delete other people's comments: use hide_inbox_comment there). Replies under the comment are deleted with it. This cannot be undone: confirm with the user before calling. Takes the message id (the #id in the thread), not the conversation id. A 403 reconnect_required means the account must be reconnected in the dashboard to grant the moderation permission.", {
         message_id: z
             .string()

package/build/types.d.ts

@@ -76,6 +76,10 @@ export interface InboxMessage {
      * YouTube, Threads): true when the comment is hidden on the platform (flip
      * it with hide_inbox_comment). null for DMs. */
     hidden?: boolean | null;
+    /** Incoming Facebook, LinkedIn Page and TikTok comments: true when the
+     * connected account liked the comment (flip it with like_inbox_comment).
+     * null for DMs, outgoing messages and the other platforms. */
+    liked?: 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

package/package.json

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