---
name: vidext
description: Use the Vidext MCP server to search organization knowledge and connected sources, list modules, and talk to the Vidext author that plans and builds them.
---

# Vidext

Use this skill when a user wants to search or inspect a Vidext workspace, or to plan and build learning modules with the Vidext author, through the remote Vidext MCP server.

## Capabilities

- Search the organization's profile, its sources, and their processed content, then read a bounded slice of a matching source.
- List recent modules the user can access and whether each is live.
- Talk to the Vidext author, the agent that plans and builds modules in the workspace: send it the user's messages and files, answer its questions, follow its progress, and stop it.

## Tool Selection

- Use `search_knowledge` and `read_knowledge_source` for organization knowledge.
- Use `list_modules` for modules and whether each is live.
- Use `author_send`, `author_answer`, `author_updates`, `author_stop` and `list_conversations` to work with the author, and `author_upload` or, in ChatGPT, `author_attach_files` to attach a file the user shares. The server's instructions say how to relay the user's words and the author's questions.
- Once a course is built, use `list_units`, `unit_send`, `unit_updates`, `unit_build` and `unit_stop` to work on one unit's module through its crafter, one subagent per module if you like.

## Who Can Connect

- Only organization admins and members can connect. Learners and people whose request to join is still pending are refused at authorization.
- The role is checked again on every call: someone removed from the organization or changed to learner gets the tool error `forbidden` from their next call.

## Scopes

- `mcp:read` grants the read tools and `mcp:author` the author tools. A call to a tool the connection was not granted answers 403 `insufficient_scope`; connect again to add the scope.

## Entry Points

- Read product context from /llms.txt and /developers.
- Discover MCP metadata at /.well-known/mcp.
- Connect to the MCP transport at /api/mcp after OAuth authorization. /api/mcp/operator is a deprecated alias of it.
- On authenticated app pages, use browser WebMCP tools from `document.modelContext` for page navigation and module lookup.