taisly-social-media-posting
VerifiedConnect AI agents to Taisly through MCP to publish and schedule videos, inspect history, and manage reposts.
Taisly social posting
Full documentation: https://docs.taisly.com/docs/mcp
Remote MCP
Prefer the existing Taisly MCP connection. OAuth already provides access; do not install the package, request an API key, or run local setup/checkin tools when remote MCP is available.
If it is not connected, help the user add https://app.taisly.com/mcp as a remote Streamable HTTP MCP server with OAuth in a compatible client. Client settings or workspace policies may require human action. After authorization, refresh tools according to the client's instructions.
- Call
taisly_auth_statusandtaisly_platforms_list. An empty account list is not a login failure. - Match the user's requested destinations to exact returned platform IDs.
- For a missing social account, get permission to start connection, show the
connectUrlfromtaisly_platform_connect_start, wait for browser approval, then check connection. - Read
taisly_platform_schemaand validate the public video URL, caption, destinations and schedule withtaisly_posts_validate. - Show the final video, caption, exact accounts and schedule. Obtain user approval before calling
taisly_posts_createwithconfirmed: true. - Save
historyIdand checktaisly_posts_status. Accepted is not published; report each destination'sPENDING,SUCCESSorFAILEDresult accurately. A scheduled post has not yet been published. - List existing repost rules and confirm source and destination accounts before creating a requested rule.
Only call tools advertised by the server. Remote MCP does not expose taisly_agent_setup_start or taisly_agent_checkin. Never print credentials. If access expires, use the client's OAuth reconnect action, not CLI installation or an API-key fallback. Do not blindly retry creation after a timeout; check history first.
Developer and local-file alternatives
Remote MCP cannot read local files or private chat attachments. Ask for a public downloadable video URL. If the user explicitly needs a local-file workflow, explain the optional local MCP or CLI package before installing anything.
Package guide: https://docs.taisly.com/en/docs/agents/agent-kit REST API: https://docs.taisly.com/en/docs/api
API keys and the npm package are developer alternatives, not prerequisites for remote MCP.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |