Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BulkPublish

NPM · @BULKPUBLISH/MCP-SERVER · 2 COMPONENTS

Schedule, cross-post, and analyze social media posts across 15 platforms from AI agents.

0 this week 85 Trust /100

Last scanned (22 hours ago)

Scores higher than 77% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

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
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
What we tested

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 →

Changelog

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.

Diagnostics

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 →

MCP tools · 80 exposed · ~14,170 tokens

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 →

Tool Tokens
abort_multipart_upload ~109

Abort an in-progress chunked upload and permanently free its stored parts. Use only when the upload should be cancelled; do not use this after all parts have been uploaded if you intend to complete the upload. This action cannot be undone. Use this when a chunked upload should be cancelled and its stored parts freed.

NameTypeReqDescription
r2KeystringyesThe r2Key returned by create_multipart_upload.
uploadIdstringyesThe uploadId returned by create_multipart_upload.

No output schema declared.

No examples provided.

approve_post ~469

Approve a post awaiting team approval. Requires a role with post:approve (owner, admin, approver). Releases a post with approvalStatus 'pending': it publishes at its scheduled time, or immediately if that time passed less than 15 minutes ago. If the scheduled time passed more than 15 minutes ago, whenLate decides: 'publish' publishes it immediately (status 'publishing'); 'hold' approves it but returns it with status 'draft' (approvalStatus 'approved', scheduledAt unchanged) and the author is notified to choose a new time — tell the user it needs rescheduling. When whenLate is omitted it follows the post's publishWhenApproved: true means 'publish', false means 'hold'. If a late post's publishWhenApproved is false, ask the user whether to publish now or send it back before approving. The author is notified in-app either way. Approving sets publishWhenApproved to false. Pass the updatedAt of the version you showed the user as ifUnmodifiedSince, so an edit made since then is not approved unseen. Errors: 400 if the post is not awaiting approval, whenLate is not 'publish'/'hold' 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 approve a post awaiting team approval.

NameTypeReqDescription
ifUnmodifiedSincestring–Optional. The post's updatedAt (ISO 8601) as you last loaded it with get_post. The approval only lands on that version; if the post changed since, nothing is written and the call returns 409.
postIdnumberyesThe post ID to approve.
whenLatestring–Optional. Only matters when the post's scheduled time passed more than 15 minutes ago: 'publish' = publish now, 'hold' = approve and return it to draft for the author to pick a new time. Defaults to…
NameTypeReqDescription
approvalStatusstring|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.
contentstring|null–The post's main text.
createdAtstring|null–ISO 8601 time the post was created.
idnumber|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.
publishedAtstring|null–ISO 8601 time the post was published.
recurringSchedule––get_post and list_posts: the repeat schedule the post belongs to, or null.
scheduledAtstring|null–ISO 8601 time the post is scheduled for.
statusstring|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.
timezonestring|null–Time zone the schedule was set in.

No examples provided.

bulk_posts ~130

Perform a bulk action on multiple posts. Supports deleting, retrying, or rescheduling up to 100 posts at once. Use this when the user wants to delete, retry, or reschedule many posts in a single request.

NameTypeReqDescription
actionstringyesBulk action: "delete", "retry", or "reschedule".
postIdsarrayyesArray of post IDs to perform the action on, at most 100 per call. Split a larger selection into batches of 100.
scheduledAtstring–New ISO 8601 datetime. Required when action is "reschedule".

No output schema declared.

No examples provided.

complete_multipart_upload ~203

Complete a chunked upload: the server assembles the uploaded parts, verifies the stored object (existence, size, magic bytes, storage quota) and records the media file — same verification and response shape as finalize_media_upload. A failed assembly automatically aborts the upload. Use this when all parts of a chunked upload are PUT and their ETags collected.

NameTypeReqDescription
durationnumber–Duration in seconds (video).
fileNamestringyesOriginal file name.
heightnumber–Pixel height (images/video).
mimeTypestringyesFile MIME type.
partsarrayyesEvery uploaded part with its ETag.
r2KeystringyesThe r2Key returned by create_multipart_upload.
sizeBytesnumberyesFile size in bytes.
uploadIdstringyesThe uploadId returned by create_multipart_upload.
widthnumber–Pixel width (images/video).

No output schema declared.

No examples provided.

compose_post ~99

Open an interactive composer to draft, schedule or publish a social media post. Shows the user's connected channels to pick from and pre-fills any provided text. The user finishes in the UI; on submit it creates the post via create_post. Use this when the user wants to compose a post interactively in a UI — prefer this over create_post when they'd review before posting.

