Upload and publish videos with Taisly MCP

Taisly MCP lets Claude, Claude Code, Codex, ChatGPT, and other AI agents publish short-form videos to the social accounts you connected in Taisly.

The most important choice is where your video file lives. Remote MCP works with a public video URL. Local MCP and the Taisly CLI work with files on your computer.

Choose the right setup

Hosted agents

Remote MCP

Use Taisly from Claude web, ChatGPT, and other hosted MCP clients when your video is already available by public HTTPS URL.

https://example.com/video.mp4Open MCP guide

Local agents

Local MCP

Let Claude Code, Codex, Cursor, and local runtimes publish files they can read from your computer or project workspace.

./launch.mp4Use local MCP

Shell workflows

Taisly CLI

Run repeatable posting commands, validate payloads, and script local publishing flows through the official Agent Kit package.

taisly posts:create --video ./launch.mp4Install Agent Kit

Backend integrations

REST API

Build direct server-side integrations with API keys, multipart video upload, platform IDs, history, schedules, and repost rules.

multipart/form-data uploadExplore API

If you drag a video into Claude web or another cloud chat, that attachment is not automatically a public video URL that Taisly can fetch. In that case, either provide a direct public URL or use local MCP or CLI from an environment that can read the file.

Remote MCP

Remote MCP is the easiest path for web-based agents and hosted connectors.

Endpoint:

https://app.taisly.com/mcp

Claude connector install link:

Manual Claude setup:

1. Open Claude settings.
2. Go to Customize > Connectors > Add Connector.
3. Name the connector Taisly.
4. Use https://app.taisly.com/mcp as the connector URL.
5. Enable Taisly inside a conversation from the connectors menu.

For Team or Enterprise workspaces, an owner or admin may need to add the connector for the workspace first.

What to give your agent

For remote MCP, give the agent a direct public video URL and ask it to use the Taisly MCP tools.

Use the Taisly MCP connector to publish this video:

Video URL: https://example.com/launch.mp4
Caption: Launch day. Short demo, big update.
Destination: my connected TikTok account

First list my connected Taisly platforms and match the correct destination account.
Then validate the post.
Before publishing, show me the final video URL, caption, destination account, and schedule.
Only call the create post tool after I confirm.

The agent should:

1. Check that Taisly is connected.
2. List your connected platforms.
3. Match your requested destination to the exact Taisly platform ID.
4. Validate the video URL, caption, destination, and optional schedule.
5. Ask for your confirmation.
6. Publish or schedule the post.
7. Return the Taisly history ID so you can check status later.

Public video URL requirements

Remote MCP can fetch only public video URLs.

Your videoUrl should:

• Use http:// or https://. HTTPS is recommended.
• Point directly to a downloadable video file.
• Be reachable without cookies, login, VPN, or an interactive confirmation page.
• Use a supported video type such as mp4, mov, webm, avi, mkv, flv, mpeg, or mpg.
• Be 500MB or smaller.

Your videoUrl should not:

• Point to localhost, a private network, or a local file path.
• Include a username or password in the URL.
• Require a browser session to download.
• Redirect through too many pages before reaching the video.

Short-form vertical video is recommended. Different social platforms may also apply their own limits for duration, format, caption length, privacy settings, and daily posting volume.

Local files

Use local MCP or the Taisly CLI when the video is on your computer.

Local MCP example:

npx -y @taisly/agent mcp

CLI example:

npm install -g @taisly/agent
taisly setup --agent claude-code
taisly checkin --agent claude-code
taisly posts:create --video ./launch.mp4 --platforms platform_id_1 --description "Launch day"

Use this path for prompts like:

• "Post ./launch.mp4 from this project."
• "Publish the video in my Downloads folder."
• "Use this local file that Claude Code or Codex can see."

Claude Code

Claude Code can use either remote MCP or local MCP.

Remote MCP:

claude mcp add --transport http taisly https://app.taisly.com/mcp

Local MCP:

claude mcp add --transport stdio taisly -- npx -y @taisly/agent mcp

Use remote MCP when you have a public video URL. Use local MCP when Claude Code needs to read a local video file.

Codex

Codex can use remote MCP or the Taisly CLI.

Remote MCP:

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

CLI setup:

npm install -g @taisly/agent
taisly setup --agent codex
taisly checkin --agent codex

Use remote MCP when you have a public video URL. Use CLI or local MCP when Codex needs to use a local video file.

Troubleshooting

The agent says Taisly cannot read my local file

Remote MCP runs outside your computer and cannot access paths like ./video.mp4, /Users/me/video.mov, or C:\Videos\video.mp4.

Use local MCP or the Taisly CLI for local files, or upload the video somewhere that gives you a direct public URL.

My Google Drive, Dropbox, or cloud storage link fails

The URL must lead directly to the video file. Links that open a preview page, require login, or require cookies may fail.

Use a direct download URL when possible.

Taisly says the URL is not public

Remote MCP blocks local and private network addresses for safety. Use a public URL that Taisly can fetch from the internet.

The video is too large

The current upload limit is 500MB. Compress the video or use a shorter export.

I do not see the right social account

Ask the agent to list your connected Taisly platforms. If the account is missing, connect it in Taisly first, then ask the agent to check again.

The agent is ready to publish without asking me

Ask the agent to stop and show the final video URL, caption, destination account, and schedule first. Taisly MCP is designed for explicit confirmation before creating a live post.

Safe publishing checklist

Before the agent creates a post, confirm:

• The video URL or local file is correct.
• The destination account is correct.
• The caption is correct.
• The schedule is correct, or the post should go live now.
• The agent is using the connected Taisly account you expect.

After publishing, save the returned Taisly history ID and ask the agent to check post status when needed.