Your channel, run by your agent.
Tell Claude, Codex or any MCP agent what needs doing. vurctube gives it hands: bulk metadata, every language you publish in, comment replies, across every channel you own. Official Google APIs. Your credentials. Your machine.
You
Put the membership link in the description of every episode of the series, in each video's own language. Don't touch anything else.
vurctube
11 videos found · 9 updated · 2 held for your approval · 6 languages
✓ descriptions updated, titles and tags left exactly as they were
✓ previous versions kept, each edit can be put back
470 of today's 10,000 Data API units used. The 2 held videos have hand-written descriptions that differ from the rest.
This is the workflow vurctube is being built to run. It is pre-alpha today: the API research is done, the design is underway, and the code is not written yet.
What it does
The work you would otherwise do by hand at eleven at night
Running a channel is mostly repetition: the same edit across forty videos, the same reply to the same question, the same subtitle upload five times over. That is exactly what an agent is good at, once it has a safe way in.
Bulk metadata
Retitle a season, fix a dead link in forty descriptions, swap a tag set. One instruction, every video, nothing else touched.
Every language you publish in
Titles and descriptions per language, caption tracks uploaded per language, and adding a sixth language without redoing the other five.
Comments
Find the ones that need an answer, draft the reply in the viewer's language, post it after you approve.
Every channel you run
A Chinese channel and its English-dub sister on two different Google accounts, each with its own credentials and its own history. Quota is counted per Google Cloud project, so channels that share a project share its daily budget.
Answers, not dashboards
Which caption language earns the watch time, which thumbnail gets the clicks, whether the new series is holding people. Asked in words, answered in words.
Playlists and shelves
Season playlists and channel shelves kept in order as episodes land, instead of drifting until someone notices.
Brakes
An agent with write access needs brakes
A bare API wrapper lets an agent overwrite the description on a video with a million views and offers no way back. vurctube is the layer that makes handing over the keys survivable.
Backup and rollback
Metadata edits read the current state first and keep a copy, so a title or description you regret goes back as it was. Actions the API cannot undo, such as rejecting a comment, are labelled as such before you approve them.
Dry run
See the exact request and its quota cost before anything leaves your machine.
Approval queue
Risky writes wait for a person. Google's policies require your express consent before an agent acts for you; this is where it lives.
Audit log
What the agent did, when, and the before and after of every field it touched.
Quota budget
Four separate daily buckets, counted as you go, so a caption batch stops before the wall instead of failing halfway.
One profile per channel
Separate credentials and separate data per channel, no cross-channel mixing.
Honest limits
What it will not pretend to do
These have no public API. They are done in YouTube Studio or the YouTube app, and vurctube tells you that instead of faking it with browser automation.
- Multi-language audio tracks
- Localized thumbnails
- Community posts
- Pin or heart a comment
- End screens and cards
- Create or edit membership tiers
- Premieres
Everything vurctube claims was checked against Google's own documentation on 12 September 2026, every statement quoted word for word, including the places where Google's pages disagree with each other. The full capability matrix ships with the tool.
Your data
Your credentials never reach us
vurctube runs entirely on your computer, against a Google Cloud project you create and control. There is no vurctube server, no database, no account to sign up for and no telemetry. Your OAuth token is written to a file only you can read and is sent only to Google. What the tool reads from your channel goes to your machine and to the agent you run it with, and nowhere else. The privacy policy has the specifics.