Social Media
sprkly.app
Manages social media content scheduling, drafts, and performance analytics via the Sprkly platform.
ENDPOINT 1
https://sprkly.app/api/mcp
MCP server metadata
- Name
- sprkly-mcp
- Version
- 1.0.0
sprkly schedules social media posts. BE FAST. The whole point of this connector is that posting takes one exchange, not a conversation. Every extra tool call costs the user an approval click, and every extra question costs them a reply. If you have what to post, where, and when, go. Go straight to sprkly_schedule_post. Do not call other tools to prepare for it. It validates the post itself and returns the same platform errors a separate check would (caption limits, missing media for Instagram and TikTok, missing YouTube title). If a target platform has more than one connected account it does NOT post: it returns `needsAccountChoice` with the accounts to choose from. Put that question to the user, then re-call with `profile_ids` set to every chosen account — `profile_ids` alone is a complete call and replaces `platforms` entirely. MEDIA: just pass the link in `media_urls`. sprkly pulls it into storage itself when the platform needs that, and it converts Google Drive and Dropbox share links for you. You do NOT need sprkly_add_media_from_url first. Use that tool only when the user wants a media id back for reuse across several posts. Times are ISO 8601. Ask only for what you are missing. Do not read the whole plan back for confirmation before scheduling: the user can see what they asked for, and a post can be edited or deleted afterwards. Ask before DELETING something. The four things a post needs are what, where, when, and how many. Everything else has a sane default. If the user gave you all four, schedule it and report the result in one line. The read tools are for when the user asks, not for preparation: sprkly_list_profiles (what is connected), sprkly_list_scheduled_posts (what is queued), sprkly_validate_post_policy (check a draft WITHOUT scheduling it). For "what should I post" or "when should I post", call sprkly_get_analytics first and reason from what it returns. It gives you evidence, not advice: totals, period-on-period change, best hour and weekday, and the top posts behind them. Two rules when you use it. Check `samples` before calling anything a pattern — a best hour backed by one post is not a finding, and saying so is more useful than a confident guess. Check `coverage` before comparing platforms: Instagram reports likes and comments only, Threads and Facebook report nothing at all, and posts published outside sprkly are invisible.
Known tools 18
sprkly_add_media_from_urlDownload an image or video from a public link into sprkly and get a media_id back, for reuse across several posts.
Inferred read-onlysprkly_draft_postCompose a caption from a content hint and save it as a draft in sprkly, shaped to the tightest caption limit among the target platforms.
Inferred read-onlysprkly_export_automation_templateDownload one Instagram auto reply as a shareable template.
Inferred read-onlysprkly_get_account_summaryPlan tier, trial state, connected account count, scheduled post counts by status, and the next three upcoming posts.
Potential side effectssprkly_get_analyticsHow the user's published posts actually performed: total views and engagement, week-on-week / month-on-month / year-on-year change, their best posting hour, weekday and content category, and the top posts behind those numbers.
Inferred read-onlysprkly_get_billing_summarySubscription status, current plan, period end, purchased handles and the last few billing events.
Inferred read-onlysprkly_get_post_approval_statusWhether a post is awaiting human review, approved or rejected, including reviewer notes and timestamps.
Potential side effectssprkly_get_post_statusFull detail for one post: status, targets, scheduled and published times, permalink, and the failure reason if it did not publish.
Potential side effectssprkly_get_tiktok_posting_optionsThis creator's allowed TikTok privacy levels and interaction settings, fetched live from TikTok.
Inferred read-onlysprkly_import_automation_templateRead an auto reply template, and optionally set it up.
Inferred read-onlysprkly_list_connected_social_accountsEvery ACTIVE social account linked to this sprkly account: platform, handle, follower count, and whether it needs reconnecting.
Inferred read-onlysprkly_list_profilesThe profile ids needed to target a post, with each one's platform and handle.
Potential side effectssprkly_list_scheduled_postsThe post queue, newest first, with a caption preview, targets, status and failure reason.
Potential side effectssprkly_update_scheduled_postChange the caption, publish time, target accounts or attached media on a post that has not published yet.
Potential side effectssprkly_validate_post_policyCheck a caption against each target platform's posting rules before scheduling: caption length, media requirements, hashtag ceilings, whether links are clickable, required YouTube titles, and PII or prohibited-content warnings.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sprkly-mcp]
url = "https://sprkly.app/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sprkly-mcp": {
"type": "http",
"url": "https://sprkly.app/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sprkly-mcp
Remote MCP URL: https://sprkly.app/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sprkly-mcp": {
"url": "https://sprkly.app/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sprkly-mcp": {
"type": "http",
"url": "https://sprkly.app/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sprkly-mcp",
"transport": "streamable-http",
"url": "https://sprkly.app/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.