Environments and base URLs

Production

https://vidext.com

Everything in these docs uses production. The MCP endpoint is:

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

The endpoint lives on the app domain by design — one host serves the app, the MCP server, and the discovery layer, so OAuth, metadata, and tools always agree.

There is no non-production MCP endpoint

MCP is a production-only surface. https://staging.vidext.com/api/mcp/operator and http://localhost:3000/api/mcp/operator do not exist and will return 404 — running the Vidext app locally does not give you a local MCP server.

https://staging.vidext.com still mirrors the app for internal validation. It is not a place to integrate against, demo from, or buy on; data and pricing there are informational, and it serves no MCP.

Point every client at the production URL above, on every machine.

The Operator MCP surface has one upstream endpoint. Pass module IDs as typed tool arguments rather than constructing module-specific URLs.