Social Publisher MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAU_PYTHON | No | Path to Python executable for social-auto-upload | |
| SAU_CONDA_ENV | No | Conda environment name for social-auto-upload (e.g., 'social-publisher-sau') | |
| SAU_LOCAL_CHROME_PATH | No | Path to local Chrome executable | |
| PLAYWRIGHT_DOWNLOAD_HOST | No | Mirror host for Playwright browser download | |
| SOCIAL_PUBLISHER_DRY_RUN | No | Set to 'false' to enable live publishing (default 'true') | |
| SAU_LOCAL_CHROME_HEADLESS | No | Whether to run Chrome headless (e.g., 'false') | |
| SOCIAL_PUBLISHER_SAU_MODE | No | Mode for social-auto-upload (e.g., 'vendored') | |
| SOCIAL_PUBLISHER_PYTHON_BIN | No | Path to Python binary or 'conda' | |
| SOCIAL_PUBLISHER_DOUYIN_ENGINE | No | Engine for Douyin publishing (e.g., 'sau') | |
| SOCIAL_PUBLISHER_DOUYIN_HEADED | No | Run browser headed (e.g., 'true') | |
| SOCIAL_PUBLISHER_DOUYIN_ACCOUNT | No | Douyin account name (e.g., 'creator') | |
| SOCIAL_PUBLISHER_SAU_PYTHON_ARGS | No | Additional arguments for Python (e.g., '-n,social-publisher-sau,python') |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_platformsA | List supported social platforms and adapter status. |
| login_platformA | Start an interactive login flow for supported live CLI adapters. Douyin uses social-auto-upload's sau CLI. |
| check_platform_authA | Check saved login/cookie state for supported live CLI adapters. Douyin uses social-auto-upload's sau CLI. |
| prepare_postA | Validate a post and build platform-specific payloads without publishing. |
| publish_postB | Publish a post or create a dry-run publish record. Live adapters require liveConfirmation.confirmed=true plus a human-reviewed summary. |
| check_publish_statusA | Read a saved publish record by id. |
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 6 tools
Each tool targets a distinct aspect of the social publishing workflow: platform enumeration, auth management, post preparation, publishing, and status retrieval. Even the two auth-related tools are clearly separated by their actions (starting a login vs. checking existing auth state).
All tool names follow a consistent verb_noun pattern in snake_case (list_platforms, login_platform, check_platform_auth, prepare_post, publish_post). The slight variation in check_publish_status still adheres to the same style and is easily readable.
With six tools, the server is well-scoped for its purpose, covering the essential operations of platform discovery, authentication, post preparation, publishing, and status checking without unnecessary redundancy or bloat.
The core lifecycle is covered: login/check auth, prepare, publish, and check status. Minor gaps exist, such as no logout or auth refresh operation and no list of previously published posts, but these are not critical to the main publishing workflow and can be worked around.