Quickstart: connect an AI client

One URL serves every client:

https://app.vidext.com/api/mcp/operator

There is no API key to create. The client's first request is refused with an OAuth challenge, and the client opens your browser to authorize. The same instructions, with a copy button, are in the app at Settings → MCP.

Before you startCopy Anchor Link

• You need an admin or member role in the organization. Learners and people whose access request is still pending cannot connect.
• Your client must speak MCP protocol 2026-07-28 over streamable HTTP with OAuth. Older clients are refused with JSON-RPC error -32022; update the client if you see it.

Add the serverCopy Anchor Link

claude mcp add --transport http vidext-operator https://app.vidext.com/api/mcp/operator

Keep the server name vidext-operator. It is the name the server reports and the one the setup page uses.

AuthorizeCopy Anchor Link

On first use, your browser opens Vidext's sign-in and a consent screen. If you are an admin or member in more than one organization, you choose one; with only one, it is picked for you. The connection stays bound to that organization, even if you later switch workspace in the app. To work in another organization, authorize again. See Authentication.

Verify it worksCopy Anchor Link

Ask your client:

List my Vidext modules.

A list_modules call that returns your modules, or an empty list, means you are connected.

Add the docs server tooCopy Anchor Link

The public Docs MCP server needs no authorization and lets the same client answer questions about Vidext from these pages:

claude mcp add --transport http vidext-docs https://app.vidext.com/api/mcp/docs

See Docs MCP server.

NextCopy Anchor Link