Add the VIDTREO MCP to Claude, Claude Code, Codex, or any MCP client with OAuth — then sign in and approve the permissions.

Connect Your Assistant

Every client connects to the same URL:

https://mcp.vidtreo.com/mcp

You need a VIDTREO account with access to at least one environment. There is no API key to copy: the client opens the VIDTREO sign-in page, you sign in with your usual account and approve the permissions, and the client keeps the connection.

Claude (Web and Desktop)

In Claude, open Settings → Connectors and click Add custom connector.

Enter a name — for example VIDTREO — and the URL https://mcp.vidtreo.com/mcp, then click Add.

Click Connect. Claude opens the VIDTREO sign-in page: sign in and approve the requested permissions.

Start a chat and ask, for example, "List my VIDTREO environments". You can turn the connector on or off for each chat from the chat's tools menu.

The connector is shared by Claude on the web and Claude Desktop: add it once and both can use it. Both display the VIDTREO recorder and player inside the conversation.

On Claude Team and Enterprise plans, an organization Owner may need to add the custom connector for the organization first. Each member then clicks Connect and signs in with their own VIDTREO account.

Claude Code

Add the server over HTTP, then authenticate from inside Claude Code:

claude mcp add --transport http vidtreo https://mcp.vidtreo.com/mcp

Start Claude Code, run /mcp, select vidtreo, and choose Authenticate. Your browser opens the VIDTREO sign-in page.

Claude Code has every tool, but it does not display MCP Apps: when you ask to record or play, the assistant gives you a link to the recorder or the recording in the VIDTREO dashboard.

Codex

codex mcp add vidtreo --url https://mcp.vidtreo.com/mcp
codex mcp login vidtreo

codex mcp login opens the VIDTREO sign-in page in your browser. codex mcp list shows whether the server is connected.

Other MCP Clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect with the same URL. The client discovers everything it needs from the server:

What	Where
MCP endpoint	`https://mcp.vidtreo.com/mcp`
Protected resource metadata	`https://mcp.vidtreo.com/.well-known/oauth-protected-resource/mcp`
Authorization server	`https://core.vidtreo.com` (metadata at `/.well-known/oauth-authorization-server`)
Client registration	Dynamic client registration, so no client ID needs to be created by hand
Flow	Authorization code with PKCE (`S256`), plus refresh tokens

A request without a valid token receives 401 with a WWW-Authenticate header that points to the metadata, which starts the sign-in in compliant clients.

When you connect, the VIDTREO consent screen lists the permissions (scopes) the assistant asks for. You choose which ones to grant, then select Authorize:

Scope	On the consent screen	Lets the assistant
`videos:read`	View videos	Search and read videos and audios, their transcripts and sharing settings; list lenses, analyses, and results; ask questions about a video; play recordings
`videos:write`	Create and edit videos	Rename recordings, reprocess transcripts, change sharing, invite and remove people, and upload recordings made in the conversation
`videos:delete`	Delete recordings	Delete videos and audios
`environment:read`	Read environment settings	List and read environments, and find your default environment when recording
`environment:write`	Edit environment settings	Create and update environments, and change your default environment
`intelligence:run`	Run intelligence on videos	Start analyses (uses credits)
`intelligence:manage`	Manage intelligence	Create, edit, publish, and delete lenses; activate them in environments; turn automatic analysis on or off
`offline_access`	Stay signed in	Stay connected without signing in again

The scope each tool needs is listed in the Tools reference. A tool that needs a permission you did not grant answers that the action is not allowed; reconnect to grant it.

Your Role Still Applies

Permissions decide what the connector may do; your role in the workspace decides what you may do. Every request is checked against both, so the assistant never does more than you could do in the dashboard. When either one does not allow an action, the tool answers:

Vidtreo refused this action: your role in the workspace or the permissions granted to this connector do not allow it.

For example, asking a question about a single video (ask_video) needs a role that can create videos — Owner, Admin, or Developer — even though it only needs the videos:read scope. See Intelligence permissions. The assistant also only sees the environments, recordings, and lenses your account can access.

Security

The MCP server verifies every access token — its signature, issuer, and audience — so a token issued for another service is rejected.
The server stores nothing. Each tool call is forwarded to the VIDTREO API with your token, where your role and the token's scopes are checked again.
The recorder in the conversation never receives your sign-in token: it gets a short-lived upload token for one environment.
Playback links are temporary and only reach the player; the assistant never sees them.

Default Environment

Recordings made from the assistant go to the environment you name. When you do not name one, they go to your default environment — the same one you set with Set as default in the dashboard — or, if you have none, to the first environment you can access.

Ask "Record into the Interviews environment from now on" and the assistant calls set_default_environment. The default is stored in VIDTREO, so it applies to every chat and also changes in the dashboard.

Disconnecting

Client	How
Claude	Settings → Connectors → VIDTREO → disconnect or remove
Claude Code	`claude mcp remove vidtreo`
Codex	`codex mcp logout vidtreo` to sign out, `codex mcp remove vidtreo` to remove it

To revoke an assistant's access from VIDTREO itself, open Company → Connected apps in the dashboard.

To use a different VIDTREO account, disconnect and connect again, then sign in with the other account.

Troubleshooting

What you see	Cause	What to do
`Vidtreo refused this action: your role in the workspace or the permissions granted to this connector do not allow it.`	Your role or the granted scopes do not allow the action	Ask an Owner or Admin for a role that allows it, or reconnect and grant the missing permission
`Not found: …`	The recording, environment, or lens does not exist or is in an environment you cannot access	Ask the assistant to search for it again, or check that you have access to its environment
`The user has no environments to record into. Create one with create_environment.`	Your account cannot access any environment	Ask the assistant to create one, or ask an Admin for access
`This video has no completed analysis yet. …`	`ask_video` needs a completed analysis	Ask the assistant to analyze the video first — see Intelligence in the chat
The client keeps asking you to sign in	The session expired or was revoked	Reconnect the connector and sign in again
No recorder or player appears	The client does not display MCP Apps	Use the link the assistant gives you; it opens the recorder or the recording in the dashboard

Connect Your Assistant

On this page