mcpbeat Sign in

Dropspace MCP Server

not responding

Dropspace is listed as active in the registry but did not answer our last check. 1 032 installs a week from npm. It exposes 40 tools.

Create, schedule, and publish social media launches across platforms, then read the analytics.

Installs per day peak 642 · avg 93 · +40% w/w
a month agotoday
Uptime history 20 hours of history · worst hour 0%
20 hours agonow
27.8%
Uptime 24h
20 of 72 checks
40
Tools
read from the server
557 ms
Response time
average over 24h
1 032
Installs / week
npm and PyPI

Dropspace does not always answer

Over the last week it answered 27.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add dropspace --transport http https://api.dropspace.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.dropspace.dev/mcp
~/.codex/config.toml
[mcp_servers.dropspace]
url = "https://api.dropspace.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dropspace": {
      "url": "https://api.dropspace.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "dropspace": {
      "type": "http",
      "url": "https://api.dropspace.dev/mcp"
    }
  }
}

Available tools 40

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

launch
create_launch
create a new launch for publishing to social platforms
delete_launch
delete a launch (cannot delete running launches)
get_launch
get a launch by ID with posting status per platform
get_launch_analytics
get publishing analytics with per-post engagement metrics (likes, views, shares, etc.). metric fields vary by platform: facebook reports reactions, likes (mirroring reactions.total), comments and shares - it has no impressions or reach, and facebook story metrics are unavailable. an instagram story reports views, reach, replies and frames only while it is live (24 hours, no backfill); under 5 viewers it returns story_insights_withheld instead of numbers
get_launch_status
get detailed posting status with per-platform logs
update_launch
update a launch (cannot update running/completed/partial launches)
autopilot
get_autopilot
get autopilot status: config, queued ideas, and drafts pending review. autopilot is the autonomous content engine that drafts and schedules posts nightly (pro/premium plans).
list_autopilot_review
list autopilot drafts awaiting approval (review mode). each item is a draft launch - approve, reject, or edit it via update_launch first.
list_autopilot_runs
recent autopilot run history - one row per run step (refresh_insights, generate_blueprints, schedule_slots) with stats and errors.
run_autopilot_now
trigger a manual autopilot run immediately instead of waiting for the nightly run. steps already completed today are skipped (limited to 2 per hour).
persona
create_persona
create a new persona for AI content generation tone/style
delete_persona
delete a persona
get_persona
get a persona by ID with analysis details and writing samples
update_persona
update a persona's name or writing samples
generate
generate_content
generate AI content for a launch's platforms using Claude
generate_media
submit an AI image or video generation job for a launch. Returns 202 with a job_id; poll get_media_job for completion. Requires generate scope. script_video requires platform=instagram|tiktok and prompt is required (not just product_description). video and script_video only support 16:9 and 9:16 aspect ratios.
retry
retry_launch
retry failed platforms for a launch. by default every failed platform is retried; pass `subreddit` to retry ONE reddit destination (leaving its siblings — succeeded or failed — untouched), and add `account_id` when that destination belongs to a secondary connected reddit account rather than your primary.
retry_launch_content
retry AI content generation for failed platforms (requires generate scope)
all
delete_all_posts
Delete all published posts for a launch from their platforms. Only deletes from Twitter, Facebook, LinkedIn, Reddit, and YouTube. Instagram and TikTok posts are skipped (require manual deletion).
analyze
analyze_persona
trigger AI analysis of a persona's writing style (queued async)
apply
apply_recommendation
apply a recommendation's one-click action. repost_winner and cross_post create a DRAFT launch seeded with the winning content (nothing publishes until scheduled); boost_winner creates a PAUSED meta boost and requires ad_account_id (activation, and therefore spend, is a separate step); promote_winner queues the winner into autopilot; pause_underperformer adds a standing directive to the autopilot config.
approve
approve_autopilot_draft
approve an autopilot draft - schedules it for publishing (a stale scheduled date rolls forward to the next posting slot).
audience
get_audience
follower counts + growth for every connected instagram / youtube / tiktok / twitter account and facebook page. one entry per ACCOUNT, not per platform: "entity_id" is null for your primary account on a platform and set for each additional one, so a user with two instagram accounts returns two instagram entries. counts come from each platform's official API and are cached for 15 minutes. youtube works differently: each youtube read spends a shared daily quota, so while you keep reading a creator's audience, their youtube count is refreshed in the background about once an hour, and an on-demand read re-fetches at most every 6 hours if that refresh is delayed; if the daily quota is exhausted, a youtube read returns the most recent successful count instead of null. "current.captured_at" is always when that count was actually read from the platform, never when it was served: use it to judge freshness. "series" is the stored history; youtube history is kept for 30 days (youtube's API storage limit), so youtube growth reaches back about 30 days whatever window_days says, while other platforms keep full history. growth is measured from the OLDEST stored point inside the window, which — because history points are recorded when you read, at most one per account per day — can be much younger than window_days: read "effective_window_days" (the span the delta actually covers) and "baseline_captured_at" before comparing growth across accounts. linkedin is not covered (its API exposes no personal-profile follower count). set include_instagram_insights to add instagram growth analytics to each instagram entry: follows, unfollows, net, and reach split into followers and non-followers per pacific-time day (the last 7 days are settled: false because instagram still revises them), followers_over_time (an estimate rebuilt back from the current count), weekly velocity with a trend, non_follower_reach_share, and contact-button taps. it reads up to 31 days per call, newest first, so a longer window fills over a few calls (days_pending says how many are left); instagram reports none of it for accounts under 100 followers (available: false).
batch
get_batch_launch_analytics
get cached analytics for multiple launches in one request (no live refresh, max 100 IDs)
changelog
get_changelog
machine-readable release history (public) - version, date, type, summary, migration notes on breaking entries. the X-Notice header's structured backstory.
configure
configure_autopilot
create or update the autopilot config. merge semantics: only the fields you send change. enabling requires at least one platform with a connected account.
connection
update_connection_profile
edit the connected account's profile ON the platform. youtube only today: sets the channel description (max 1,000 characters; an empty string clears it) via channels.update. instagram's api can read a profile but not write it, facebook page "about" needs a permission dropspace does not hold, and tiktok / x / linkedin expose no profile write - those return an error with the reason. requires the write scope.
connections
list_connections
list your connected social media accounts. each row has a "platform" and an "entity_id" (null for your primary account on that platform, set for additional accounts). to target a specific account in create_launch when you have more than one on instagram / tiktok / youtube / twitter / reddit, pass "{platform}:{entity_id}" as a user_platform_accounts key (the bare "{platform}" key targets your primary). the same entity_id is what disconnect_connection and retry_launch take as account_id
discard
discard_persona_analysis
discard a persona's pending analysis without committing (preserves any previously saved analysis)
dismiss
dismiss_recommendation
dismiss a pending recommendation so it stops showing everywhere.
dropspace
get_dropspace_status
check which platforms have a connected dropspace official account (requires read scope)
finalize
finalize_persona
commit a persona's pending analysis after review (the analyzed voice becomes usable)
launches
list_launches
list your launches with pagination
media
get_media_job
poll the status of a media generation job. Returns the result_url when complete.
personas
list_personas
list your personas with pagination
post
delete_post
Delete a single published post from its platform. Only works for Twitter, Facebook, LinkedIn, Reddit, and YouTube. Instagram and TikTok do not support API deletion.
publish
publish_launch
publish a launch to all configured platforms (queued async)
recommendations
list_recommendations
list actionable recommendations computed from your organic post performance: winners to repost, cross-post, or boost, autopilot promote signals, and underperformer pause signals. dropspace sweeps post metrics every 30 minutes and compares each post to your own per-platform baseline.
reject
reject_autopilot_draft
reject an autopilot draft - deletes it and refunds the launch slot. optional feedback teaches future runs what to avoid.
usage
get_usage
get your current plan, usage limits, and billing period (requires read scope)

Endpoints

URLTransportStateLatencyChecked
https://api.dropspace.dev/mcp streamable-http answering 85 ms 15 min ago

Alternatives to Dropspace

same job, measured the same way
PostZen
by postzen

Schedule and publish social posts, manage the inbox, and read analytics across 10 platforms

answering
Zernio
by zernio

Schedule, publish, and analyze social media across 15+ platforms, plus inbox, ads, and analytics.

52 tools answering
Mallary MCP
by mallary

Publish and schedule social posts, reply to comments, and read analytics across connected platforms.

answering
Outstand
by outstand

Publish and schedule social media posts and read analytics across 12 networks through one API.

answering
Social media studio
by so-me

Schedule and publish posts on 18 social platforms, manage drafts, inbox, media and analytics.

answering
ShortSync
by shortsync

Let AI agents draft, schedule and publish posts to 17 social platforms, read analytics and reply.

answering
Social Media MCP by Publinio
by publinio

Create social posts, schedule campaigns, and read saved analytics with Publinio.

answering
PostQuest
by post-quest

Draft, validate, schedule and publish social posts to 10 networks, then read post analytics.

answering

Dropspace — questions

Answers built from our own checks of this server.

What can Dropspace do?
It exposes 40 tools, read directly from the server on our last check. Among them: analyze_persona, apply_recommendation, approve_autopilot_draft, configure_autopilot, create_launch, create_persona and 34 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Dropspace mostly used for?
Its tools cluster around launch, autopilot and persona. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Dropspace working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 20 of 72 checks got a reply (27.8%), average response time 557 ms. The bar chart above shows every period we have measured.
The registry lists Dropspace as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Dropspace?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Dropspace need an API key?
No. Dropspace completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 40 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Dropspace?
It answers our handshake in 557 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Dropspace?
The npm package @jclvsh/dropspace was installed 1 032 times in the last week. Week over week that is +40%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.