BulkPublish
NPM · @BULKPUBLISH/MCP-SERVER · 2 COMPONENTS
Schedule, cross-post, and analyze social media posts across 15 platforms from AI agents.
Available components
Last scanned (22 hours ago)
Scores higher than 77% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14478 tokens (~168/item across 86 items; 80 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
- Structured output schemas are declared (41% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 15 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 82 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (17)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- Stability: 0.97 → pass security
- 19 Nov 26 0
- Stability: pass → 0.97 functional
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 11 Nov 26 −3
- Known CVEs: pass → unverified ▼ security
- Schema quality: 145 → 168 ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Schema quality: 0% → 100% ▲ functional
- Tool coverage: 35% → 41% ▲ functional
- Package version: 1.42.0 → 1.53.0 functional
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@bulkpublish/mcp-server@1.53.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_rss_feeds List RSS feeds ~107
List RSS autopost feeds — RSS/Atom feeds, checked on a schedule set by the plan (every 60 minutes on Free and Lifetime, 30 on Pro, 15 on Business), whose new items automatically become posts. Returns name, feedUrl, channelIds, mode, fieldMapping (how items are rendered into posts; null = default), enabled, lastCheckedAt, and lastError for each feed. Use this when the user wants their RSS autopost feeds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_schedules List recurring schedules ~91
List recurring post schedules, newest first (at most 500; a workspace with more gets the 500 most recently created). Returns schedule name, frequency/timeOfDay timing fields, target channels, active status, and nextRunAt. These schedules also appear in the web app: managed on the Repeat Posts page, with upcoming runs shown on the Calendar. Use this when the user wants their recurring posting schedules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List post templates ~75
List the organization's saved post templates — reusable text to start a new post from. Filter by kind to get saved first-comment snippets instead of captions. Use this when the user wants their saved post templates, or wants to start a post from one.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Which kind of saved text to list. Defaults to caption. |
No output schema declared.
No examples provided.
moderate_comment Like, hide or delete comment ~257
Like, unlike, hide, unhide or delete a comment on one of the workspace's published posts, on the platform, as the channel the post was published to. Likes and hides can be undone; delete is permanent and needs a role that can publish. Hiding or deleting also removes the comment from the Inbox. Which actions a channel supports is in its commentActions from list_post_comments (Threads supports hide and unhide; Facebook supports hide, unhide and delete). A comment hidden on Threads or Facebook comes back with hidden: true. If the channel's connection has stopped working, the call is refused and the channel needs reconnecting from the Channels page. Replying to and moderating comments is on every plan except Free; on Free, or before it is available to the account, the call is refused with a message saying so. Use this when the user wants to like, hide or delete a comment on one of their published posts.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do with the comment. |
| commentId | string | yes | The comment's id from list_post_comments. |
| postId | number | yes | The post id. |
| postPlatformId | number | yes | The channel's postPlatformId from list_post_comments. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string|null | – | The action that was applied. |
| success | boolean|null | – | true when the action was applied. |
No examples provided.
publish_post Publish post now ~154
Publish a draft or scheduled post immediately. The post will be queued for publishing to all its target channels. Requires a role with post:publish — contributors get 403 APPROVAL_REQUIRED and must submit the post for approval instead (create/update with requestApproval, then a teammate approves). To 'publish now' with approval, create_post with status 'scheduled', scheduledAt = now, requestApproval true and publishWhenApproved true, so it goes out the moment it is approved. Publishing a pending/rejected post as an approver implicitly approves it. Use this when the user wants to publish an existing draft or scheduled post right now.
| Name | Type | Req | Description |
|---|---|---|---|
| postId | number | yes | The post ID to publish, from create_post or list_posts. |
| Name | Type | Req | Description |
|---|---|---|---|
| approvalStatus | string|null | – | Team approval state: none, pending, approved or rejected. |
| approver | – | – | Who approved it: { id, name, image }. Null unless approvalStatus is approved. |
| assignee | – | – | Who is expected to act on it next: { id, name, image }. Null when nobody is. |
| author | – | – | Who wrote the post: { id, name, image }. Null when that account is gone. |
| content | string|null | – | The post's main text. |
| createdAt | string|null | – | ISO 8601 time the post was created. |
| id | number|string|null | – | The post's ID, used by get_post, update_post, publish_post and delete_post. |
| labels | – | – | Labels on the post. |
| mediaFiles | – | – | Media on the post itself: file IDs after create_post or update_post, full file objects from get_post and list_posts. |
| postPlatforms | – | – | One entry per destination, with its platform and its own publish status. |
| publishedAt | string|null | – | ISO 8601 time the post was published. |
| recurringSchedule | – | – | get_post and list_posts: the repeat schedule the post belongs to, or null. |
| scheduledAt | string|null | – | ISO 8601 time the post is scheduled for. |
| status | string|null | – | draft, scheduled, publishing, processing, published, partial or failed. |
| threadMediaFiles | – | – | get_post and list_posts: the media the thread parts reference. Not included in mediaFiles. |
| threadParts | – | – | For a thread post: its parts, in order. |
| timezone | string|null | – | Time zone the schedule was set in. |
No examples provided.
publish_story Publish story ~62
Publish a post as a story on Facebook or Instagram. Use this when the user wants to post an Instagram/Facebook story.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | Platform to publish the story on. |
| postId | number | yes | The post ID to publish as a story. |
No output schema declared.
No examples provided.
reject_post Reject pending post ~275
Reject a post awaiting team approval. Requires a role with post:approve. The post returns to draft with approvalStatus 'rejected' and the optional reason; the author is notified and can edit + reschedule to resubmit for approval. Rejecting sets publishWhenApproved to false. Pass the updatedAt you reviewed as ifUnmodifiedSince to refuse the rejection if the post changed since. Errors: 400 if the post is not awaiting approval or ifUnmodifiedSince is not a timestamp, 403 if the role lacks post:approve, 404 if not found, 409 if the post changed since you loaded it (checked when ifUnmodifiedSince is sent) or is no longer awaiting approval — reload it with get_post and review again. Use this when the user (an owner/admin/approver) wants to reject a post awaiting team approval, optionally with a reason.
| Name | Type | Req | Description |
|---|---|---|---|
| ifUnmodifiedSince | string | – | Optional. The post's updatedAt (ISO 8601) as you last loaded it with get_post. If the post changed since, nothing is written and the call returns 409. |
| postId | number | yes | The post ID to reject. |
| reason | string | – | Optional reason (max 2000 chars). Shown to the author (in-app notification + on the post). |
| Name | Type | Req | Description |
|---|---|---|---|
| approvalStatus | string|null | – | Team approval state: none, pending, approved or rejected. |
| approver | – | – | Who approved it: { id, name, image }. Null unless approvalStatus is approved. |
| assignee | – | – | Who is expected to act on it next: { id, name, image }. Null when nobody is. |
| author | – | – | Who wrote the post: { id, name, image }. Null when that account is gone. |
| content | string|null | – | The post's main text. |
| createdAt | string|null | – | ISO 8601 time the post was created. |
| id | number|string|null | – | The post's ID, used by get_post, update_post, publish_post and delete_post. |
| labels | – | – | Labels on the post. |
| mediaFiles | – | – | Media on the post itself: file IDs after create_post or update_post, full file objects from get_post and list_posts. |
| postPlatforms | – | – | One entry per destination, with its platform and its own publish status. |
| publishedAt | string|null | – | ISO 8601 time the post was published. |
| recurringSchedule | – | – | get_post and list_posts: the repeat schedule the post belongs to, or null. |
| scheduledAt | string|null | – | ISO 8601 time the post is scheduled for. |
| status | string|null | – | draft, scheduled, publishing, processing, published, partial or failed. |
| threadMediaFiles | – | – | get_post and list_posts: the media the thread parts reference. Not included in mediaFiles. |
| threadParts | – | – | For a thread post: its parts, in order. |
| timezone | string|null | – | Time zone the schedule was set in. |
No examples provided.
reply_to_comment Reply to comment ~225
Reply to a comment on one of the workspace's published posts. The reply is posted publicly on the platform right away, as the channel the post was published to, and it cannot be taken back from here. Up to 2,000 characters. If the channel's connection has stopped working, the call is refused and the channel needs reconnecting from the Channels page. Comment replies are on every plan except Free; on Free, or before they are available to the account, the call is refused with a message saying so. Use this when the user wants to answer a comment on one of their published posts.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | The comment's id from list_post_comments. |
| postId | number | yes | The post id. |
| postPlatformId | number | yes | The channel's postPlatformId from list_post_comments. |
| rootCommentId | string | – | When replying to a reply: the thread's top-level comment id (Instagram and YouTube). Leave it out when replying to a top-level comment. |
| text | string | yes | The reply text. |
| Name | Type | Req | Description |
|---|---|---|---|
| accountName | string|null | – | The account the reply was posted as. |
| replyId | string|null | – | The platform's id for the new reply. |
| success | boolean|null | – | true when the reply was posted. |
No examples provided.
reply_to_conversation Reply in Inbox conversation ~253
Send a reply in an Inbox conversation. The message goes to the person on the platform right away, from the channel the conversation belongs to, and it cannot be unsent. Send text (up to 4,000 characters), up to 4 media library files, or both; reviews and comment threads take text only. Facebook Messenger and Instagram accept a reply only within 24 hours of the person's last message; after that the call is refused. If the channel's connection has stopped working, the call is refused and the channel needs reconnecting from the Channels page. The Inbox is part of the Pro and Business plans; on other plans, or before it is available to the account, the call is refused with a message saying so. Use this when the user wants to answer a direct message, review or comment thread in their Inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | number | yes | The conversation id from list_conversations. |
| mediaIds | array | – | Media library file ids to attach (direct messages only). |
| replyToMessageId | number | – | Comment threads only: the id of the incoming message to answer. Defaults to the newest one from the other person. |
| text | string | – | The reply text. |
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string|null | – | The platform's id for the sent message. |
| success | boolean|null | – | – |
No examples provided.
retry_post Retry failed post ~219
Retry publishing a failed or partially failed post. Only retries the platforms that failed, not the ones that already succeeded. Platforms in status 'unconfirmed' (the publish request may have reached the platform but its response was lost — the post may already be live) are NOT retried unless republish is true; if the post has unconfirmed platforms and no failed ones, the call fails with a 400 and code UNCONFIRMED_REQUIRES_REPUBLISH — ask the user to check the account on the platform, and only pass republish: true after they confirm the post is not live. Use this when a post failed on some platforms and the user wants to retry just those.
| Name | Type | Req | Description |
|---|---|---|---|
| postId | number | yes | The post ID to retry. |
| republish | boolean | – | Explicit opt-in to also retry platforms in status 'unconfirmed'. Their publish may have already gone through, so this can DUPLICATE the post — only pass true after the user has checked the account an… |
| Name | Type | Req | Description |
|---|---|---|---|
| approvalStatus | string|null | – | Team approval state: none, pending, approved or rejected. |
| approver | – | – | Who approved it: { id, name, image }. Null unless approvalStatus is approved. |
| assignee | – | – | Who is expected to act on it next: { id, name, image }. Null when nobody is. |
| author | – | – | Who wrote the post: { id, name, image }. Null when that account is gone. |
| content | string|null | – | The post's main text. |
| createdAt | string|null | – | ISO 8601 time the post was created. |
| id | number|string|null | – | The post's ID, used by get_post, update_post, publish_post and delete_post. |
| labels | – | – | Labels on the post. |
| mediaFiles | – | – | Media on the post itself: file IDs after create_post or update_post, full file objects from get_post and list_posts. |
| postPlatforms | – | – | One entry per destination, with its platform and its own publish status. |
| publishedAt | string|null | – | ISO 8601 time the post was published. |
| recurringSchedule | – | – | get_post and list_posts: the repeat schedule the post belongs to, or null. |
| retriedCount | number|string|null | – | How many destinations were retried. |
| scheduledAt | string|null | – | ISO 8601 time the post is scheduled for. |
| skippedMaxRetries | number|string|null | – | Destinations skipped for hitting the retry ceiling. |
| status | string|null | – | draft, scheduled, publishing, processing, published, partial or failed. |
| threadMediaFiles | – | – | get_post and list_posts: the media the thread parts reference. Not included in mediaFiles. |
| threadParts | – | – | For a thread post: its parts, in order. |
| timezone | string|null | – | Time zone the schedule was set in. |
No examples provided.
search_mentions Search mentions ~140
Search for @mention suggestions on a channel (X, Bluesky, Mastodon, LinkedIn). On LinkedIn the query is a Page's URL slug (exact match), each result's handle is a ready-to-paste @[Name](urn:li:organization:ID) token, and vanityName is the slug it matched — check it against the Page you meant before using the token, since a display name alone is ambiguous. Use this when you need @mention suggestions from a connected channel while drafting a post.
| Name | Type | Req | Description |
|---|---|---|---|
| channelId | number | yes | The channel ID to search mentions on. |
| query | string | yes | Search query for the mention lookup. |
No output schema declared.
No examples provided.
share_post Create post review link ~134
Create (or fetch) a post's read-only review link that anyone can open without signing in — for client approval outside the app. Returns { shareToken, url, created }. regenerate=true mints a new link and kills the old one. Pro and Business only: on the single-seat Free and Lifetime plans this answers 403 FEATURE_DISABLED with the plan and an upgrade hint. Use this when the user wants a link a client or colleague can open to review a post without an account.
| Name | Type | Req | Description |
|---|---|---|---|
| postId | number | yes | The post ID. |
| regenerate | boolean | – | Mint a new token, invalidating the previous link. |
No output schema declared.
No examples provided.
unshare_post Revoke post review link ~79
Revoke a post's review link so the URL stops working. Idempotent. Pro and Business only: on the single-seat Free and Lifetime plans this answers 403 FEATURE_DISABLED with the plan and an upgrade hint. Use this when the user wants to stop a shared review link from working.
| Name | Type | Req | Description |
|---|---|---|---|
| postId | number | yes | The post ID. |
No output schema declared.
No examples provided.
update_calendar_note Update calendar note ~87
Change a calendar note's day, text and/or colour (partial update — at least one field is required). Use this when the user wants to move, reword or recolour a calendar note.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| color | string | – | – |
| date | string | – | New date, YYYY-MM-DD. |
| noteId | number | yes | The note ID. |
No output schema declared.
No examples provided.
update_channel Update channel sync settings ~216
Change a connected channel's sync settings. Both switches apply to X channels only, where every read is billed, and each is off until turned on: metricsSyncEnabled turns on analytics sync (at most once every 7 days) and the list of people who liked a post; inboxSyncEnabled turns on direct messages and replies to the channel's posts. Send at least one. On a channel of any other platform the call succeeds but changes nothing. Needs a role that can manage channels (owner, admin, approver). Does not connect, reconnect or remove a channel. Use this when the user wants to turn analytics sync or direct-message/reply reading on or off for an X channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channelId | number | yes | The channel ID (from list_channels). |
| inboxSyncEnabled | boolean | – | X only. Turn reading direct messages and replies on or off. Omit to leave unchanged. |
| metricsSyncEnabled | boolean | – | X only. Turn analytics sync and liker lists on or off. Omit to leave unchanged. |
| Name | Type | Req | Description |
|---|---|---|---|
| success | boolean|null | – | true when the settings were saved. |
No examples provided.
update_channel_set Update channel set ~114
Update a channel set's name and/or channels (partial update — at least one field is required). A name that collides with another set fails with a 409, code DUPLICATE_NAME. Use this when the user wants to rename a channel set or change its channels.
| Name | Type | Req | Description |
|---|---|---|---|
| channelIds | array | – | Replacement channel IDs (at least 1). |
| name | string | – | New set name (max 100 chars, unique per organization). |
| setId | number | yes | The channel set ID to update. |
No output schema declared.
No examples provided.
update_conversation Update Inbox conversation ~235
Change how the workspace handles one Inbox conversation: mark it read or unread, archive or reopen it, snooze it until a time (at most 90 days out), or assign it to a teammate, who is notified. Nothing is sent to the other person and nothing changes on the platform. Send at least one field. The Inbox is part of the Pro and Business plans; on other plans, or before it is available to the account, the call is refused with a message saying so. Use this when the user wants to mark a conversation read or unread, archive or reopen it, snooze it, or assign it to a teammate.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedUserId | string|null | – | A workspace member's user id; null unassigns. |
| conversationId | number | yes | The conversation id from list_conversations. |
| read | boolean | – | true marks it read, false unread. |
| snoozedUntil | string|null | – | ISO timestamp in the future to snooze until; null unsnoozes. |
| status | string | – | archived archives it, open reopens it. Either clears a snooze. |
| Name | Type | Req | Description |
|---|---|---|---|
| success | boolean|null | – | true when the change was saved. |
No examples provided.
update_hashtag_group Update hashtag group ~77
Rename a hashtag group and/or replace its hashtags (partial update — at least one field is required). Use this when the user wants to rename a hashtag group or change its hashtags.
| Name | Type | Req | Description |
|---|---|---|---|
| groupId | number | yes | The hashtag group ID. |
| hashtags | array | – | Replacement hashtag list. |
| name | string | – | New name. |
No output schema declared.
No examples provided.
update_label Update label ~73
Update an existing label's name or color. Use this when the user wants to rename or recolor a label.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | New hex color code (e.g. "#ef4444"). |
| labelId | number | yes | The label ID to update. |
| name | string | – | New label name. |
No output schema declared.
No examples provided.
update_media Set media alt text ~116
Set a media file's alt text (accessibility description). It belongs to the file, so one value covers every post that reuses it, and is sent to Instagram, LinkedIn, X, Bluesky, Tumblr and Discord. Pass an empty string to clear. Use this when the user wants to add or change an image's alt text / accessibility description.
| Name | Type | Req | Description |
|---|---|---|---|
| altText | string | yes | Description of the image for people who cannot see it. Empty string clears it. |
| mediaId | number | yes | The media file ID. |
No output schema declared.
No examples provided.
update_post Update post ~1,149
Update an existing post. Can change content, schedule, media, labels, status, target channels, per-platform text, thread parts, assignee, recurring schedule, and platform-specific settings. Only draft, scheduled, failed, or partial posts can be edited; editing a failed post resets it to draft, a partial post stays partial. Set status to 'draft' or 'scheduled' to move the post between those states — scheduling a partial post re-queues only its failed channels; use publish_post to publish immediately. To add or remove a channel, send `channels` with the COMPLETE list the post should keep (read it from get_post first): channels left out are dropped from the post, new ones are added as pending, and the ones kept keep their publish state. Use this when the user wants to edit an existing post.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedUserId | string|null | – | Optional. The member expected to act on this post next (a user id from the organization), or null to unassign. Omit to leave the assignment unchanged. |
| channels | array | – | Optional. The FULL list of channels the post should target after this update — not a diff, and at least one. Channels already on the post that you include keep their state (a published one is not re-… |
| content | string | – | New post text content. |
| ifUnmodifiedSince | string | – | Optional precondition: the post's updatedAt exactly as the last read returned it. The update is refused with 409 CONFLICT if a teammate has changed the post since, rather than overwriting their versi… |
| labelIds | array | – | Replace label IDs on the post. |
| linkTrackingOverride | boolean|null | – | Optional per-post override for link tracking (bulkpubli.sh). true forces links in this post to be shortened and their clicks counted, false forces them to publish as written, and null clears the over… |
| mediaFileIds | array | – | Replace attached media file IDs. |
| platformContent | object | – | Optional per-platform text overrides, keyed by platform. Replaced wholesale, not merged: send every platform's override you want to keep, or omit to leave them unchanged. |
| platformSpecific | object | – | Platform-specific settings, e.g. { "youtube": { "title": "…", "privacyStatus": "public" } }. Discord, Telegram, Tumblr and Snapchat nest their options under the BulkPublish channel id, e.g. { "discor… |
| postFormat | string | – | Optional. 'thread' to turn the post into a multi-part thread (send threadParts too), 'post' for a single post. |
| postId | number | yes | The post ID to update. |
| postTypeOverrides | object | – | Per-platform post type override. E.g. { "instagram": "reel", "youtube": "short" }. Video length is checked per type when the post is scheduled or published, and a video outside the range is refused:… |
| publishWhenApproved | boolean | – | Optional. Set true to have the post go out as soon as it is approved, even after its scheduled time (see create_post). An explicit value is stored while the post waits for approval. Omitted, it is ke… |
| recurringScheduleId | number|null | – | Optional. Attach the post to a recurring schedule by id, or null to detach it. Omit to leave it unchanged. |
| requestApproval | boolean | – | Optional (default false). Set true to hold a scheduled post for team approval (approvalStatus becomes 'pending'). Forced on server-side for API keys of roles without post:publish (contributors), rega… |
| scheduledAt | string | – | New ISO 8601 scheduled datetime. |
| status | string | – | Move the post between draft and scheduled. 'scheduled' requires a future scheduledAt (in this call or already stored) and at least one channel; 'draft' unschedules it. Any other value is rejected. Om… |
| threadParts | array | – | Optional. Replace the thread parts (at least 2 when postFormat is thread). Every part is measured against the character limit of every platform the post targets; an over-long part is rejected naming… |
| timezone | string | – | Timezone for scheduling. |
| Name | Type | Req | Description |
|---|---|---|---|
| approvalStatus | string|null | – | Team approval state: none, pending, approved or rejected. |
| approver | – | – | Who approved it: { id, name, image }. Null unless approvalStatus is approved. |
| assignee | – | – | Who is expected to act on it next: { id, name, image }. Null when nobody is. |
| author | – | – | Who wrote the post: { id, name, image }. Null when that account is gone. |
| content | string|null | – | The post's main text. |
| createdAt | string|null | – | ISO 8601 time the post was created. |
| id | number|string|null | – | The post's ID, used by get_post, update_post, publish_post and delete_post. |
| labels | – | – | Labels on the post. |
| mediaFiles | – | – | Media on the post itself: file IDs after create_post or update_post, full file objects from get_post and list_posts. |
| postPlatforms | – | – | One entry per destination, with its platform and its own publish status. |
| publishedAt | string|null | – | ISO 8601 time the post was published. |
| recurringSchedule | – | – | get_post and list_posts: the repeat schedule the post belongs to, or null. |
| scheduledAt | string|null | – | ISO 8601 time the post is scheduled for. |
| status | string|null | – | draft, scheduled, publishing, processing, published, partial or failed. |
| threadMediaFiles | – | – | get_post and list_posts: the media the thread parts reference. Not included in mediaFiles. |
| threadParts | – | – | For a thread post: its parts, in order. |
| timezone | string|null | – | Time zone the schedule was set in. |
No examples provided.
update_rss_feed Update RSS feed ~303
Update an RSS autopost feed (partial update). Note: changing feedUrl re-baselines the feed — its check state resets and only items published after the change are posted, so the new feed's backlog is not flooded. Use this when the user wants to change, pause, or re-point an RSS autopost feed.
| Name | Type | Req | Description |
|---|---|---|---|
| channelIds | array | – | Replacement channel IDs (at least 1). |
| enabled | boolean | – | Enable or disable polling of this feed. |
| feedId | number | yes | The RSS feed ID to update. |
| feedUrl | string | – | New feed URL. Changing it re-baselines the feed (only items newer than the change are posted). |
| fieldMapping | – | – | New field mapping; pass null to clear back to the built-in default. |
| mode | string | – | draft = new items become drafts for review; publish = auto-published. |
| name | string | – | New feed name. |
| requireApproval | boolean | – | Hold items auto-published from this feed for team approval — each generated post lands with approvalStatus 'pending' and waits for approve_post. Only meaningful when mode is 'publish' (draft items ne… |
No output schema declared.
No examples provided.
update_schedule Update recurring schedule ~292
Update an existing recurring schedule. Can change name, content template, frequency/timing, timezone, media, or active status. The next run time is recomputed by the server when timing changes. Use this when the user wants to change a recurring schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| contentTemplate | string | – | New post content template. |
| dayOfMonth | number | – | New day of month (1-31) for monthly. |
| dayOfWeek | number | – | New day of week (0=Sunday..6=Saturday) for weekly/biweekly. |
| frequency | string | – | New frequency. |
| isActive | boolean | – | Enable or disable the schedule. |
| mediaFileIds | array | – | Replace the media file IDs used for generated posts. |
| name | string | – | New schedule name. |
| requireApproval | boolean | – | Hold every future occurrence this schedule generates for team approval — each generated post lands with approvalStatus 'pending' and does not publish until an approver releases it via approve_post. D… |
| scheduleId | number | yes | The schedule ID to update. |
| timeOfDay | string | – | New time of day, 24h "HH:MM". |
| timezone | string | – | New IANA timezone. |
No output schema declared.
No examples provided.
update_template Update post template ~67
Rename a template and/or replace its text (partial update — at least one field is required). Use this when the user wants to rename a template or change its text.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| name | string | – | – |
| templateId | number | yes | The template ID. |
No output schema declared.
No examples provided.
upload_media Upload media ~236
Upload a media file (image, video or document) from a URL or local file path. The file is stored in BulkPublish for use in posts. Supported formats: JPEG, PNG, WebP, GIF, MP4, MOV, WebM, and documents (PDF, Word .doc/.docx, PowerPoint .ppt/.pptx). Max 100MB. A document has no thumbnail or preview and can only be published to LinkedIn, as a `document` post. Provide either url OR filePath, not both. Returns the stored file under file, including file.id to pass in mediaFileIds on create_post. Use this when the user provides an image, video or document to attach to a post.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | A file provided by the chat host. Leave unset and use url otherwise. |
| filePath | string | – | Absolute path to a local file to upload (e.g. /Users/me/photo.png). |
| filename | string | – | Optional filename. If omitted, derived from the URL or file path. |
| url | string | – | Public URL of the media file to upload. |
| Name | Type | Req | Description |
|---|---|---|---|
| file | – | – | The stored media file. file.id is what mediaFileIds takes. |
| filename | string|null | – | – |
| id | number|string|null | – | – |
| mimeType | string|null | – | – |
| sizeBytes | number|string|null | – | – |
| url | string|null | – | – |
No examples provided.
view_analytics Analytics dashboard ~98
Open an interactive analytics dashboard for a date range — totals, status breakdown, per-platform stats, and daily post counts. Use this when the user wants an interactive analytics dashboard — prefer over get_analytics for a visual view.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date (ISO, e.g. 2025-01-01). Defaults to 30 days ago. |
| to | string | – | End date (ISO). Defaults to today. |
| Name | Type | Req | Description |
|---|---|---|---|
| from | string|null | – | Start of the date range shown. |
| summary | – | – | Post totals for the range, by status, by platform and by day. |
| to | string|null | – | End of the date range shown. |
No examples provided.
view_channels Channels ~57
Open an interactive view of connected social channels with platform, account, and connection/token status. Returns the same list: channelId, platform, accountName, active and status. Use this when the user wants an interactive view of their connected channels.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | – | – | The connected accounts shown, each with its connection status. |
No examples provided.
view_media Media library ~49
Open an interactive gallery of uploaded media files with thumbnails and metadata. Use this when the user wants to browse their media library visually.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max items to show (default 30). |
| Name | Type | Req | Description |
|---|---|---|---|
| media | – | – | The media files shown. |
No examples provided.
view_posts Posts ~79
Open an interactive list of posts with their status, schedule, and channels. Optionally filter by status. Use this when the user wants to see their posts as an interactive dashboard — prefer over list_posts for a visual view.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max posts to show (default 20). |
| status | string | – | Filter by post status. |
| Name | Type | Req | Description |
|---|---|---|---|
| posts | – | – | The posts shown, each with its status, times and platforms. |
| total | number|string|null | – | Posts matching the filter. |
No examples provided.
view_quota Account usage ~45
Open an interactive view of current account usage — daily/monthly post counts, channel counts, and media storage. Use this when the user wants a visual view of their plan usage.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| usage | – | – | – |
No examples provided.
How do I install the BulkPublish MCP server?
BulkPublish runs locally as an npm package, launched with npx -y @bulkpublish/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @bulkpublish/mcp-server
claude mcp add azeemkafridi-bulkpublish -- npx -y @bulkpublish/mcp-server
What is the BulkPublish MCP server?
BulkPublish is an MCP server listed in the public MCP registry as io.github.azeemkafridi/bulkpublish. Schedule, cross-post, and analyze social media posts across 15 platforms from AI agents. This page covers its npm package (@bulkpublish/mcp-server).
Is the BulkPublish MCP server safe to use?
BulkPublish scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BulkPublish MCP server expose?
BulkPublish exposes 80 tools: list_channels, list_platforms, create_post, list_posts, get_post, and 75 more. Their descriptions and schemas cost roughly 14,170 tokens of context every time the server is loaded.
Is the BulkPublish MCP server still maintained?
BulkPublish is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the BulkPublish MCP server under?
BulkPublish declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the BulkPublish MCP server?
VerifyMCP ran 17 checks on BulkPublish, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.