NameTypeReqDescription
contentstring–Optional initial text to pre-fill the composer with.
NameTypeReqDescription
channels––The active connected accounts offered in the composer.
media––Recent media files offered for attaching.

No examples provided.

create_calendar_note ~111

Pin a note to a day on the content calendar. Not a post: nothing is published. A workspace may keep up to 5000 notes (400 LIMIT_REACHED beyond that). Use this when the user wants to pin a note, reminder or campaign marker to a calendar day without creating a post.

NameTypeReqDescription
bodystringyesNote text.
colorstring–Six-digit hex colour, default #F59E0B.
datestringyesCalendar date, YYYY-MM-DD.

No output schema declared.

No examples provided.

create_channel_set ~109

Create a channel set — a saved channel grouping for one-click multi-channel targeting. Names are unique per organization (a duplicate fails with a 409, code DUPLICATE_NAME); an organization can have up to 50 sets. Use this when the user wants to save a group of channels for one-click targeting.

NameTypeReqDescription
channelIdsarrayyesIDs of channels in your organization (at least 1).
namestringyesSet name (max 100 chars, unique per organization).

No output schema declared.

No examples provided.

create_client_connect_link ~333

Create a one-time link a client can open, with no BulkPublish account of their own, to connect one of their platform accounts into this organization. The client picks which platform when they open it — only these are supported (telegram asks for a bot token instead of a plain sign-in, and stays a manual connect by your own team): bluesky, facebook, instagram, x, tiktok, youtube, threads, pinterest, gmb, linkedin, mastodon, discord, tumblr, snapchat. For bluesky, the client enters their handle and approves access on Bluesky; they are never asked for a password. For facebook, the client signs in to Facebook and then picks which one of their Pages to connect. For mastodon, they first enter the address of the server their account is on. Expires in 7 days or the moment an account is connected through it, whichever comes first — creating again always makes a new link. Returns { clientConnectLink, url }. The url is shown only this once: it cannot be recovered later, so save it when you get it. 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 (an agency) wants a client to connect their own platform account without giving the agency their login, and without the client needing a BulkPublish account.

NameTypeReqDescription
namestringyesYour own label for the client (e.g. "Acme Corp"). Never shown to the client — only applied to the resulting channel so you can tell whose account it is.

No output schema declared.

No examples provided.

create_hashtag_group ~101

Save a named set of hashtags (1-30) for reuse in posts. Hashtags may be given with or without the leading '#'; letters, digits and underscores only. Up to 100 groups per organization. Use this when the user wants to save a set of hashtags for reuse.

NameTypeReqDescription
hashtagsarrayyesHashtags, e.g. ["launch", "#newproduct"].
namestringyesGroup name, unique per organization.

No output schema declared.

No examples provided.

create_label ~82

Create a new label for organizing posts or media files. Use this when the user wants a new label/tag.

NameTypeReqDescription
colorstring–Hex color code (e.g. "#6366f1"). Defaults to indigo.
namestringyesLabel name.
typestring–Label type: "post" (default) or "media".

No output schema declared.

No examples provided.

create_media_upload ~91

Reserve a one-time upload link for a direct browser upload (used by the composer UI). For scripted uploads use upload_media instead. Use this when you need an upload link for a large direct upload (advanced; prefer upload_media for normal files).

NameTypeReqDescription
contentTypestringyesFile MIME type, e.g. image/png or video/mp4.
sizeBytesnumberyesFile size in bytes.
NameTypeReqDescription
expiresInnumber|string|null–Seconds until uploadUrl stops working.
r2Keystring|null–Reference for this upload; pass it to finalize_media_upload.
uploadUrlstring|null–Address to send the file's bytes to with an HTTP PUT.

No examples provided.

create_multipart_upload ~193

Start a chunked (multipart) direct-to-storage upload for large media — videos up to 1GB, images up to 100MB. Returns r2Key, uploadId, the fixed partSize (10485760 bytes = 10MB), and one PUT URL per part (valid 3600s). PUT each 10MB slice to its URL, collect each response's ETag header, then call complete_multipart_upload. For ordinary files prefer upload_media. Use this when a file is too large for a single upload (e.g. a video over 100MB, up to 1GB) and must be sent in 10MB chunks.

NameTypeReqDescription
contentTypestringyesFile MIME type, e.g. video/mp4 or image/png.
sizeBytesnumberyesExact file size in bytes. Videos up to 1GB; images up to 100MB.

No output schema declared.

No examples provided.

create_post ~1,369

