These docs are an early preview — some sections are still being expanded.
Vidext Docs

Quickstart: connect an AI client

Connect Claude Code, Claude.ai, Cursor, or Codex to the Vidext Operator MCP server in five minutes.

One URL powers every client:

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

No API key, no pre-registration — the first unauthenticated request triggers OAuth in your browser. Pick your client:

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

Then run /mcp inside Claude Code to complete the browser authorization. A registration that reports "Needs authentication" is healthy — it just has not been authorized yet.

Settings → Connectors → Add custom connector. Name it Vidext Operator, set the URL above, save, then enable it in a new chat. The connector syncs to Claude Desktop and mobile.

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "vidext-operator": {
      "url": "https://vidext.com/api/mcp/operator"
    }
  }
}
codex mcp add vidext-operator --url https://vidext.com/api/mcp/operator

Authorize

On first use, your browser opens Vidext's sign-in. If you belong to multiple organizations, you choose which one this connection is scoped to — the token stays bound to that organization. See Authentication for the full flow.

Verify it works

Ask your client:

List my Vidext modules.

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

Next

Your first agent run

Build a real module end to end from your client.

Tool reference

Everything the connection can do.

Last updated on

On this page

Authorize
Verify it works
Next