Private remote MCP · Setup guide
Connect your agent.
Start with a read.
Access comes first. The remote service is live for one invited owner. Public signup, arbitrary client registration and Google sensitive-scope verification are not complete. Contact us about private testing; please do not email credentials.
Vurctube’s complete local automation pipeline has long supported short-drama localization and distribution. This guide covers the remote YouTube MCP connection for channel reads and owner-approved metadata edits. Migration of the complete pipeline to the cloud is underway. See cloud progress.
What you need today
- The invited Google account and its connected YouTube channel.
- A preregistered MCP client supporting Streamable HTTP and OAuth with PKCE. Native Codex and an official SDK client have passed private acceptance.
- Client/model-provider settings compatible with Google's Limited Use requirements. Review the data flow and retention policy and terms first.
No local connector installation or personal Google Cloud project is required for the remote pilot. The local CLI/stdio build is a separate private interface, not the onboarding path described here.
1. Add the remote connection
Use this endpoint in the registered client:
https://mcp.vurctube.com/mcpRead clients use mcp:read; a separately approved proposal client can also request mcp:metadata.propose. Both require an exact preregistered client ID and callback. An arbitrary new client cannot register itself. Never paste a Google refresh token, client secret or authorization URL into an agent conversation.
2. Authorize Google and your agent separately
Start sign-in from your MCP client and use your browser for Google consent. Vurctube requests openid, email and youtube.readonly; enabled metadata editing also requests youtube.force-ssl. That Google permission is broader than the remote tools: the pilot permits only title, description and tag edits, not uploads, publishing or deletion. Check the app name and channel, then separately approve the named agent and its return address. Analytics and Reporting scopes are not requested by this pilot.
Vurctube stores an encrypted Google credential copy on its hosted service. Your agent receives a separate Vurctube grant and the results of permitted reads, not that Google credential. The agent may forward results to a cloud model provider.
3. Try a read-only request
“Use Vurctube to read my connected channel and its latest five videos. Show the YouTube titles and links. Do not modify anything.”
Results reflect YouTube at the time of the request. Available information depends on the granted permissions and channel eligibility.
4. Review a metadata proposal
An approved proposal client can prepare a title, description or tag change. Open the returned Vurctube approval page, check the channel and exact before/after values, then approve or reject it yourself. Google permission alone does not approve a particular edit. The agent cannot make this browser decision on your behalf.
Vurctube checks for conflicting changes, sends an approved update once and reads back the result. A saved result is not a fresh approval request. If verification reports a mismatch or unknown outcome, inspect it before any new proposal; do not repeat the write or assume automatic rollback.
5. Manage or disconnect
Visit Manage connection to disconnect and delete Vurctube's stored channel profile and credential copy. This does not delete YouTube videos or copies in your agent's history. Google project-wide permissions can be revoked separately at Google app permissions.
The pilot connection expires within seven days. Agent access tokens refresh automatically within that limit; a fresh Google authorization is required when the connection expires. Browser identity reuse lasts up to eight hours. After that, identity-only sign-in can reuse a valid channel credential without asking for all YouTube permissions again. New scopes, revoked or expired credentials and new agent clients can still require consent.
Remote connection scope
This connection supports channel and video reads, plus title, description and tag edits independently approved by the owner. Remote access is managed separately from the complete local pipeline.
- Proposal tools require separate client permission and browser approval of each exact change.
- This remote connection does not offer uploads, publishing, deletes, comment/caption edits, Analytics reports or Content ID.
- Access is limited to the invited owner and registered clients; public registration is not available.
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 zw@vurctne.com with a redacted error, never a credential.