# taisly/agent [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/taisly/agent  
**GitHub Stars:** 222  
**npm Downloads (last month):** 754  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/taisly-agent

## Description
Taisly Agent Kit MCP server for AI agent social media video publishing. Discover connected accounts, validate videos, publish or schedule posts to TikTok, Instagram Reels, YouTube Shorts, X, and Facebook through Taisly. Install: npx -y @taisly/agent mcp. Requires a Taisly API key and connected accounts.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "agent": {
    "command": "npx",
    "args": ["-y","@taisly/agent"],
    "env": {
      "TAISLY_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `TAISLY_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What taisly/agent MCP server does

taisly/agent gives AI agents a JSON-oriented interface for short-form video publishing through Taisly. It can inspect authentication, list connected social accounts, start and check account connections, validate a video payload, create a post, schedule it for a future time, and retrieve the status of a published post.

Supported destinations include TikTok, Instagram, YouTube, X, and Facebook. The workflow uses the platform account identifiers returned by Taisly, allowing one video and description to target multiple connected accounts. Platform-specific publishing options can be discovered before submission, including TikTok visibility and interaction controls and YouTube settings.

The package is intended for agents that handle content planning, caption generation, or campaign logic while Taisly performs account connections and publishing execution.

## How it works

The recommended sequence is authentication, platform discovery, validation, explicit confirmation, creation, and status checking. Agents can first call the authentication and platform-list operations, then use the platform schema operation to learn accepted settings. Validation checks the proposed video and destination configuration before a create operation is made.

A successful create operation returns a history identifier. Store that identifier and pass it to the status operation when the agent needs to inspect the resulting post. Posts can be created immediately or assigned a scheduled timestamp. Settings are grouped by destination platform and passed as a structured object.

Taisly offers a remote MCP endpoint at `https://app.taisly.com/mcp`, where OAuth handles access. The npm package also starts a local stdio MCP process for local-file, SDK, CLI, or isolated automation workflows.

## Setup and configuration

For remote MCP, add the Taisly endpoint through a client’s remote MCP and OAuth settings. The package is not required for this connection, and authorization may require a user or administrator approval.

For local use, install `@taisly/agent` globally or invoke it with `npx`, then run:

```bash
npx @taisly/agent mcp
```

The local workflow can authenticate through browser-based setup, which stores an agent credential locally. A manual alternative is to create a Taisly API key and expose it as `TAISLY_API_KEY`. The default local credential location is `~/.taisly/config.json`; `TAISLY_CONFIG_HOME` can select another configuration directory for CI, tests, or separate agent profiles.

Connected accounts must be authorized before publishing. Account connection flows support Instagram, TikTok, YouTube, X, and Facebook.

## Tools and capabilities

- Check Taisly authentication status.
- List connected social accounts and platform identifiers.
- Start and verify a social-account connection.
- Discover destination-specific posting settings.
- Validate a local video and its publishing payload.
- Publish immediately or schedule a video post.
- Retrieve post status using a returned history identifier.

## Limitations and notes

Publishing depends on connected accounts and valid Taisly access. The recommended agent skill asks for explicit confirmation before creating a live post. Free installation does not mean every workflow is unlimited: higher-volume publishing, larger account sets, and automatic repost workflows are associated with paid plans. OAuth users should reconnect through OAuth when remote access expires rather than switching connection methods.

_Full upstream README: https://allmcps.com/mcp/taisly-agent/readme_