Environments and base URLs
Integrate against production. What staging, branch previews, and a local app answer on the MCP paths.
Production
https://app.vidext.comProduction is the place to integrate. Its MCP endpoints are:
https://app.vidext.com/api/mcp/operator # authenticated, your organization's data
https://app.vidext.com/api/mcp/docs # public, these docsOne host serves the app, both MCP servers, and the discovery layer, so OAuth metadata, tokens, and tools always point at the same origin. Access tokens are bound to that MCP endpoint: a token issued on one origin is not accepted on another.
The in-app setup page (Settings → MCP) always shows the production URL, whichever environment you open it from.
Staging is internal
https://staging.vidext.com is Vidext's internal validation environment. It answers on /api/mcp/*, because the MCP servers are validated there before a release, but it is not offered to integrators: there is no self-serve signup, no stability promise, and its data can change or disappear at any time. Nothing you build should point at it.
Branch previews and local apps
Branch preview deployments and a locally running app have no MCP server. /api/mcp/operator and /api/mcp/docs answer 404 there.
Point every client at the production URL, on every machine. Pass module IDs as typed tool arguments; there are no module-specific URLs.
Last updated on