Ad Copy Ai tools for AI agents. Capabilities: generate ad copy, generate variants, create campaign. Built by MEOK AI Labs.
from $12/mo
Nothing to run from here
Bulkpublish is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Model Context Protocol server for BulkPublish — lets AI assistants manage social media posts, channels, media, and analytics.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @bulkpublish/mcp-server
# 2 — ask your agent something
> Model Context Protocol server for BulkPublish — lets AI assistants manage social media posts, channels, media, and analytics.
Bulkpublish is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
BUAll 1 server
@bulkpublish1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Bulkpublish as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add bulkpublish-mcp -- npx -y @bulkpublish/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
45 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all connected social media channels (X/Twitter, Instagram, LinkedIn, Facebook, TikTok, etc.). Returns channel ID, platform, account name, and token status.
Takes no parameters.
Example callreturns →
List every social platform BulkPublish supports and whether it is currently available.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get a single post by ID with full details including platform statuses, labels, media files, recurring schedule info, and metrics.
Takes no parameters.
Example callreturns →
Publish a draft or scheduled post immediately. The post will be queued for publishing to all its target channels.
Takes no parameters.
Example callreturns →
Retry publishing a failed or partially failed post. Only retries the platforms that failed, not the ones that already succeeded.
Takes no parameters.
Example callreturns →
Approve a post awaiting team approval. Requires a role with post:approve (owner, admin, approver).
Takes no parameters.
Example callreturns →
Reject a post awaiting team approval. Requires a role with post:approve.
Takes no parameters.
Example callreturns →
Upload a media file (image or video) 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. Max 100MB. Provide either url OR filePath, not both.
Takes no parameters.
Example callreturns →
List uploaded media files with optional search and pagination. Returns file metadata including URLs, dimensions, and labels.
Takes no parameters.
Example callreturns →
Get an analytics summary for a date range. Returns total posts, status breakdown (published, failed, scheduled), per-platform stats, and daily post counts.
Takes no parameters.
Example callreturns →
List all labels available for tagging posts and media.
Takes no parameters.
Example callreturns →
Create a new label for organizing posts or media files.
Takes no parameters.
Example callreturns →
Check current account usage. Returns daily/monthly post counts, scheduled post counts, channel counts, and media storage usage.
Takes no parameters.
Example callreturns →
Update an existing post. Can change content, schedule, media, labels, status, and platform-specific settings.
Takes no parameters.
Example callreturns →
Delete a post by ID. Only draft and failed posts can be deleted.
Takes no parameters.
Example callreturns →
Get engagement metrics for a published post. Returns likes, comments, shares, impressions, and other platform-specific metrics. IMPORTANT: every platform entry carries
Takes no parameters.
Example callreturns →
Publish a post as a story on Facebook or Instagram.
Takes no parameters.
Example callreturns →
Perform a bulk action on multiple posts. Supports deleting, retrying, or rescheduling multiple posts at once.
Takes no parameters.
Example callreturns →
Get the organization
Takes no parameters.
Example callreturns →
Check the health status of a connected channel. Returns token validity, connection status, and any issues.
Takes no parameters.
Example callreturns →
Get platform-specific options for a channel (e.g. available post types, character limits, media requirements).
Takes no parameters.
Example callreturns →
Search for @mention suggestions on a channel. Useful for finding users/pages to mention in posts.
Takes no parameters.
Example callreturns →
Get details of a single media file by ID. Returns metadata, URL, dimensions, and labels.
Takes no parameters.
Example callreturns →
Delete a media file by ID. Removes the file from storage and detaches it from any posts.
Takes no parameters.
Example callreturns →
Update an existing label
Takes no parameters.
Example callreturns →
Delete a label by ID. Removes the label from all associated posts or media.
Takes no parameters.
Example callreturns →
List all recurring post schedules. Returns schedule name, cron expression, target channels, and active status.
Takes no parameters.
Example callreturns →
Create a new recurring post schedule. Posts are automatically created and published on the chosen frequency.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Delete a recurring schedule by ID. Stops all future posts from this schedule.
Takes no parameters.
Example callreturns →
List saved channel sets — named channel groupings for one-click multi-channel targeting. Returns id, name, and channelIds for each set, ordered by name.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Update a channel set
Takes no parameters.
Example callreturns →
Delete a channel set by ID. Does not affect the channels themselves.
Takes no parameters.
Example callreturns →
List RSS autopost feeds — RSS/Atom feeds polled every 15 minutes 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.
Takes no parameters.
Example callreturns →
Add an RSS autopost feed. The feed is polled every 15 minutes and new items become posts on the chosen channels. The server validates that feedUrl is a reachable public RSS 2.0 or Atom feed. An organization can have up to 20 feeds.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
Delete an RSS autopost feed by ID. Stops polling; already-created posts are kept.
Takes no parameters.
Example callreturns →
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 presigned PUT URL per part (valid 3600s). PUT each 10MB slice to its URL, collect each response
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Abort an in-progress chunked upload and free its stored parts.
Takes no parameters.
Example callreturns →
Reserve a presigned R2 upload URL for a direct browser upload (used by the composer UI). For scripted uploads use upload_media instead.
Takes no parameters.
Example callreturns →
Record an uploaded R2 object as a media file after the browser PUT (pairs with create_media_upload; used by the composer UI).
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Bulkpublish costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 1.15.0 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digestfbdb96b022dd4c4bb7dbda9f911d2bd7b862cf0fb2b1636dac2351ab27f9ab8d
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (45 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_channels | no tags | |
| list_platforms | no tags | |
| create_post | no tags | |
| list_posts | no tags | |
| get_post | no tags | |
| publish_post | no tags | |
| retry_post | no tags | |
| approve_post | no tags | |
| reject_post | no tags | |
| upload_media | no tags | |
| list_media | no tags | |
| get_analytics | no tags | |
| list_labels | no tags | |
| create_label | no tags | |
| get_quota_usage | no tags | |
| update_post | no tags | |
| delete_post | no tags | |
| get_post_metrics | no tags | |
| publish_story | no tags | |
| bulk_posts | no tags | |
| get_queue_slot | no tags | |
| get_channel_health | no tags | |
| get_channel_options | no tags | |
| search_mentions | no tags | |
| get_media | no tags | |
| delete_media | no tags | |
| update_label | no tags | |
| delete_label | no tags | |
| list_schedules | no tags | |
| create_schedule | no tags | |
| update_schedule | no tags | |
| delete_schedule | no tags | |
| list_channel_sets | no tags | |
| create_channel_set | no tags | |
| update_channel_set | no tags | |
| delete_channel_set | no tags | |
| list_rss_feeds | untrusted-input | |
| create_rss_feed | untrusted-input | |
| update_rss_feed | untrusted-input | |
| delete_rss_feed | untrusted-input | |
| create_multipart_upload | no tags | |
| complete_multipart_upload | no tags | |
| abort_multipart_upload | no tags | |
| create_media_upload | no tags | |
| finalize_media_upload | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestfbdb96b022dd4c4b
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.15.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.15.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Bulkpublish in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.