REDDIT 原始帖子

How are you connecting Claude to your video library?

About 95% of my content workflow now happens inside Claude. I’ll start with a content idea, use Claude for audience research, and then have it help me turn that into a script. That part works surprisingly well. The bottleneck starts immediately afterward.…

原帖正文r/content_marketing

About 95% of my content workflow now happens inside Claude. I’ll start with a content idea, use Claude for audience research, and then have it help me turn that into a script. That part works surprisingly well. The bottleneck starts immediately afterward. Once I have the script, I still have to leave Claude, manually search through my video library, scrub through clips, and figure out which footage matches each part of the script. Claude knows what the video is supposed to say, but it has no idea what footage I already have. What I’d really like is a way for Claude to search or understand my existing video library—something like: “Find a close-up that fits this line” or “Show me clips related to this section of the script.” I signed up for one tool that claims to do something similar, but it’s still in closed beta and I haven’t received access. For people using Claude as part of their content or editing workflow, how are you handling this right now? Are you tagging and transcribing everything manually, using a media asset manager, building something with MCP, or just accepting that clip selection is still a separate manual step?

已收录讨论

2 条评论

u/AutoModerator

Moderator Announcement Read More » If this post doesn't follow the rules report it to the mods. Join our community Discord! I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

u/wilzerjeanbaptiste

MCP servers are the answer here. That's the open standard that lets Claude actually touch your tools instead of you copy-pasting between tabs. There are MCPs for Drive and Dropbox already, and more video platforms are shipping their own. Once Claude can read the library, the workflow you're describing gets wild. Ours goes idea to scheduled post without leaving the chat. Content ops is my day job, I run Aidelly, and we built the platform agent-first for exactly this: Claude connects over an MCP server and handles publishing and engagement across 11 platforms itself. For your bottleneck specifically, start with a Drive MCP and ruthless file naming. Boring, but it works.