Agents roadmap
Public roadmap for YT2Text agent support, from REST API and skill files to SDKs and MCP.
By YT2Text Team • Published March 30, 2026 • Updated April 29, 2026
Agents roadmap
YT2Text is API-first today. Agents can already integrate over HTTPS using the public skill files, the REST API, and the remote MCP server.
Live now
- public agent skill:
https://yt2text.cc/skill.md - metadata:
https://yt2text.cc/skill.json - JSONL discovery:
https://yt2text.cc/skill.jsonl - landing page:
https://yt2text.cc/agents - public API:
https://api.yt2text.cc/api/v1 - remote MCP server:
https://mcp.yt2text.cc/mcp - local MCP adapter:
mcp/yt2text-mcp(stdio)
Phase 1: solid API-first onboarding
Current priority:
- make the skill files easy to discover
- document plan gates clearly
- keep examples curl-first and operational
- ensure agents can submit, poll, and fetch reliably
Phase 2: first-party SDKs
Priority order:
- JavaScript/TypeScript
- Python
- Swift
- Kotlin
The first SDK releases should cover:
- API-key auth
- video submission
- polling helpers
- typed response models
- retry/backoff
- error normalization
Phase 3: MCP (live)
The remote MCP server is now live at https://mcp.yt2text.cc/mcp.
Tools exposed:
process_youtube_videoget_video_job_statusget_video_resultsummarize_youtube_videoexport_video_markdown
Auth is per-request: Authorization: Bearer sk_... (the user's yt2text API key). No server-side key storage.
Plan gates apply identically to REST: Plus minimum, Pro for batch / custom prompts / PDF / chat / infographics.
Local stdio adapter is also published in mcp/yt2text-mcp for embedded use.
Phase 4: platform hardening
Ongoing work to make the integration layer stronger:
- webhook secret management on the public API
- delivery logging and retry semantics
- stable batch completion events
- idempotency guidance
- clearer quota and usage reporting
Positioning
What we can say now:
- YT2Text works with agents today over the public REST API
- public skill files are available
- the remote MCP server is live at
mcp.yt2text.cc/mcp - first-party SDKs are planned
- a native n8n node is planned
What we should not say yet:
- official SDK packages are already published
- batch completion webhook delivery is fully productized