SocialDispatch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOCIALDISPATCH_API_KEY | Yes | Your SocialDispatch API key, starting with sd_live_... | |
| SOCIALDISPATCH_API_URL | No | The SocialDispatch API base URL, e.g. https://api.socialdispatch.site |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_social_connectionsA | List all connected social media accounts/pages (Facebook Pages, Instagram, X/Twitter, TikTok, YouTube) in SocialDispatch. Returns connection IDs, names, platforms, and connection status. |
| generate_social_contentA | Generate platform-tailored social media post drafts for Facebook, Instagram, and X (Twitter) from a topic, idea, or link using SocialDispatch AI copywriting engine. |
| upload_mediaA | Upload a local image or video file directly to SocialDispatch and its enabled storage (Cloudflare R2 or local storage). Returns the public media URL, storage provider, and metadata to use for publishing. |
| publish_social_postB | Publish a social post immediately across one or more connected social accounts in SocialDispatch. Supports remote media URLs or local file paths directly. |
| schedule_social_postB | Schedule a social post for a specific future date/time or into the next scheduled queue slot. Supports remote media URLs or local file paths directly. |
| generate_and_publish_postC | End-to-end AI agent action: Generates platform-tailored copies (Facebook, Instagram, X) from a topic and immediately publishes (or schedules) across target connections. Supports remote media URLs or local file paths directly. |
| get_post_statusA | Check publication status, external live URLs, and execution logs for a specific post in SocialDispatch. |
| list_recent_postsA | List recent posts in SocialDispatch to see publishing history, scheduled queue items, and statuses. |
| update_social_postB | Update or edit a post content or schedule in SocialDispatch. If the post is already published, you can optionally set updateOnPlatform=true to sync the update to supported live platforms (Facebook Page, YouTube). |
| delete_social_postA | Delete a post from SocialDispatch. Supports deleting locally only, or deleting both locally and from connected live platforms (Facebook, X/Twitter, YouTube). |
| add_content_ideasA | Batch adds new content ideas/plans into the SocialDispatch pipeline queue in IDEA stage. Allows brainstorming and researching batches of content ideas (up to 50 at once). |
| list_content_pipelineB | Returns current queued items in the SocialDispatch content pipeline, showing counts and progress (e.g. 3 generated, 7 pending ideas). |
| update_content_progressA | Updates progress of a content item after script generation or media rendering (transitions stage to SCRIPTED, GENERATING, or GENERATED, and attaches script or media). |
| get_next_pipeline_itemB | Retrieves the next oldest or prioritized ungenerated content item from the pipeline queue to resume work where left off across sessions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools map to a distinct resource+action (list connections, upload media, publish, schedule, update, delete, status, pipeline ops). The only real overlap is between generate_and_publish_post and the pair generate_social_content + publish_social_post, which do the same work in one call versus two; descriptions make the distinction clear but an agent could still hesitate. update_social_post vs update_content_progress target different objects (posts vs pipeline items) and are adequately separated by wording.
Every tool follows a consistent snake_case verb_noun pattern: list_*, get_*, generate_*, upload_*, publish_*, schedule_*, update_*, delete_*, add_*. The compound generate_and_publish_post is a slight deviation but still readable and follows the same convention.
14 tools sit comfortably in the well-scoped range and each covers a distinct stage of the workflow (connections, generation, media, publishing, scheduling, post CRUD, pipeline). Nothing appears redundant or padded beyond the single convenience wrapper.
Post lifecycle is fully covered (publish, schedule, list, status, update, delete) and the AI pipeline has ideas, listing, progress, and next-item retrieval. Gaps remain: connections are read-only (no connect/disconnect/refresh), media has upload but no list/delete, and there is no analytics/engagement retrieval for published posts, so agents cannot close the measurement loop.