Skip to main content
Glama
taisly

Taisly

Official

Taisly Agent Kit: AI agent social media posting for TikTok, Instagram Reels, YouTube Shorts, X, and Facebook

Taisly Agent Kit

AI agent social media posting for short-form video. Taisly Agent Kit is a JSON-first SDK, CLI, Agent Skill, and MCP server that lets AI agents, developer tools, and automation workflows publish videos to TikTok, Instagram Reels, YouTube Shorts, X, Facebook, and other connected social platforms through Taisly.

Use it when your agent can create content, write captions, or prepare a campaign, but still needs a reliable video publishing API to put that content online.

Website | Agent Kit | API Docs | npm | GitHub | Guide

Languages

Read this guide in: English, Español, Deutsch, Français, Português, ไทย, 中文, Bahasa Indonesia, Русский, Nederlands, 한국어, 日本語, العربية, Türkçe, Polski.

Related MCP server: atlas-social-mcp

Why developers use it

  • Build AI agent social media posting into Codex, Claude Code, Cursor, OpenClaw, and custom automation tools.

  • Automate video publishing from one local file to multiple connected social accounts.

  • Give agents a safe JSON workflow: discover accounts, validate payloads, create posts, and check status.

  • Add TikTok API posting automation, Instagram Reels automation, YouTube Shorts publishing, and cross-platform social media automation without building every platform integration yourself.

Taisly handles the connected accounts and posting execution. Your agent handles planning, caption writing, campaign logic, or workflow orchestration.

Agent Skill

This package includes the Taisly Social Media Posting Skill in SKILL.md. Use it with Claude Code, Codex, Cursor, OpenClaw, and custom agents when you want the agent to understand the safe posting workflow before it touches live social accounts.

Recommended skill workflow:

auth -> platforms -> validate -> confirm -> create -> status

The skill tells agents to discover connected accounts, validate the post, ask for explicit user confirmation, create the post, and save the returned historyId for status checks.

Install

npm install -g @taisly/agent

Or run it without a global install:

npx @taisly/agent help

Start the stdio MCP server:

npx @taisly/agent mcp

For local development inside this repository:

node packages/agent/src/cli.js help

Authentication

Create an API key in Taisly Settings, then set:

export TAISLY_API_KEY="taisly_..."
export TAISLY_API_URL="https://app.taisly.com/api/private"

TAISLY_API_URL is optional unless you need to target a non-default Taisly API environment.

Quick start

List the connected social accounts available to the API key:

taisly auth:status
taisly platforms:list

Validate a local video before publishing:

taisly posts:validate \
  --video ./launch.mp4 \
  --platforms platform_id_1,platform_id_2 \
  --description "Launch day"

Publish now:

taisly posts:create \
  --video ./launch.mp4 \
  --platforms platform_id_1,platform_id_2 \
  --description "Launch day"

Schedule for later:

taisly posts:create \
  --video ./launch.mp4 \
  --platforms platform_id_1,platform_id_2 \
  --description "Launch day" \
  --scheduled "2026-06-14T09:00:00+07:00"

Check the returned post:

taisly posts:status --id <historyId>

Every command prints JSON so agents can parse results without scraping terminal text.

MCP server

Taisly Agent Kit includes a stdio MCP server in the same package. MCP clients can connect it with:

{
  "mcpServers": {
    "taisly": {
      "command": "npx",
      "args": ["@taisly/agent", "mcp"],
      "env": {
        "TAISLY_API_KEY": "taisly_..."
      }
    }
  }
}

Available MCP tools:

  • taisly_auth_status

  • taisly_platforms_list

  • taisly_platform_schema

  • taisly_posts_validate

  • taisly_posts_create

  • taisly_posts_status

  • taisly_posts_list

  • taisly_reposts_list

  • taisly_reposts_create

taisly_posts_create requires confirmed: true. Set it only after the user explicitly approves the video, destination accounts, caption, and schedule.

JSON workflow for agents

Agents can write a payload file and pass it to the CLI:

{
  "video": "./launch.mp4",
  "platforms": ["platform_id_1", "platform_id_2"],
  "description": "Launch day. Short demo, big update.",
  "scheduled": "2026-06-14T09:00:00+07:00"
}

Then run:

taisly posts:validate --json ./campaign.json
taisly posts:create --json ./campaign.json

The video path must point to a real local file available to the agent. Supported local preflight extensions are .mp4, .mov, .avi, .mkv, .webm, .flv, .mpeg, and .mpg.

Commands

taisly auth:status
taisly platforms:list
taisly integrations:list
taisly platforms:schema --platform TikTok
taisly posts:validate --video ./launch.mp4 --platforms platform_id_1 --description "Launch day"
taisly posts:create --video ./launch.mp4 --platforms platform_id_1 --description "Launch day"
taisly posts:create --json ./campaign.json
taisly posts:list --page 1
taisly posts:status --id <historyId>
taisly reposts:list
taisly reposts:create --from <platform_id> --to <platform_id_1,platform_id_2>
taisly mcp

integrations:* commands are aliases for platforms:* commands. Taisly calls connected social accounts platforms in the app, while many public APIs call them integrations.

SDK

import { Taisly } from "@taisly/agent";

const taisly = new Taisly({
  apiKey: process.env.TAISLY_API_KEY,
});

const platforms = await taisly.platforms.list();

const validation = await taisly.posts.validate({
  video: "./launch.mp4",
  platforms: [platforms.data[0].id],
  description: "Launch day",
});

const post = await taisly.posts.create({
  video: "./launch.mp4",
  platforms: [platforms.data[0].id],
  description: "Launch day",
  scheduled: "2026-06-14T09:00:00+07:00",
});

console.log(validation.success);
console.log(post.historyId);

Use with AI agents

Taisly Agent Kit is designed for agentic workflows where the user gives a high-level instruction and the agent executes a safe posting path.

  • Codex: let a coding agent publish demo videos, launch clips, or build updates after user confirmation.

  • Claude Code: add social posting to local content workflows and campaign scripts.

  • Cursor: ship video publishing from developer tools, content apps, and internal automation.

  • OpenClaw and custom agents: connect planning, caption writing, and posting execution through a single CLI.

Recommended agent path:

auth:status -> platforms:list -> platforms:schema -> posts:validate -> user confirmation -> posts:create -> posts:status

Agent recipes

The examples/ folder includes copy-paste workflows for common coding agents:

  • examples/codex/post-video.md

  • examples/claude-code/schedule-video.md

  • examples/cursor/post-build-demo-video.md

  • examples/post-video.sh

  • examples/schedule-video.sh

What this package is not

  • It is not a social media dashboard.

  • It is not a video editor.

  • It does not replace a Taisly account.

  • It requires connected social accounts and a Taisly API key.

  • It does not bypass platform rules, account permissions, or media validation.

Current limits

  • posts:create uses the existing multipart /post API.

  • posts:status reads recent history because a single-post status endpoint is not available yet.

  • posts:validate is local preflight; final validation still happens in Taisly.

  • The MCP server currently uses stdio transport. Remote MCP transport is planned later.

  • Media upload reuse is planned later.

A
license - permissive license
-
quality - not tested
D
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taisly/agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server