Getting Started

1. Connect social accounts

Open Taisly and connect the social accounts you want agents or integrations to use:

https://app.taisly.com

Your connected accounts become Taisly platforms. Agents and API integrations should always list platforms first and use the exact platform IDs returned by Taisly.

2. Pick an integration path

Hosted agents

Remote MCP

Use Taisly from Claude web, ChatGPT, and other hosted MCP clients when your video is already available by public HTTPS URL.

https://example.com/video.mp4Open MCP guide

Local agents

Local MCP

Let Claude Code, Codex, Cursor, and local runtimes publish files they can read from your computer or project workspace.

./launch.mp4Use local MCP

Shell workflows

Taisly CLI

Run repeatable posting commands, validate payloads, and script local publishing flows through the official Agent Kit package.

taisly posts:create --video ./launch.mp4Install Agent Kit

Backend integrations

REST API

Build direct server-side integrations with API keys, multipart video upload, platform IDs, history, schedules, and repost rules.

multipart/form-data uploadExplore API

Use remote MCP when your agent runs in the cloud and can provide a direct public video URL. Use local MCP or the Taisly CLI when the video file is on your machine. Use the REST API when you are building a backend integration.

3. Verify access

For Agent Kit or CLI workflows:

npm install -g @taisly/agent
taisly auth:status
taisly platforms:list

For direct API workflows, generate an API key in Taisly settings and send it as a bearer token.

4. Validate before posting

Agents should validate:

• The destination platform ID.
• The video URL or local file path.
• The caption.
• The schedule, if one is provided.

5. Track status

Every created post returns a Taisly history ID. Save it and use it to check whether the post is pending, successful, failed, or scheduled.