Taisly Agent Kit logo

Taisly Agent Kit

Community
taisly

Taisly Agent Kit: MCP server, CLI, SDK, and agent docs for publishing videos to TikTok, Reels, Shorts, X, and Facebook.

Publishertaisly
Repositoryagent
LanguageJavaScript
Forks
4
Stars
213
Available tools
13
Transport typestdio, streamable-http
Categories
LicenseMIT
Links
  • Connect tools to AI workflows

    Taisly Agent Kit exposes MCP capabilities that can be used by compatible AI clients and agents.

  • 13 available tools

    Browse the callable actions below, including names and descriptions when provided by the server.

  • Ready-to-copy setup

    Use the installation snippets to configure this server in your preferred MCP client.

  • Open source signals

    213 stars and 4 forks from the linked repository.

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

Taisly Agent Kit

Taisly MCP server Taisly MCP score

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.

Free AI-first posting

  • 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:

txt
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:

txt
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.

Install

bash
npm install -g @taisly/agent

Or run it without a global install:

bash
npx @taisly/agent help

Start the stdio MCP server:

bash
npx @taisly/agent mcp

For local development inside this repository:

bash
node packages/agent/src/cli.js help

Authentication

The easiest flow is to let your AI agent open the browser login for you. Use any short agent slug, for example claude-code, codex, cursor, windsurf, openclaw, hermes-agent, cline, or aider.

txt
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:

bash
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:

bash
taisly auth:status
taisly platforms:list

Connect a social account from an AI-agent flow:

bash
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:

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

Publish now:

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

Schedule for later:

bash
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:

bash
taisly posts:status --id <historyId>

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

MCP server

Taisly is published in the official MCP Registry as:

txt
io.github.taisly/agent

Display name: Taisly Social Media Posting

Remote MCP endpoint:

txt
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:

bash
codex mcp add taisly --url https://app.taisly.com/mcp
codex mcp login taisly

Claude Code remote MCP setup:

bash
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:

