AI agent 워크플로우를 통해 TikTok, Instagram Reels, YouTube Shorts, X, Facebook에 숏폼 동영상을 게시합니다.
다른 이름 taisly/agent, agent, @taisly/agent
- 스타
- 222
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.2.10
- 마지막 커밋
- 2026년 10월 22일
- 라이선스
- MIT
Taisly MCP란?
AI agent 워크플로우를 통해 TikTok, Instagram Reels, YouTube Shorts, X, Facebook에 숏폼 동영상을 게시합니다.
프로젝트 README에서 생성된 요약
Taisly MCP server 정보
Taisly Social Media Posting은 개발자와 AI agent 사용자가 여러 소셜 플랫폼에 걸쳐 숏폼 동영상 배포를 자동화할 수 있도록 지원합니다. 이 도구를 사용하면 에이전트가 TikTok, Instagram Reels, YouTube Shorts, X, Facebook에 콘텐츠를 직접 게시할 수 있습니다. 콘텐츠를 생성하거나 캡션을 작성할 수는 있지만 온라인 게시를 위한 직접적인 통합 기능이 없는 에이전트에게 가교 역할을 합니다.
사용자는 간편한 설정을 위해 OAuth를 사용하는 원격 MCP 엔드포인트로 연결하거나, npx를 통해 로컬 stdio MCP server를 실행하여 에이전트가 로컬 머신에 저장된 동영상 파일에 액세스할 수 있도록 할 수 있습니다. 이 시스템은 연결된 계정 검색, 동영상 페이로드 검증, 게시 상태 확인을 포함하는 구조화된 JSON 우선 워크플로우를 제공합니다. 개발자는 이러한 기능을 Claude Code, Cursor 또는 Codex와 같은 도구에 통합하여 개별 플랫폼 통합 기능을 직접 구축하지 않고도 초기 아이디어에서 게시된 동영상까지 구현할 수 있습니다.
활용 사례
- 1교차 플랫폼 동영상 게시AI agent가 단일 로컬 동영상 파일을 가져와 여러 소셜 미디어 계정에 동시에 게시할 수 있습니다.
- 2자동화된 콘텐츠 검증개발자가 에이전트에게 게시를 시도하기 전, 특정 플랫폼에 동영상과 설명이 유효한지 확인하도록 지시할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Taisly MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Taisly MCP 설치
$ claude mcp add --env 'TAISLY_API_KEY=<YOUR_TAISLY_API_KEY>' agent -- npx -y @taisly/agentCursor에 Taisly MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"agent": {
"command": "npx",
"args": [
"-y",
"@taisly/agent"
],
"env": {
"TAISLY_API_KEY": "<YOUR_TAISLY_API_KEY>"
}
}
}
}VS Code에 Taisly MCP 설치
.vscode/mcp.json
{
"servers": {
"agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@taisly/agent"
],
"env": {
"TAISLY_API_KEY": "<YOUR_TAISLY_API_KEY>"
}
}
}
}VS Code CLI에 Taisly MCP 설치
$ code --add-mcp '{"name":"agent","type":"stdio","command":"npx","args":["-y","@taisly/agent"],"env":{"TAISLY_API_KEY":"<YOUR_TAISLY_API_KEY>"}}'Claude Desktop에 Taisly MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"agent": {
"command": "npx",
"args": [
"-y",
"@taisly/agent"
],
"env": {
"TAISLY_API_KEY": "<YOUR_TAISLY_API_KEY>"
}
}
}
}Codex에 Taisly MCP 설치
$ codex mcp add agent --env 'TAISLY_API_KEY=<YOUR_TAISLY_API_KEY>' -- npx -y @taisly/agentCodex config.toml에 Taisly MCP 설치
~/.codex/config.toml
[mcp_servers.agent] command = "npx" args = ["-y", "@taisly/agent"] [mcp_servers.agent.env] TAISLY_API_KEY = "<YOUR_TAISLY_API_KEY>"
Gemini CLI에 Taisly MCP 설치
$ gemini mcp add -s user -e 'TAISLY_API_KEY=<YOUR_TAISLY_API_KEY>' agent npx -- -y @taisly/agentGemini settings.json에 Taisly MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"agent": {
"command": "npx",
"args": [
"-y",
"@taisly/agent"
],
"env": {
"TAISLY_API_KEY": "<YOUR_TAISLY_API_KEY>"
}
}
}
}시작하려면 키가 필요
2026년 11월 16일에 키 없이 실행하자 멈추고 키를 요구했습니다. 위 변수를 설정하기 전까지 클라이언트에는 도구가 보이지 않습니다.
구성
TAISLY_API_KEY비밀Optional. Run `taisly setup --agent <agent-slug>` to store a local Taisly agent credential, or set this manual API key from Taisly Settings.
TAISLY_API_KEY
| 이름 | 설명 | 유형 |
|---|---|---|
| TAISLY_API_KEY | Optional. Run `taisly setup --agent <agent-slug>` to store a local Taisly agent credential, or set this manual API key from Taisly Settings. | 비밀 |
| TAISLY_API_KEY | — |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기
Taisly Agent Kit
Free AI-first 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. The package is free to install and designed to get an agent from idea to published video without building every platform integration yourself.
Website | Agent Kit | API Docs | npm | GitHub | MCP Registry | Glama | Guide
Languages
Read this guide in: English, Español, Deutsch, Français, Português, ไทย, 中文, Bahasa Indonesia, Русский, Nederlands, 한국어, 日本語, العربية, Türkçe, Polski.
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.
- Start free, then upgrade only when the publishing workflow grows.
Taisly handles the connected accounts and posting execution. Your agent handles planning, caption writing, campaign logic, or workflow orchestration.
Optional local workflows
- Install the package for free.
- Create or connect a Taisly account from your AI agent.
- Let the agent authenticate, connect social accounts, validate videos, and publish through a JSON-first workflow.
- Upgrade later when you need higher-volume publishing, larger account sets, or automatic repost workflows.
No credit card is required to get started. Paid plans are for teams and workflows that need more scale.
Agent Skill
This package includes the Taisly Social Media Posting Skill in SKILL.md. Use it with Claude Code, Codex, Cursor, OpenClaw, and other 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.
Codex plugin
This package includes a Codex plugin manifest in .codex-plugin/plugin.json. The plugin points Codex to the canonical SKILL.md file and the official remote MCP server:
https://app.taisly.com/mcp
Use the plugin when you want Codex to discover both the posting workflow instructions and the Taisly MCP tools from one package. The root SKILL.md is the single source of truth for the agent workflow.
Connect an AI agent through remote MCP
Remote MCP is the default AI-agent connection. If Taisly tools are already available, call taisly_auth_status and taisly_platforms_list directly. OAuth provides access; do not install this package or ask for an API key for that connection.
Help me connect Taisly to this agent using the setup guide. Check access and list my connected social accounts. Do not publish anything during setup.
Full documentation: https://docs.taisly.com/docs/mcp
The remote server URL is https://app.taisly.com/mcp. Add it through your client's remote MCP and OAuth settings if needed. Human authorization or administrator approval may be required. On expiry, reconnect through OAuth rather than switching to the CLI.
Optional local package installation
Use the following package instructions for explicit SDK, CLI or local-file workflows. They are not remote MCP setup requirements.
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
Local package authentication
For the local package, browser setup can store a local credential without manually copying an API key. Use any short agent slug, for example claude-code, codex, cursor, windsurf, openclaw, hermes-agent, cline, or aider.
Help me set up Taisly Agent Kit.
1. Install the CLI: npm i -g @taisly/agent
2. Run taisly setup --agent <agent-slug> and send me the login URL so I can finish authentication.
3. Wait for me to finish login in the browser.
4. Run taisly checkin --agent <agent-slug>.
5. Tell me if Taisly is connected and ready. If not, tell me what failed.
If you cannot install or run the Taisly CLI in this environment, stop and tell me to open Taisly Settings instead.
The setup command stores a local Taisly agent credential, so later CLI and MCP commands can run without manually copying an API key.
Manual fallback: create an API key in Taisly Settings, then set:
export TAISLY_API_KEY="taisly_..."
Advanced: by default, the browser setup stores the local credential in ~/.taisly/config.json. Most users should not change this. Set TAISLY_CONFIG_HOME=/path/to/dir only for CI, tests, or isolated agent profiles that need a separate credential store.
Quick start
List the connected social accounts available to the API key:
taisly auth:status
taisly platforms:list
Connect a social account from an AI-agent flow:
taisly platforms:connect:start --platform instagram
# Open the returned connectUrl and finish authorization in the browser.
taisly platforms:connect:check --platform instagram
taisly platforms:list
Supported connect slugs: instagram, tiktok, youtube, x, facebook.
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>
Posting settings
Discover supported options and accepted values for each destination platform:
taisly platforms:schema --platform TikTok
taisly platforms:schema --platform YouTube
Group options by platform name in settings. For example:
taisly posts:create \
--video ./launch.mp4 \
--platforms your_tiktok_platform_id,your_youtube_platform_id \
--description "Product walkthrough" \
--settings '{"TikTok":{"status":"PUBLIC_TO_EVERYONE"},"YouTube":{"title":"Product walkthrough","status":"unlisted"}}'
With --json, put the same object in the input file's settings property. SDK
calls accept settings as an object. For remote or local MCP, discover options
with taisly_platform_schema and pass settings to both taisly_posts_validate
and taisly_posts_create. The HTTP API accepts a JSON-encoded settings form field.
| Platform | Settings | Meaning |
|---|---|---|
| TikTok | status |
PUBLIC_TO_EVERYONE, MUTUAL_FOLLOW_FRIENDS, FOLLOWER_OF_CREATOR, or SELF_ONLY, subject to the account's available visibility options. |
| TikTok | comment_disabled, duet_disabled, stitch_disabled |
Boolean switches; true disables the interaction. |
| TikTok | brand_content_toggle |
Boolean; discloses a paid partnership promoting a third-party business. Cannot be combined with SELF_ONLY. |
| TikTok | brand_organic_toggle |
Boolean; discloses promotion of the creator's own business. Both brand switches may be enabled together. |
| TikTok | is_aigc |
Boolean; true enables the native AI-generated content label. Omit to keep existing behavior, or explicitly pass false. |
| YouTube | title |
Optional video title, up to 100 characters. Omit to use the post caption. |
| YouTube | status |
public, private, or unlisted. |
For example, a public TikTok post promoting your own business and an unlisted YouTube post with its own title can share one request:
{
"settings": {
"TikTok": {
"status": "PUBLIC_TO_EVERYONE",
"brand_organic_toggle": true,
"comment_disabled": false
},
"YouTube": {
"title": "Product walkthrough",
"status": "unlisted"
}
}
}
These settings work with --settings, --json, SDK calls, and both MCP servers,
for immediate and scheduled posts. They apply to all selected accounts on the
corresponding platform. Omitted fields keep the usual posting behavior. These
options apply only to the requested post. TikTok account restrictions still apply.
Every command prints JSON so agents can parse results without scraping terminal text.
MCP server
Taisly is published in the official MCP Registry as:
io.github.taisly/agent
Display name: Taisly Social Media Posting
Remote MCP endpoint:
https://app.taisly.com/mcp
The remote MCP server uses streamable HTTP and OAuth. Remote MCP tools can publish only from public videoUrl values because they cannot read local files from your machine.
Codex remote MCP setup:
codex mcp add taisly --url https://app.taisly.com/mcp
codex mcp login taisly
Claude Code remote MCP setup:
claude mcp add --transport http taisly https://app.taisly.com/mcp
Then ask Claude Code to verify the connection. If OAuth is needed, Claude Code can guide the browser login from the session. You can also authenticate explicitly with claude mcp login taisly if you want to complete the OAuth flow from the shell before using tools.
Taisly Agent Kit also includes a local stdio MCP server in the same package. Use local MCP when your agent needs to read local video files:
{
"mcpServers": {
"taisly": {
"command": "npx",
"args": ["@taisly/agent", "mcp"]
}
}
}
If you already use a manual API key, you can still pass TAISLY_API_KEY in the MCP server env block.
Codex local MCP setup:
codex mcp add taisly -- npx @taisly/agent mcp
Claude Code local MCP setup:
claude mcp add taisly -- npx @taisly/agent mcp
Then ask the agent:
Use the local Taisly MCP server you just added and run the Taisly agent setup start tool with agentId: "<agent-slug>".
Send me the login URL and wait for me to finish in the browser.
Then run the Taisly agent checkin tool with agentId: "<agent-slug>".
After checkin, run the Taisly auth status tool.
Tell me if Taisly is connected and ready. If not, tell me what failed.
Available MCP tools:
taisly_agent_setup_starttaisly_agent_checkintaisly_auth_statustaisly_platforms_listtaisly_platform_schemataisly_platform_connect_starttaisly_platform_connect_checktaisly_posts_validatetaisly_posts_createtaisly_posts_statustaisly_posts_listtaisly_reposts_listtaisly_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 setup --agent <agent-slug>
taisly checkin --agent <agent-slug>
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 other 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.mdexamples/claude-code/schedule-video.mdexamples/cursor/post-build-demo-video.mdexamples/post-video.shexamples/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 agent credential or API key.
- It does not bypass platform rules, account permissions, or media validation.
Current limits
posts:createuses the existing multipart/postAPI.posts:statusreads recent history because a single-post status endpoint is not available yet.posts:validateis local preflight; final validation still happens in Taisly.- Local MCP uses stdio transport. Remote MCP uses streamable HTTP at
https://app.taisly.com/mcp. - Remote MCP requires public video URLs; use local MCP or the CLI for local video files.
- Media upload reuse is planned later.
Links
- Taisly: https://taisly.com/en
- Agent Kit page: https://taisly.com/en/ai-agent-kit
- API docs: https://docs.taisly.com/en/docs
- npm package: https://www.npmjs.com/package/@taisly/agent
- GitHub repo: https://github.com/taisly/agent
- MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.taisly%2Fagent
- SEO guide: https://taisly.com/en/blog/ai-agent-social-media-posting-api
Taisly MCP 질문
Taisly MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'TAISLY_API_KEY=<YOUR_TAISLY_API_KEY>' agent -- npx -y @taisly/agent를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Taisly MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Taisly로 로컬 파일을 게시할 수 있나요?
네, 하지만 원격 서버는 사용자의 컴퓨터에 있는 파일을 읽을 수 없으므로 로컬 stdio MCP server 또는 CLI를 통해서만 가능합니다. 로컬 파일 액세스를 위해 npx @taisly/agent mcp를 실행하세요.
Taisly로 어떤 소셜 플랫폼에 게시할 수 있나요?
Instagram, TikTok, YouTube, X, Facebook에 게시할 수 있습니다. 게시물을 나중에 올라가도록 예약할 수도 있습니다.
게시하기 전에 동영상을 검증하려면 어떻게 해야 하나요?
동영상 경로, 대상 플랫폼 ID, 설명을 포함하여 taisly posts:validate를 실행하세요. 권장 워크플로우는 auth, platforms, validate, confirm, create, status 순서입니다.
에이전트가 게시 성공 여부를 확인할 수 있나요?
네, 반환된 historyId와 함께 taisly posts:status를 실행하세요. 해당 SKILL은 에이전트가 상태 확인을 위해 해당 ID를 저장하도록 안내합니다.