Connecting Claude or Another MCP Client to a VidWorth Workspace: A Technical Walkthrough
Sep 28, 2026 · by Omar adel
How the OAuth-authenticated, workspace-scoped MCP connection between an AI client like Claude and VidWorth actually works, and what stays outside the AI's control.
Letting an AI assistant query business data is only useful if the access is scoped correctly — otherwise "connect Claude to my analytics" becomes a much bigger ask than the person making it intended. Here's what the connection actually involves.
The connection model
VidWorth exposes a remote, OAuth-authenticated, workspace-scoped MCP endpoint. In practical terms: an MCP client like Claude authenticates through OAuth, the same category of flow used by most modern app-to-app connections, and the access it's granted is scoped to a single VidWorth workspace — not the platform generally.
What "workspace-scoped" means
An agency running multiple client workspaces doesn't get one MCP connection that reaches across all of them by default. The scope is tied to the workspace that was authorized, which matters for anyone managing several client accounts and wanting to keep each client's data segmented from the others.
What the AI client can do once connected
It can query the data already inside that workspace — views, clicks, leads, bookings, revenue by video — and it can prepare actions such as identifying videos missing a tracked link. What it cannot do is write to a connected YouTube channel without a separate, explicit approval step; the OAuth connection grants scoped access to VidWorth's data and tools, not unrestricted control over YouTube itself. See How VidWorth's Approval Boundary Works for how that boundary is enforced regardless of which client is connected.
Setup at a glance
| Step | What happens |
|---|---|
| Initiate connection from the AI client | Client requests access to the VidWorth MCP endpoint |
| Authenticate via OAuth | Standard authorization flow, scoped to one workspace |
| Client sees available tools | Workspace data and prepared actions become queryable |
| Every write still requires approval | No step in this flow grants standing write access |
Where to go for exact steps
The precise authorization screens and endpoint details are maintained in the documentation rather than reproduced here, since setup screens change independently of this explanation of how the access model works. For the conceptual version of what the assistant can do day to day, see What Can an AI Assistant Actually Do Inside VidWorth via MCP?