Taisly
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAISLY_API_KEY | Yes | API key for Taisly, required for authentication. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taisly_agent_setup_startA | Start browser-based Taisly authentication for an AI agent. Returns a loginUrl that the user must open and approve before checkin. |
| taisly_agent_checkinA | Finish setup after the user approves the loginUrl in the browser. Saves the local Taisly agent credential for later CLI and MCP calls. |
| taisly_auth_statusA | Check whether the Taisly API key is valid and count connected social accounts. |
| taisly_platforms_listA | List connected TikTok, Instagram, YouTube, X, Facebook, and other social accounts available to this API key. |
| taisly_platform_schemaB | Get posting constraints and supported settings for a destination platform. |
| taisly_platform_connect_startA | Start browser-based connection for a social account. Returns a connectUrl that the user must open and approve in the browser. |
| taisly_platform_connect_checkA | Check whether a social account connection started by taisly_platform_connect_start has appeared in Taisly. |
| taisly_posts_validateA | Validate a local video path, destination platform IDs, caption, and optional schedule before publishing. |
| taisly_posts_createA | Start publishing or schedule a video post after explicit user confirmation. success: true means Taisly accepted the request, not that every platform published it. For an immediate post, use the returned historyId with taisly_posts_status and report success only when the per-platform status is SUCCESS. |
| taisly_posts_statusA | Fetch per-platform status for a Taisly post by historyId. Inspect data.result[].status: PENDING is still processing, SUCCESS is published, and FAILED is not published. |
| taisly_posts_listA | List recent Taisly post history for status checks and audits. |
| taisly_reposts_listA | List configured repost automations for connected social accounts. |
| taisly_reposts_createA | Create a repost automation from one connected account to one or more destination accounts. |
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 13 tools
Each tool has a clearly distinct purpose across authentication, platform setup, posting, status checks, and repost automations. The start/check pairs are explicitly separated, and validate/create/status/list for posts do not overlap in role.
All tools use a consistent taisly_ prefix and snake_case, mostly following a resource_action pattern. Minor deviations exist where names are noun_noun rather than action-final (e.g. platform_schema, auth_status) and where platform/platforms is inconsistently singular or plural.
The 13 tools are well-scoped for a social posting and repost automation server. Authentication, platform discovery, posting, validation, status, and repost operations each earn their place without obvious bloat.
The set covers the core lifecycle: setup, platform connection, validation, publishing, status checking, post history, and repost automation creation/listing. Minor gaps remain around canceling or deleting scheduled posts, managing or deleting repost automations, and disconnecting accounts, but these are not blocking for core workflows.