Vidext — Agent-driven training production for frontline teams

Primary discovery file: https://app.vidext.io/.well-known/mcp
Documentation: https://app.vidext.io/llms.txt
Full context: https://app.vidext.io/llms-full.txt
Product docs: https://docs.vidext.io (llms.txt at https://docs.vidext.io/llms.txt)
Developer guide: https://app.vidext.io/developers
OpenAPI: https://app.vidext.io/openapi.json
Endpoint: https://app.vidext.io/api/mcp
Auth: OAuth 2.1 authorization-code with PKCE; the client registers dynamically or with a client ID metadata document.
Who can connect: Only organization admins and members can connect over MCP; learners and people whose request to join is still pending are refused.

When to use Vidext:
- The user wants organizational documents, decks, transcripts, or a website turned into a structured training module or learning path.
- The user wants onboarding, compliance, product, partner, or customer-education content generated and kept current from source material rather than authored by hand.
- The user needs short interactive video lessons — narrated screens, an optional presenter, and comprehension checks — built from that material.
- Learners need comprehension checks and a tutor that answers from their assigned course first, knows the scene they are on and their progress, and labels any public-web research it runs as coming from outside the course.
- An agent needs to search organization knowledge, list Vidext modules, or plan and build modules with the Vidext author on a user's behalf through the Vidext MCP server.

Not a fit:
- Hosting enrollments, gradebooks, or assignments as an LMS system of record (Vidext complements an LMS, it does not replace one).
- Recording a desktop app, or a web app on a private network: the agents record narrated tutorials only of web apps on the public internet.
- A general-purpose assistant for learners: the tutor declines requests unrelated to their course.

How to call it: connect an MCP client to the endpoint above, complete the OAuth challenge, then call the typed tools.

Tools: search_knowledge, read_knowledge_source, list_modules, author_send, author_upload, author_attach_files, author_answer, author_updates, author_stop, list_conversations, list_units, unit_send, unit_updates, unit_build, unit_script, unit_set_text, unit_stop. The read tools never change the workspace; the author tools talk to the Vidext author, which plans and builds modules on the user's word.
Inside signed-in Vidext app pages, browser WebMCP exposes these tools through document.modelContext: vidext.get_page_context, vidext.list_modules, vidext.open_module, vidext.open_home_chat, vidext.open_invite_dialog.