Create a new social media post. Can be saved as a draft or scheduled for a specific time. Supports platform-specific content overrides, media attachments, labels, and thread format. IMPORTANT: YouTube requires a video. TikTok requires a video, or 1 to 35 images with postTypeOverrides.tiktok = "photo_slideshow". Do not include either on a text-only post. Instagram defaults to feed_photo — set postTypeOverrides for video content (reel, feed_video). Use this when the user wants to draft or schedule one new post. It never publishes immediately; publish_post does that.

NameTypeReqDescription
autoPlugEnabledboolean–Optional (default false). Automatically post a follow-up comment (autoPlugText) once the published post reaches autoPlugThreshold likes.
autoPlugTextstring–Optional. The follow-up comment text for auto-plug.
autoPlugThresholdinteger–Optional (default 50). Likes needed before the auto-plug comment is posted.
autoRepostEnabledboolean–Optional (default false). Automatically repost/reshare the post once it reaches autoRepostThreshold likes.
autoRepostThresholdinteger–Optional (default 100). Likes needed before the post is reposted.
channelsarrayyesArray of channels to post to. Get channel IDs from list_channels.
contentstring–The post text content. Optional — defaults to empty for media-only posts. LinkedIn mentions: write @[Display Name](urn:li:organization:ID) for a Page or @[Display Name](urn:li:person:ID) for a person…
deleteMediaAfterPublishboolean–Optional (default false: media is kept in the library). Set true to delete the attached media once every channel has published, so it stops counting toward the storage limit. Forced to false when rep…
labelsarray–Array of label IDs to tag the post with. Label IDs come from list_labels.
linkTrackingOverrideboolean|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/omitted (the de…
mediaFileIdsarray–Array of media file IDs to attach. Upload media first with upload_media.
platformContentobject–Per-platform content overrides, e.g. { "x": "Short tweet", "linkedin": "Longer LinkedIn post" }.
platformSpecificobject–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…
platformThreadPartsobject–Optional per-platform thread overrides, keyed by platform, e.g. { "x": [{ "content": "Part 1" }, { "content": "Part 2" }] }. Part content must be a plain string.
postFormatstring–Post format. "post" (default), "video", "reel", "story", "carousel", or "thread" for multi-part threads.
postTypeOverridesobject–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:…
publishWhenApprovedboolean–Optional (default false). Set true on a post that waits for approval when it should go out as soon as it is approved, even if that is after its scheduled time. This is how someone who needs approval…
repeatScheduleobject–Optional. Make this a repeating post: it is re-published on this cadence. Media on a repeating post is always kept (deleteMediaAfterPublish is forced to false).
requestApprovalboolean–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…
scheduledAtstring–ISO 8601 datetime for scheduling (e.g. 2025-01-15T10:00:00Z). Required when status is scheduled.
statusstring–Post status. "draft" (default) or "scheduled".
threadPartsarray–Thread parts array. Required when postFormat is thread (min 2 parts). EVERY part is measured against the character limit of every platform the post targets, not only the first — an over-long part is…
timezonestring–Timezone for scheduling (e.g. "America/New_York"). Defaults to UTC.
NameTypeReqDescription
approvalStatusstring|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.
contentstring|null–The post's main text.
createdAtstring|null–ISO 8601 time the post was created.
idnumber|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.
publishedAtstring|null–ISO 8601 time the post was published.
recurringSchedule––get_post and list_posts: the repeat schedule the post belongs to, or null.
scheduledAtstring|null–ISO 8601 time the post is scheduled for.
statusstring|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.
timezonestring|null–Time zone the schedule was set in.

No examples provided.

create_review_link ~195

Create a read-only review link covering several posts at once — the multi-post counterpart of share_post. Anyone with the link can open it without signing in. Every postId must belong to the organization. Unlike share_post this is never regenerated in place: each call mints a new link and a new token, even for the same posts. Returns { reviewLink, url }. 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 one link a client can open to review several posts at once, e.g. a week's worth of scheduled content, instead of sharing each post separately.

NameTypeReqDescription
namestring–Optional label shown only to your team (e.g. the client's name) — never shown on the public page.
postIdsarrayyesPost IDs to cover, up to 50 per link.

No output schema declared.

No examples provided.

create_rss_feed ~352

Add an RSS autopost feed. The feed is checked on a schedule set by the plan (every 60 minutes on Free and Lifetime, 30 on Pro, 15 on Business) and new items become posts on the chosen channels. The server validates that feedUrl is a reachable public RSS 2.0 or Atom feed. The number of feeds is capped by plan (Free 1, Lifetime 3, Pro 10, Business 50); one more is refused with 403 QUOTA_EXCEEDED. mode 'publish' needs a paid plan or Lifetime (403 FEATURE_DISABLED on Free). Use this when the user wants new items from an RSS/Atom feed to become posts automatically.

NameTypeReqDescription
channelIdsarrayyesIDs of channels new items are posted to (at least 1).
feedUrlstringyesPublic RSS 2.0 or Atom feed URL.
fieldMappingobject–Field mapping controlling how each feed item becomes a post.
modestring–draft = new items become draft posts for review (the default); publish = auto-published.
namestringyesFeed name (max 100 chars).
requireApprovalboolean–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.

create_schedule ~337

Create a new recurring post schedule. Posts are automatically created and published on the chosen frequency. The schedule is visible in the web app (Repeat Posts page, with upcoming runs on the Calendar); a post record exists only once an occurrence fires, carrying recurringScheduleId. Use this when the user wants a recurring posting schedule.

NameTypeReqDescription
channelIdsarrayyesArray of channel IDs to post to.
contentTemplatestring–Post content template. Defaults to empty.
dayOfMonthnumber–Day of month (1-31). Required for monthly.
dayOfWeeknumber–Day of week (0=Sunday..6=Saturday). Required for weekly/biweekly.
frequencystringyesHow often the schedule runs.
isActiveboolean–Whether the schedule starts active. Defaults to true.
mediaFileIdsarray–Media file IDs re-used for every generated post.
namestringyesSchedule name.
requireApprovalboolean–Hold every 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. Defaults…
timeOfDaystringyesTime of day to post, 24h "HH:MM" (e.g. "09:00").
timezonestring–IANA timezone (e.g. "America/New_York"). Defaults to UTC.

No output schema declared.

No examples provided.

create_template ~127

Save post text as a named template for reuse (text only; media and channels belong to the post). Up to 200 per organization per kind (captions and first-comment snippets each have their own 200); names are unique per kind, so a caption and a first-comment snippet can share a name. Use this when the user wants to save post text for reuse.

NameTypeReqDescription
contentstringyesTemplate text.
kindstring–What the text is for: a post caption, or a first-comment reply. Defaults to caption.
namestringyesTemplate name.

No output schema declared.

No examples provided.

delete_calendar_note ~39

Delete a calendar note. Use this when the user wants to remove a calendar note.

NameTypeReqDescription
noteIdnumberyesThe note ID to delete.

No output schema declared.

No examples provided.

delete_channel_set ~50

Delete a channel set by ID. Does not affect the channels themselves. Use this when the user wants to remove a saved channel set.

NameTypeReqDescription
setIdnumberyesThe channel set ID to delete.

No output schema declared.

No examples provided.

delete_client_connect_link ~104

Revoke a client-connect link before it has been used. Idempotent; an account it already connected is untouched. 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 client-connect link from working before it has been used. Any account it already connected is unaffected.

NameTypeReqDescription
clientConnectLinkIdnumberyesThe client-connect link ID.

No output schema declared.

No examples provided.

delete_hashtag_group ~52

Delete a saved hashtag group. Posts that already contain its hashtags are untouched. Use this when the user wants to remove a saved hashtag group.

NameTypeReqDescription
groupIdnumberyesThe hashtag group ID to delete.

No output schema declared.

No examples provided.

delete_label ~48

Delete a label by ID. Removes the label from all associated posts or media. Use this when the user wants to delete a label.

NameTypeReqDescription
labelIdnumberyesThe label ID to delete.

No output schema declared.

No examples provided.

delete_media ~54

Delete a media file by ID. Removes the file from storage and detaches it from any posts. Use this when the user wants to delete a media file.

NameTypeReqDescription
mediaIdnumberyesThe media file ID to delete.

No output schema declared.

No examples provided.

delete_post ~111

Delete a post by ID. Any post can be deleted except one that is publishing right now (409 PUBLISH_IN_PROGRESS; wait for it to finish). Deleting removes the post from BulkPublish only: a published post stays live on the platforms, and its stats here are removed with it. Deleting a post made by a repeat schedule also switches that schedule off. Use this when the user wants to permanently remove a post.

NameTypeReqDescription
postIdnumberyesThe post ID to delete, from list_posts.
NameTypeReqDescription
successboolean|null–true when the post was deleted.

No examples provided.

delete_review_link ~85

Revoke a client review link. The posts it covered are untouched. 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 batch review link from working. The posts it covered are unaffected.

NameTypeReqDescription
reviewLinkIdnumberyesThe review link ID.

No output schema declared.

No examples provided.

delete_rss_feed ~58

Delete an RSS autopost feed by ID. Stops polling; already-created posts are kept. Use this when the user wants to stop and remove an RSS autopost feed.

NameTypeReqDescription
feedIdnumberyesThe RSS feed ID to delete.

No output schema declared.

No examples provided.

delete_schedule ~50

Delete a recurring schedule by ID. Stops all future posts from this schedule. Use this when the user wants to stop and delete a recurring schedule.

NameTypeReqDescription
scheduleIdnumberyesThe schedule ID to delete.

No output schema declared.

No examples provided.

delete_template ~39

Delete a saved post template. Use this when the user wants to remove a saved template.

NameTypeReqDescription
templateIdnumberyesThe template ID to delete.

No output schema declared.

No examples provided.

finalize_media_upload ~154

Record an uploaded file as a media file after the browser PUT (pairs with create_media_upload; used by the composer UI). Returns the new media file, including the id to pass in mediaFileIds. Use this when a direct upload finished and the file must be registered (advanced).

NameTypeReqDescription
durationnumber–Duration in seconds (video).
fileNamestringyesOriginal file name.
heightnumber–Pixel height (images/video).
mimeTypestringyesFile MIME type.
r2KeystringyesThe r2Key returned by create_media_upload.
sizeBytesnumberyesFile size in bytes.
widthnumber–Pixel width (images/video).
NameTypeReqDescription
file––The new media file. Its id is what mediaFileIds takes.

No examples provided.

get_analytics ~341

Get an analytics summary for a date range. Returns total posts, status breakdown (published, failed, scheduled), per-platform stats, and daily post counts. Optional filters narrow every figure to matching posts; `compare` adds the equal-length previous window under `previous` (available for windows of 15 days or fewer — the 30-day statistics-retention cap applies). Use this when the user asks how their content performed overall, across channels and over a date range.

NameTypeReqDescription
channelIdsstring–Comma-separated channel ids to include, e.g. "12,15". Ids come from list_channels.
compareboolean–Also return the previous equal-length window as `previous` / `previousWindow`.
fromstringyesStart date in ISO format (e.g. 2025-01-01).
labelIdsstring–Comma-separated label ids (from list_labels); a post matches when it carries ANY of them.
mediaTypestring–By the post's first media file: text (no media), image or video.
platformsstring–Comma-separated platform keys to include, e.g. "x,linkedin".
postFormatstring–Only single posts or only threads.
tostringyesEnd date in ISO format (e.g. 2025-01-31).
tzstring–IANA timezone (e.g. "Asia/Karachi") that sets where each day starts and ends and how daily counts are grouped. Defaults to UTC; pass the user's zone so 'today' and daily figures match their calendar.
NameTypeReqDescription
byDay––Posts that went out per day: { date, count, platforms }.
byPlatform––Per platform: destinations in the range as { total, published, failed }.
failednumber|string|null–How many failed.
fromstring|null–Start of the date range.
partialnumber|string|null–How many published to only some destinations.
previous––With compare: totalPosts, published, failed, scheduled and partial for the previous window; null when that window is not available.
previousWindow––With compare: { from, to, days, available } for the previous window.
publishednumber|string|null–How many of them published.
publishedTimes––Not filled in by this tool.
schedulednumber|string|null–Posts currently waiting to publish, whatever the date range.
tostring|null–End of the date range.
totalPostsnumber|string|null–Posts in the date range.

No examples provided.

get_channel_health ~59

Check the health status of a connected channel. Returns token validity, connection status, and any issues. Use this when the user asks whether a channel's connection/token is healthy.

NameTypeReqDescription
channelIdnumberyesThe channel ID to check health for.

No output schema declared.

No examples provided.

get_channel_options ~220

Get platform-specific options for a channel: Pinterest boards (or, with boardId, that board's sections), YouTube playlists, Tumblr blogs, Discord text channels, Threads location search. Returns type (which kind of option came back) and items, each with an id and a name; a TikTok channel returns info instead of items. Use this when you need a platform's valid post types before creating a post for it.

NameTypeReqDescription
boardIdstring–Pinterest only: the board's ID, digits only, sent as a string (from this tool's boards list). Returns that board's sections ({ type: 'sections', items: [{ id, name }] }) for platformSpecific.pinteres…
channelIdnumberyesThe channel ID to get options for, from list_channels.
qstring–Search term. Threads: place search for platformSpecific.threads.locationId (returns { unavailable: true } until the channel has granted location tagging).
NameTypeReqDescription
info––Extra details for types that are not a list, such as creator_info.
items––The options of that type. Use an item's id in the matching platformSpecific field.
typestring|null–boards, sections, playlists, blogs, channels, locations or creator_info.
unavailableboolean|string|null–Set when the options cannot be offered for this channel.

No examples provided.

get_conversation ~119

Get the messages of one Inbox conversation: the newest 500, oldest first, each with its direction (in from the other person, out sent by the workspace), text, attachments and time. Reading does not mark the conversation read. 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 read one Inbox conversation in full.

NameTypeReqDescription
conversationIdnumberyesThe conversation id from list_conversations.
NameTypeReqDescription
conversationIdnumber|string|null–The conversation these messages belong to.
messages–––

No examples provided.

get_media ~53

Get details of a single media file by ID. Returns metadata, URL, dimensions, and labels. Use this when the user references one specific media file by ID.

NameTypeReqDescription
mediaIdnumberyesThe media file ID.

No output schema declared.

No examples provided.

get_post ~100

Get a single post by ID with full details including platform statuses, labels, media files, recurring schedule info, and metrics. For a thread post, `threadParts` holds the parts and `threadMediaFiles` resolves the media they reference: that media is NOT in `mediaFiles`, which carries only the media on the post itself. Use this when the user references one specific post by its ID.

NameTypeReqDescription
postIdnumberyesThe post ID.
NameTypeReqDescription
approvalStatusstring|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.
contentstring|null–The post's main text.
createdAtstring|null–ISO 8601 time the post was created.
idnumber|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.
publishedAtstring|null–ISO 8601 time the post was published.
recurringSchedule––get_post and list_posts: the repeat schedule the post belongs to, or null.
scheduledAtstring|null–ISO 8601 time the post is scheduled for.
statusstring|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.
timezonestring|null–Time zone the schedule was set in.

No examples provided.

get_post_metrics ~351

Get engagement metrics for a published post. Returns likes, comments, shares, impressions, and other platform-specific metrics. IMPORTANT: every platform entry carries `metricsSupported` and `supportedMetrics` — a metric key NOT in `supportedMetrics` is stored as 0 because that platform's API has no such field, so report it as unavailable rather than as zero. X reports impressions/likes/comments/shares/saves (bookmarks); Bluesky and Mastodon report no impressions; Pinterest reports no reach; YouTube reports no shares or reach; Discord reports likes (reaction counts) and comments (thread replies); TikTok reports reach, saves and clicks only for accounts that have granted TikTok insights. An Instagram story reports only impressions, reach and comments (story replies). Google Business, Telegram, Tumblr and LinkedIn personal profiles report nothing readable at all, and an X post comes back with `metricsSupported: false` until its channel turns on X metrics sync. Each platform entry also carries `linkClicks` (summed in `totals.linkClicks`): clicks on bulkpubli.sh short links in this post, measured by BulkPublish rather than reported by the platform. It sits OUTSIDE `latest` and is distinct from the platform's own `clicks` — one visit can register in both, so never add them together. It is therefore available even for the platforms that report nothing, and `supportedMetrics` always includes it. Bot and link-preview traffic is excluded; it is 0 for organizations without Link Tracking enabled. Use this when the user asks how a specific post performed (likes, views, engagement).

NameTypeReqDescription
postIdnumberyesThe post ID to get metrics for.
NameTypeReqDescription
platforms––One entry per destination with its own figures, plus metricsSupported and supportedMetrics.
postIdnumber|string|null–The post these metrics belong to.
totals––Sums across destinations: impressions, likes, comments, shares, clicks, videoViews and linkClicks.

No examples provided.

get_queue_slot ~176

Get the organization's next available queue slot. Useful for finding the next optimal scheduling time. Returns scheduledAt (an ISO timestamp) and dayLabel (a readable day). Use this when the user asks when the next available scheduling slot is, or wants a post moved to the top or bottom of the queue (then update_post with the returned scheduledAt).

NameTypeReqDescription
excludePostIdnumber–When the slot is for rescheduling an existing post, its ID — so its current slot is not counted as booked.
positionstring–"next" (default): the next free slot. "end": the slot after the last pending scheduled post, i.e. the bottom of the queue.
timezonestring–IANA timezone for the slot calculation (e.g. "America/New_York"). Defaults to UTC.
NameTypeReqDescription
dayLabelstring|null–Human label, e.g. "Today" or "Wed, Feb 14".
scheduledAtstring|null–ISO timestamp of the next free slot.

No examples provided.

get_quota_usage ~120

Check current account usage. Returns daily/monthly post counts, scheduled post counts, channel counts, and media storage usage. Also returns channelSlots — purchased extra channel slots ($2.99/month each, available on every plan; a seat-based subscription whose unused slots are auto-canceled before renewal): each active slot raises the effective total channel limit by one and allows one channel above the per-platform cap; per-slot autoRenews says whether it renews or lapses at expiresAt. Use this when the user asks about plan limits or current usage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_calendar_notes ~116

List calendar notes (free text pinned to a day — campaigns, holidays, 'no posts this week'; they never publish) in a date range of at most a year. Returns at most 1000 notes, earliest first; narrow the range to see more. Use this when the user asks what is noted on the content calendar for a period (campaigns, holidays, reminders).

NameTypeReqDescription
fromstringyesStart date, YYYY-MM-DD (inclusive).
tostringyesEnd date, YYYY-MM-DD (inclusive).

No output schema declared.

No examples provided.

list_channel_sets ~55

List saved channel sets — named channel groupings for one-click multi-channel targeting. Returns id, name, and channelIds for each set, ordered by name. Use this when the user wants their saved channel groups (channel sets).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_channels ~127

List all connected social media channels (X/Twitter, Instagram, LinkedIn, Facebook, TikTok, etc.). Returns channel ID, platform, account name, and token status, plus a `capabilities` object saying whether the caller may create, publish or approve posts. Check that before attempting a write rather than discovering the permission from a 403. Use this when the user wants to see which social accounts are connected.

NameTypeReqDescription
activeboolean–Filter by active status. Defaults to true (only active channels). false also includes up to 100 disconnected channels, most recently updated first.
NameTypeReqDescription
capabilities––Whether the caller may create, publish or approve posts.
channels––Connected accounts. Each one's id is the channelId that create_post and update_post take.

No examples provided.

list_client_connect_links ~167

List the organization's client-connect links, newest first — one-time links a client can open, with no BulkPublish account, to connect their own platform account. Paged: returns { clientConnectLinks, page, limit, total }, 50 per page by default (max 100); `total` counts every link, so request the next page while page × limit < total. 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 see the client-connect links they have created and whether each has been used yet.

NameTypeReqDescription
limitnumber–Links per page (default 50, max 100).
pagenumber–Page number (default 1).

No output schema declared.

No examples provided.

list_conversations ~303

List Inbox conversations: direct messages, reviews and comment threads across the connected channels, newest activity first. Each conversation has its platform, kind (dm, review or comment), the other person, unread count, a preview of the last message, and canReply with replyNotice saying why a reply cannot be sent now. Internal team notes are not included. Results are paged: pass nextCursor back as cursor for the next 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 asks about their direct messages, reviews or comment threads, or what is waiting for a reply.

NameTypeReqDescription
assignedstring–me, unassigned, or a teammate's user id.
channelIdnumber–Only conversations on this connected account. Channel IDs come from list_channels.
cursorstring–nextCursor from the previous page.
kindstring–Only direct messages, reviews or comment threads. Omit for all.
limitnumber–Page size, 1 to 100 (default 50).
platformsarray–Only these platforms, e.g. ["instagram", "facebook"].
qstring–Search the person's name and handle and the message text (2 to 100 characters).
statusstring–open (default), archived or snoozed.
NameTypeReqDescription
conversations–––
nextCursorstring|null–Pass back as cursor for the next page; null on the last page.
offsetnumber|string|null–Where this page started when paging by position; 0 when paging by cursor.
totalnumber|string|null–How many conversations match the filters, across every page.

No examples provided.

list_hashtag_groups ~48

List the organization's saved hashtag groups — named sets of hashtags to drop into a post. Use this when the user wants their saved hashtag sets, or you need hashtags to add to a post.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_labels ~70

List the labels available for tagging posts and media, sorted by name. Returns at most 500 (the first 500 alphabetically). Use this when the user wants their post labels/tags.

NameTypeReqDescription
typestring–Filter by label type: "post" or "media". Returns all if omitted.
NameTypeReqDescription
items––The workspace's labels. id is what the labels input of create_post takes.

No examples provided.

list_media ~127

List uploaded media files with optional search and pagination. Returns file metadata including URLs, dimensions, and labels. Use this when the user wants a list of their uploaded media files.

NameTypeReqDescription
limitnumber–Results per page (default 20, max 100).
pagenumber–Page number (default 1).
searchstring–Search by filename.
typestring–Filter by media kind: image, video or document (PDF, Word and PowerPoint files). Omit for all files. The response's `total` counts matches across all pages.
NameTypeReqDescription
files––Media files on this page. id is what mediaFileIds takes.
limitnumber|string|null–Page size used.
pagenumber|string|null–This page's number.
totalnumber|string|null–Files matching the filters, across every page.

No examples provided.

list_platforms ~222

List every social platform BulkPublish supports and whether it is currently available. Check this before telling a user they can connect a platform or scheduling a post to one: a platform in state 'off' rejects post creation with a 403 PLATFORM_DISABLED error and holds any already-scheduled posts until it is re-enabled, and one in state 'connect_off' cannot accept new connections although existing channels keep publishing. Disabled platforms are still listed, with enabled=false and a reason. A platform may also carry a 'variants' object keyed by channel accountType for sub-platforms gated on their own: LinkedIn reports variants.organization for company pages (a separate LinkedIn app with its own review), while the platform-level state covers personal profiles — so pages can be paused while personal-profile posting is live. A variant is never more permissive than its parent, and when a variant blocks a write the 403 PLATFORM_DISABLED error carries an accountType field naming it. Use this when the user asks which platforms are supported or available, or a connect/publish attempt failed with PLATFORM_DISABLED.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_post_comments ~173

List the comments and reactions on one published post, per channel, read from each platform. Each channel's entry has its postPlatformId and each comment its id, which reply_to_comment and moderate_comment take, plus commentActions listing the actions that channel supports. Some platforms have no comment access (TikTok, Pinterest, Google Business, Telegram, Snapchat) and say so in a notice. Use this when the user asks who commented on one of their published posts, or needs a comment's id to reply to or moderate it.

NameTypeReqDescription
commentsLimitnumber–Max comments per channel (default 25, max 100).
postIdnumberyesThe post id.
reactionsLimitnumber–Max reactors (people who liked or reacted) per channel (default 25, max 100).
NameTypeReqDescription
platforms––One entry per destination: its comments and reactions under engagement, or error when they could not be read. postPlatformId identifies the destination when replying to or moderating a comment.
postIdnumber|string|null–The post these comments belong to.

No examples provided.

list_posts ~452

List posts with optional filters for status, search text, date range, channel, and label. Returns paginated results with platform statuses and metrics, ordered newest-first by publishedAt if the post is live, else scheduledAt, else createdAt. Use this when the user wants to browse, filter, or check the status of existing posts as raw data (not the visual dashboard).

NameTypeReqDescription
approvalStatusstring–Filter by team approval state (e.g. 'pending' for the approval queue).
assignedTostring–Filter by who the post is assigned to: a user id, 'me' for the caller, or 'unassigned'. Orthogonal to status — a post can be scheduled AND assigned.
channelIdnumber–Only posts on this channel. Channel IDs come from list_channels.
fromstring–Filter posts created on or after this ISO date.
labelIdnumber–Filter by a single label ID. Prefer labelIds.
labelIdsarray–Filter by several label IDs (from list_labels). Combined per labelMode.
labelModestring–How labelIds combine: 'or' (default) matches posts with any of them, 'and' only posts with all of them.
limitnumber–Results per page (default 20, max 500).
orderstring–Direction of the timeline sort (published, else due, else created). 'desc' is the default and returns the most recent first. Use 'asc' to read what is coming NEXT — with a limit, 'desc' returns the p…
pagenumber–Page number (default 1).
recurringboolean–Set true to return only posts attached to a recurring schedule.
scheduledFromstring–Filter posts scheduled on or after this ISO date.
scheduledTostring–Filter posts scheduled on or before this ISO date.
searchstring–Search post content (case-insensitive).
statusstring–Filter by post status.
tostring–Filter posts created on or before this ISO date.
NameTypeReqDescription
limitnumber|string|null–Page size used.
pagenumber|string|null–This page's number.
posts––The posts on this page.
totalnumber|string|null–Posts matching the filters, across every page.
totalPagesnumber|string|null–How many pages there are.

No examples provided.

list_review_links ~153

List the organization's client review links (batch review links), newest first, with how many posts each one covers. Paged: returns { reviewLinks, page, limit, total }, 50 per page by default (max 100); `total` counts every link, so request the next page while page × limit < total. 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 see the client review links they have created for batches of posts.

NameTypeReqDescription
limitnumber–Links per page (default 50, max 100).
pagenumber–Page number (default 1).

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add azeemkafridi-bulkpublish -- npx -y @bulkpublish/mcp-server
Common questions

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.