Taisly MCP

Taisly connects AI agents to your social accounts. Its remote MCP tools can discover accounts, start social-account connections, validate videos, publish now or schedule for later, inspect posting history, and manage automatic repost rules.

Connect once, reuse the connection

If Taisly MCP tools are already available in your conversation, use them directly. Call taisly_auth_status and taisly_platforms_list to check access. Do not install a package, start a local server, run setup/checkin commands, or request an API key for an existing remote MCP connection.

If Taisly is not connected, add it to a client that supports remote MCP over Streamable HTTP and OAuth:

Name: Taisly
Server URL: https://app.taisly.com/mcp
Authentication: OAuth

Finish Taisly sign-in and consent in your browser, then enable the connection in the conversation. An agent may help configure its client, but some clients require you or a workspace administrator to add the connection in settings. A prompt alone cannot grant access or bypass client restrictions.

After connection, run these read-only tools:

1. taisly_auth_status: verify the signed-in Taisly account and plan limits.
2. taisly_platforms_list: show connected social accounts and their exact platform IDs.

If no social accounts are connected, say so. Do not treat that as an authentication failure or reinstall the connection.

Client setup

Claude

Add a custom connector in Claude with the server URL above and complete OAuth. Enable Taisly in the conversation. Workspace policies may require administrator approval.

Open the Taisly connector dialog

Claude Code

Add the remote connection, then open /mcp in Claude Code to authenticate when prompted:

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

This registers a remote server; it does not install the Taisly package. An existing connection can be reused.

Codex

Add Taisly in Codex MCP settings with the server URL and authenticate, or use the installed Codex CLI:

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

Use an existing connection if one is already configured. Follow your client's instructions for refreshing tools or starting a new conversation after adding a server.

Codex MCP documentation

ChatGPT

Use ChatGPT's custom MCP connection flow, enter the Taisly server URL, select OAuth, and approve access. Enable the resulting connection in your conversation. Availability depends on account and workspace policies. This does not require the Taisly CLI or a manually copied Taisly API key.

Current ChatGPT connection instructions

Other clients and content tools

Use the client's documented remote MCP and OAuth configuration. Client-specific commands and configuration schemas are not interchangeable. If your client cannot connect, explain that limitation and suggest a compatible client. Do not silently replace MCP with a package installation or API-key flow.

A content generator or editor is not necessarily an MCP client. Create or export the video there, then use a compatible agent connected to Taisly for publishing. For example, Gemini CLI has its own MCP configuration; that does not establish that every Gemini chat has the same capability.

First prompt

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

Tools and capabilities

Only call tools actually advertised by the connected server. taisly_agent_setup_start and taisly_agent_checkin belong to the separate local package and are not remote MCP authentication tools.

Connect a social account

First list existing accounts. If the requested account is missing, ask whether the user wants to connect it. Call taisly_platform_connect_start for a supported platform and show its connectUrl. The user completes platform authorization in the browser. Then call taisly_platform_connect_check and list accounts again.

Connecting a social account is separate from authorizing the agent to access Taisly. Neither step requires collecting a social-network password in chat.

Publish or schedule a video

1. Check access and list accounts. Match the user's destinations to exact returned IDs; do not guess IDs or choose the first account automatically.
2. Obtain a direct public video URL, caption, and optional schedule. Read taisly_platform_schema for relevant constraints.
3. Call taisly_posts_validate.
4. Show the video, caption, exact accounts, and schedule to the user for confirmation.
5. Only after approval call taisly_posts_create with confirmed: true.
6. Save the returned historyId. An accepted request is not proof of publication. For immediate posts, check taisly_posts_status: PENDING means processing, SUCCESS means published, and FAILED means failed, separately for each destination.
7. For scheduled posts, report the scheduled date and history ID, not that the video has already been published.

The scheduled field accepts an ISO datetime with timezone or Unix milliseconds. Resolve ambiguous dates and timezones before asking for approval.

Video URL requirements and publishing examples

History and reposts

Use taisly_posts_list to inspect history and taisly_posts_status for a particular history ID. Do not call create again just because a request timed out; check history before risking a duplicate.

For automatic reposts, list accounts and existing rules first. Show the exact source and destination accounts and obtain approval before calling taisly_reposts_create. Do not create a rule as a connection test. Repost automation and scheduling a single video are separate features.

Access and troubleshooting

OAuth grants access to the signed-in user's Taisly account. The remote connection uses bearer tokens obtained by the client, not keys pasted into chat. Supported permissions are mcp:read and mcp:write; write operations require write permission. Never print credentials or put them in a prompt, URL, log, or repository.

If access expires or is revoked, use the client's OAuth reconnect or authentication action. Do not install the CLI or ask for an API key as an automatic fallback. If a tool is missing after connection, refresh the server's tools or start a new conversation according to the client's instructions.

Remote MCP currently publishes videos from publicly reachable URLs. It cannot read local paths or private chat attachments. A file attached to a cloud conversation is not automatically a downloadable public URL. Ask for a suitable URL, or discuss the separate local-file workflow with the user.

Developer alternatives

The REST API uses API keys and HTTP requests for custom integrations. The SDK, CLI and local MCP package can work with files available to a local process. These are optional alternatives, not prerequisites for remote MCP.

Machine-readable version of this guide: mcp.txt. Full documentation index: llms.txt.