json
{
  "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:

bash
codex mcp add taisly -- npx @taisly/agent mcp

Claude Code local MCP setup:

bash
claude mcp add taisly -- npx @taisly/agent mcp

Then ask the agent:

txt
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_start
  • taisly_agent_checkin
  • taisly_auth_status
  • taisly_platforms_list
  • taisly_platform_schema
  • taisly_platform_connect_start
  • taisly_platform_connect_check
  • 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:

json
{
  "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:

bash
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

bash
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

js
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:

txt
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 agent credential or 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.
  • 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

Installation

TypingMind
{
  "mcpServers": {
    "agent": {
      "command": "npx",
      "args": [
        "@taisly/agent",
        "mcp"
      ]
    }
  }
}

Available Tools

  • taisly_agent_setup_start

    Start browser-based Taisly authentication for an AI agent. Returns a loginUrl that the user must open and approve before checkin.

  • taisly_agent_checkin

    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_status

    Check whether the Taisly API key is valid and count connected social accounts.

  • taisly_platforms_list

    List connected TikTok, Instagram, YouTube, X, Facebook, and other social accounts available to this API key.

  • taisly_platform_schema

    Get local posting constraints for a destination platform before validating or creating a post.

  • taisly_platform_connect_start

    Start browser-based connection for a social account. Returns a connectUrl that the user must open and approve in the browser.

  • taisly_platform_connect_check

    Check whether a social account connection started by taisly_platform_connect_start has appeared in Taisly.

  • taisly_posts_validate

    Validate a local video path, destination platform IDs, caption, and optional schedule before publishing.

  • taisly_posts_create

    Publish or schedule a video post through Taisly after the user explicitly confirms the media, destinations, caption, and schedule.

  • taisly_posts_status

    Fetch recent-history status for a Taisly post by historyId.

  • taisly_posts_list

    List recent Taisly post history for status checks and audits.

  • taisly_reposts_list

    List configured repost automations for connected social accounts.

  • taisly_reposts_create

    Create a repost automation from one connected account to one or more destination accounts.

Use Taisly Agent Kit MCP with multiple AI models

TypingMind connects MCP tools at the workspace level, so once Taisly Agent Kit is connected, you can use it with different AI models in TypingMind instead of setting it up separately for each model. You can run MCP locally on your device or connect to a remote MCP server URL.

Option 1: Use the local connector

Use this when the MCP server needs access to local files, apps, or private resources on your computer.

1

Open the MCP settings

In TypingMind, go to Settings, Advanced Settings, then Model Context Protocol and choose Setup Connector.

  1. Open TypingMind in your browser.
  2. Click the Settings icon.
  3. Go to Advanced Settings.
  4. Open the Model Context Protocol section.
  5. Click Setup Connector and choose This Device.
TypingMind MCP connector setup screen with This Device selected
2

Run the connector command

Choose This Device, copy the command from TypingMind, and run it in Terminal. Keep the process running while you use MCP.

  1. Copy the setup command shown by TypingMind.
  2. Open Terminal on macOS or Windows Terminal on Windows.
  3. Paste and run the command.
  4. Approve the package install if Terminal asks you to proceed.
  5. Keep the Terminal window running while using MCP tools.
3

Add Taisly Agent Kit as a server

When the connector status is Ready, click Edit Servers and paste the MCP server configuration.

  1. Wait until the connector status shows Ready.
  2. Click Edit Servers.
  3. Paste the Taisly Agent Kit MCP server configuration.
  4. Save the server list.
  5. Refresh if you want to confirm the connector is still ready.
TypingMind MCP settings showing active server and Edit Servers button
{
  "mcpServers": {
    "agent": {
      "command": "npx",
      "args": [
        "-y",
        "@taisly/agent"
      ]
    }
  }
}
4

Use it across models

Save the server list, open Plugins, enable the Taisly Agent Kit MCP tools, then select any supported AI model in TypingMind and use the tools in chat or assign them to an AI agent.

  1. Open the Plugins page in TypingMind.
  2. Enable the Taisly Agent Kit MCP tools.
  3. Start a chat and choose the AI model you want to use.
  4. Use the MCP tools in chat or assign them to an AI agent.
  5. Switch to another AI model whenever needed without reconnecting MCP.
TypingMind chat using enabled MCP tools with a selected AI model
Can you use Taisly Agent Kit to help me with this task?
Taisly Agent Kit
Sure. I read it.
Here is what I found using Taisly Agent Kit.

Option 2: Add an MCP server URL

Use this when Taisly Agent Kit is already hosted remotely or your team wants one shared connector that multiple users can access.

1

Open MCP connectors

In TypingMind, go to Plugins, open MCP connectors, then choose Add URL.

  1. Open TypingMind in your browser.
  2. Go to Plugins.
  3. Open MCP connectors.
  4. Click Add URL.
TypingMind Add Custom MCP Server URL form
2

Paste the server URL

Enter https://app.taisly.com/mcp in the Server URL field. Add a connection name, description, icon, custom HTTP headers, or OAuth client settings if the server requires them.

  1. Paste https://app.taisly.com/mcp into the Server URL field.
  2. Enter a connection name for Taisly Agent Kit.
  3. Add a description and icon if you want it to be easier to identify.
  4. Add custom HTTP headers or OAuth client details if the server requires authentication.
3

Create the connection

Click Create connection, then return to the Plugins list and confirm the new MCP connection is active.

  1. Click Create connection.
  2. Return to the MCP connectors list.
  3. Confirm the Taisly Agent Kit connection appears as active.
  4. Refresh the plugin list if the connection does not appear immediately.
4

Switch models without reconnecting

Start a chat with your preferred model, enable the Taisly Agent Kit tools from Plugins, and switch to another model whenever needed. The MCP connection stays available to the TypingMind workspace.

  1. Start a new chat in TypingMind.
  2. Select the AI model you want to use.
  3. Enable the Taisly Agent Kit tools from Plugins.
  4. Ask the model to use the tool when needed.
  5. Switch to another AI model and reuse the same MCP connection.
TypingMind chat using enabled MCP tools with a selected AI model
Can you use Taisly Agent Kit to help me with this task?
Taisly Agent Kit
Sure. I read it.
Here is what I found using Taisly Agent Kit.

Frequently asked questions

What is the Taisly Agent Kit MCP server used for?

Taisly Agent Kit is an MCP server that lets compatible AI clients connect to external tools and context. In TypingMind, you can add this MCP server once and make its tools available in your AI workspace.

Can I use Taisly Agent Kit MCP with multiple AI models in TypingMind?

Yes. TypingMind connects MCP tools at the workspace level, so you can use Taisly Agent Kit with different AI models such as Claude, ChatGPT, Gemini, or other models you have configured in TypingMind without setting up the MCP server separately for each model.

Why use Taisly Agent Kit MCP with TypingMind?

TypingMind is one of the best frontends for LLM chat because it brings multiple AI models, prompts, plugins, AI agents, API keys, and MCP tools into one workspace. With Taisly Agent Kit connected, you can use its MCP tools across your preferred models while keeping your chat workflow organized in TypingMind.

How do I connect Taisly Agent Kit MCP to TypingMind?

Taisly Agent Kit can be connected in TypingMind with the local MCP connector or by adding a remote MCP server URL. Use the local connector when the server needs access to files, apps, or private resources on your device, and use a server URL when the MCP server is hosted remotely.

What tools does Taisly Agent Kit MCP provide in TypingMind?

Taisly Agent Kit exposes 13 MCP tools that can be enabled from the TypingMind Plugins page and used in chat or assigned to AI agents.

Do I need to share my API keys with TypingMind to use Taisly Agent Kit MCP?

No. TypingMind is local-first and lets you keep your model providers, API keys, prompts, and MCP configuration under your control. If Taisly Agent Kit requires authentication, add the required headers, OAuth settings, or local configuration for that MCP server when you create the connection.

Related MCP Servers

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