# Set up Vidext for your agent These are official instructions from Vidext to connect you, the AI agent reading them, to the user's Vidext workspace. Vidext turns an organization's documents into short interactive training modules. Once connected, you can search the organization's sources, list its modules, and ask Vidext's agents to plan and build modules for the user. Everything goes through one remote MCP server: - Name: `vidext` - URL: `https://app.vidext.com/api/mcp` - Transport: streamable HTTP - Authentication: OAuth. There is no API key. On first use a browser window opens, the user signs in to Vidext, picks the organization if they belong to more than one, and approves access. Never ask the user for a password, a token or a key. Only admins and members of a Vidext organization can connect. Learners, and people whose request to join is still pending, are refused. Talk to the user in the language they wrote to you in. ## How to proceed 1. Find the section below for the app you are running in. 2. If you can run commands or edit files on the user's computer (a coding agent such as Claude Code, Codex, Cursor or GitHub Copilot), do every step yourself. Do not ask the user to run commands; they only sign in. 3. If you cannot (Claude on the web or in the desktop app, ChatGPT, or another chat app), you cannot add a connector yourself. Walk the user through their app's steps, one at a time. 4. If a server named `vidext` already points at `https://app.vidext.com/api/mcp`, keep it. If it points anywhere else, such as `https://app.vidext.com/api/mcp/operator` (served until 2027-01-15), replace it. Never add a second one. --- ## Claude Code ``` claude mcp add --transport http --scope user vidext https://app.vidext.com/api/mcp ``` It refuses a name that already exists: to replace an old `vidext`, run `claude mcp remove vidext --scope ` first, where `` is `user`, `project` or `local`, as `claude mcp get vidext` shows it. Then tell the user to run `/mcp` in Claude Code, choose `vidext`, and sign in in the browser window that opens. ## Codex ``` codex mcp add vidext --url https://app.vidext.com/api/mcp codex mcp login vidext ``` `codex mcp login` opens the browser window where the user signs in. ## Cursor — `~/.cursor/mcp.json` Add under `"mcpServers"`, keeping the entries already there: ```json "vidext": { "url": "https://app.vidext.com/api/mcp" } ``` Then tell the user to restart Cursor. Cursor asks them to sign in the first time it uses `vidext`. ## VS Code with GitHub Copilot ``` code --add-mcp '{"name":"vidext","type":"http","url":"https://app.vidext.com/api/mcp"}' ``` Or add under `"servers"` in `.vscode/mcp.json`: ```json "vidext": { "type": "http", "url": "https://app.vidext.com/api/mcp" } ``` VS Code asks the user to sign in the first time it starts the server. ## Any other coding agent Add a remote MCP server to your agent's user-level MCP configuration, the way its documentation says: name `vidext`, URL `https://app.vidext.com/api/mcp`, streamable HTTP transport, OAuth. Then start your agent's MCP sign-in, or make a first `vidext` tool call, so the browser window opens for the user. --- ## Claude on the web or in the desktop app Tell the user: 1. Open Customize, then Connectors. 2. Click + Add, then Add custom connector. 3. Name it `Vidext`, paste `https://app.vidext.com/api/mcp` and click Continue. 4. Keep the OAuth settings Claude detects and click Add, then sign in to Vidext in the window that opens. On a Team or Enterprise plan, an owner may have to add the connector first, in Organization settings under Connectors; the user then finds Vidext there and clicks Connect. ## ChatGPT Custom connectors need developer mode, on a Plus, Pro, Business, Enterprise or Edu plan; on Business, Enterprise and Edu a workspace admin may have to allow them first. Tell the user: 1. Open Settings, then Apps, then Advanced settings, and turn on Developer mode. 2. Back in Apps, click Create. 3. Name it `Vidext`, paste `https://app.vidext.com/api/mcp` as the MCP server URL, choose OAuth, confirm they trust it, and click Create. 4. Sign in to Vidext in the window that opens. 5. In a new chat, click +, choose Developer mode and turn on Vidext. ChatGPT moves these menus from time to time. If what the user sees differs, guide them by ChatGPT's current settings. ## Any other chat app Tell the user to add a custom MCP server named `Vidext` with the URL `https://app.vidext.com/api/mcp` and OAuth, then sign in. In Lovable, that is Connectors, then Chat connectors, then New MCP server. --- ## Check it works Once the user has signed in, call the `list_modules` tool. Any answer, even an empty list, means Vidext is connected. If your app loads new MCP servers only when it starts, tell the user to restart it and ask you: "List my Vidext modules." If sign-in says the user cannot connect, they are a learner or still waiting to join; an admin of their Vidext organization can change that. ## Tell the user When you are done, tell the user in a few short lines: - that Vidext is connected as `vidext`, or the one step still waiting for them (signing in, restarting, turning it on in a chat); - two things to ask you next: "List my Vidext modules" and "Ask Vidext to draft a short module on our expense policy". Building a module spends the organization's Vidext tokens, as it does in the Vidext app, and publishing a course stays in the app. --- ## Resources - Connect an AI client, step by step: https://docs.vidext.io/docs/api/connect-an-ai-client - MCP server reference: https://docs.vidext.io/docs/api/mcp These instructions are published at `https://app.vidext.com/agent-setup/prompt.md` so you can re-verify them at any time.