Private MCP build · Setup guide

Connect your agent.
Start with a read.

What you need today

• An approved copy of the private build, Python 3.12+ and uv.
• An MCP client supporting local stdio servers.
• Your own Google Cloud project with the required YouTube services enabled, an OAuth client and a channel you are authorized to manage.

Planned onboarding: a shared Vurctube Google authorization flow, without asking each creator to configure a Cloud project. It still needs implementation and the applicable Google verification. It is not available in the current build.

1. Install the private build

From the checkout supplied for your pilot:

uv venv --python 3.12 .venv-mcp
uv pip install --python .venv-mcp/bin/python -e .
.venv-mcp/bin/vurctube --json profile list

2. Authorize a channel in your terminal

Use your own private OAuth client file. Replace the example path below; do not paste file contents or tokens into an agent conversation. Read the privacy policy and terms before using the tool.

.venv-mcp/bin/vurctube profile add mychannel \
  --client-json /absolute/private/client.json
.venv-mcp/bin/vurctube profile auth mychannel

Follow Google's consent screen and check the channel identity. Permissions must match the operations you intend to use. A successful local setup does not prove every service or restricted feature is enabled.

3. Add the MCP server to your agent

Configure a local stdio server named vurctube. Set its command to the absolute path of .venv-mcp/bin/vurctube-mcp inside your checkout, with no arguments. No API key, token or public server URL belongs in this configuration.

Codex configuration and independent MCP protocol connections have been tested. Other compatible clients still need their own end-to-end check.

4. Try a read-only request

For a metadata edit, ask for a preview first. Saving a proposal does not write to YouTube. Review the complete proposed change before approving that specific plan; check the execution record afterwards. Production writes have not yet completed live acceptance.

Know the current boundaries

• API adapters are not proof of account permissions, service enablement or live verification.
• No Content ID partner tools, large resumable uploads, automatic rollback or hosted multi-user service.
• Automatic retention maintenance is not yet delivered. The private build requires operator-managed data cleanup; do not use it as an unattended public service.
• Your chosen agent may send tool results to its model provider. Review that client's data controls before connecting a channel.

For disabled services or missing scopes, check the Google project and consent settings. Do not keep repeating requests or approve an uncertain write again. Contact contact@vurctne.com with a redacted error, never a credential.