Chewbr MCP server

Your workflow is messy.
The model fills the gaps.

Chewbr connects your YouTube channel to a workflow that actually holds together. The MCP server hands that connection to Claude, or any AI assistant, with 33 live tools. So when you skip a step, the model catches it: it pulls your stats, scores your packaging, ticks the checklist, and locks the schedule. In plain English, in the chat you already have open.

Plan. Produce. Package. Post. Promote. Now by conversation.

The gaps, filled

Ask like a person.
It answers like a workflow.

Pull your YouTube stats. Score your title and thumbnail. Lock the publish time. Rank what to film next. Each one is a sentence in chat, and a real change in your Chewbr account.

One prompt, five tool calls

You say the outcome.
The model does the clicking.

Bigger asks chain tools together. Say Friday's upload should be handled and the model finds the video, scores the packaging, locks the schedule, and reports what is still blocking, all in one turn.

Uploads never fire on their own. The model stages and schedules; sending to YouTube happens when you say go.

The full toolkit

33 tools. Eight groups. One connected account.

Everything the model can reach, grouped the way you already think about the work. Pick a group, or let the tour run.

Capture and rank what to film next.

  • Capture an ideaDrop it straight into your inbox mid-chat
  • Rank the inboxPull every idea, ordered and ready
  • Sharpen an angleRework the hook without opening the app
  • Greenlight an ideaTurn it into a real video with a date
  • Clear dead ideasDrop the ones that will never work

Works where you already work.

MCP is an open standard, so the Chewbr server is not tied to one assistant. If your tool of choice speaks MCP, it can speak Chewbr.

  • Claude Desktop
  • Claude Code
  • Cursor
  • Windsurf
  • VS Code
  • GitHub Copilot
  • Any MCP client

This page is the tour, not the manual. Connection lives inside the app once you're signed in. Client names and marks belong to their owners; they appear here to show compatibility.

Chewbr MCP FAQ

Questions, answered.

What is the Chewbr MCP server?

The Chewbr MCP server connects your Chewbr account, and the YouTube channel linked to it, to AI assistants like Claude. It exposes 33 live tools covering ideas, videos, the 47-point checklist, title and thumbnail scoring, uploads, and channel analytics, so the model can do real workflow work from a normal chat.

What is MCP (Model Context Protocol)?

MCP is an open standard that lets AI assistants use tools from outside services. Any MCP-capable client, including Claude Desktop, Claude Code, Cursor, Windsurf, and GitHub Copilot, can connect to an MCP server and call its tools mid-conversation.

What can the model actually do with Chewbr?

It can pull your YouTube stats, score titles and thumbnails out of 100, rank your idea inbox, tick checklist tasks, move videos between phases, and stage and schedule uploads. You ask in plain English; the model picks the right tools and reports back.

Can the model upload to YouTube without me?

No. The model can stage a file and lock a publish time, but sending anything to YouTube only happens when you explicitly say go. You stay the publisher; it stays the assistant.

Do I need to be a developer to use it?

No. If you can type a sentence into a chat window, you can use the Chewbr MCP server. Connection lives inside the Chewbr app once you are signed in, and this page is just the tour.

Which AI assistants work with the Chewbr MCP server?

Any assistant that speaks MCP. That includes Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, and GitHub Copilot, with more MCP clients arriving as the standard spreads.

Stop letting the gaps win.

Chewbr keeps the checklist honest. The MCP server hands it to the model. All that is left is the part only you can do: make the video.