# taisly/agent [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/taisly/agent  
**GitHub Stars:** 219  
**npm Downloads (last month):** 415  
**Views:** 3  
**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 the taisly/agent MCP server does

The taisly/agent MCP server connects an AI-agent workflow to Taisly's short-form video publishing service. It lets an agent inspect authentication state, find connected social accounts, start or check account connections, validate a video payload, create a post, and retrieve the post's status.

Supported publishing destinations listed in the project include TikTok, Instagram Reels, YouTube Shorts, X, and Facebook. The workflow is intended for agents that handle planning, captions, or campaign logic while Taisly performs the platform-specific publishing work. Posts can be published immediately or scheduled for a later time.

## How it works

The package provides both a local stdio MCP server and access to Taisly's hosted MCP endpoint. The local server is useful when the agent needs to work with a video file stored on the same machine. The hosted endpoint uses streamable HTTP and OAuth, and accepts only public `videoUrl` values because it cannot read local files.

A recommended workflow is to authenticate, inspect available platforms, validate the post, obtain explicit confirmation, create the post, and retain the returned `historyId` for later status checks. The package also includes an agent skill describing this sequence, plus a Codex plugin manifest that points to the skill and the remote MCP service.

## Setup and configuration

Install the package globally with npm or run its MCP entry point through `npx`. The local MCP command is:

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

Authentication can be completed through the browser-based setup flow. That process stores a local Taisly agent credential for later CLI and MCP use. As an alternative, create a key in Taisly Settings and provide it as `TAISLY_API_KEY`. `TAISLY_CONFIG_HOME` can be used to place the local configuration in a separate directory for CI, tests, or isolated agent profiles.

The remote endpoint is `https://app.taisly.com/mcp`. Codex and Claude Code setup examples are provided in the repository for both remote and local MCP use. The package is free to install; the README says paid plans apply to higher-volume publishing, larger account sets, and automatic repost workflows.

## Tools and capabilities

The taisly/agent MCP server lists tools for:

- Starting agent setup and completing check-in
- Checking Taisly authentication status
- Listing connected platforms and retrieving platform schemas
- Starting and checking social-account connections
- Validating video posts before publication
- Creating immediate or scheduled posts
- Checking a post by its returned history identifier

The associated CLI prints JSON for command results, which is suitable for agent workflows that need structured output. Supported connection slugs are `instagram`, `tiktok`, `youtube`, `x`, and `facebook`.

## Limitations and notes

Connected social accounts are required before publishing. Remote MCP use cannot access local video paths, so videos must be available through public URLs in that mode. The project documentation describes browser authentication and manual API-key authentication, but does not state that every client uses the same authentication flow.

The taisly/agent MCP server is focused on video publishing rather than content generation: the agent remains responsible for creating the content, captions, and campaign decisions. The README does not specify an open-source license.

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