Creator Brain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CBRAIN_VAULT | No | Path to the Creator Brain vault. Defaults to ~/CreatorBrain. | ~/CreatorBrain |
| GROQ_API_KEY | No | Optional Groq API key for background claim extraction. Can also be stored in ~/.cbrain/secrets.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_creatorA | Add a YouTube creator (handle like @JeremyEthier, or channel URL) to the brain and start building it. Returns quickly: the video list is queued and transcripts download in the background, so you can search what is ready right away. full=True fetches every video instead of the newest 30% plus the top winners. Tell the user the returned brain label and that more material keeps arriving. |
| add_videosA | Add more of a creator's videos to their brain. By default a brain holds the newest 30% plus top winners; every other upload is listed in the creator's ' - All Videos' note. Pick by title words (match= 'protein diet'), explicit video_ids, or top=N most-viewed. Use dry_run=True first to show the user the matches, then call again to add them. They download and get analysed in the background. |
| next_video_to_analyseA | YOU are the brain's reader. Returns one video's transcript (with [mm:ss] markers), the known topics and the rules for writing knowledge cards. Read it, write the claims yourself, then call submit_claims. Repeat to build the brain without any external AI key. Returns video=None when nothing is left. |
| submit_claimsA | Add your knowledge cards for a video. Each item: {"claim": one plain sentence, "quote": 6-40 words copied EXACTLY from the transcript, "t": "mm:ss", "topic": short Title Case topic (reuse known topics), "kind": advice|fact|protocol|warning|opinion}. Code checks every quote against the transcript and drops any that don't match word for word; the result says how many were kept. |
| list_topicsA | All topics with claim counts and creators. Use it to plan clean topic names and merges. |
| merge_topicsA | Rename/merge topics: {"Protein Intake": ["Daily Protein", "Protein Timing"], ...}. Only existing names are used; claims, topic notes, video links and search are rewritten, old names stay as aliases. Pause first. |
| rebuild_brainA | Re-render every note (clean names, key points, topic + related links, dashboards). Pause first. |
| pause_brainA | Pause background downloading/analysis (needed before merge_topics or rebuild_brain). |
| resume_brainB | Resume background work after maintenance. |
| brain_graphA | Start the live, animated graph of the brain on localhost and return its URL. Give the user the link: nodes pop in as videos and topics are added, and Replay animates how the brain was built. |
| update_creatorsA | Check one creator (or all of them) for new videos and queue anything new. Cheap and quick; it also runs automatically about once a day. New material appears in search as it finishes processing. |
| brain_statusA | How complete is the brain? Returns the brain label, percent built (searchable) and analysed, whether the background worker is running, failures with reasons and a rough ETA. Use it to tell the user how much of a creator is ready before relying on search results. |
| search_brainA | Search creators' transcripts and verified claims (call this BEFORE answering from memory). Returns short snippets, each with a timestamp URL: cite the video title and that URL for every point. Includes brain_completeness per creator: if it is below 100%, tell the user results may be missing videos. Use plain words, e.g. 'protein per day for muscle gain'; narrow with creators=['jeremy-ethier']. |
| get_topicA | Everything the brain has verified about one topic (e.g. 'Protein Intake') across all creators: claims with exact quotes and timestamp URLs, newest first. Names and synonyms are matched loosely. Cite the timestamp URLs when you use a claim. |
| compare_creatorsB | Compare what several creators say about a topic: per creator, their claims (with quotes and timestamp URLs) plus matching transcript passages. Use it to show where creators agree or disagree, and cite both sides. |
| my_profileA | Read the user's profile (Me.md): goal, level, age, weight, injuries, equipment, days_per_week, diet, notes. Read it before giving advice so the answer is personalised, and ask the user for fields that are empty. Pass updates={'goal': 'build muscle', 'days_per_week': 4} to save new facts the user tells you. |
| save_outputA | Save a finished plan, summary or answer into the vault (outputs/) so the user can open it in Obsidian. Always save plans with this tool. Put the timestamp URLs / video titles you relied on in sources. |
| suggest_creatorsA | Find YouTube channels worth adding for a topic (ranked by views in search results, excluding creators already in the brain). Show the list to the user and call add_creator only for the ones they choose. |
| brain_doctorA | Check the vault for problems (broken links, missing notes, failed videos, stale creators) and, with fix=True, repair what is safe. Run it if search looks wrong or status shows failures. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools occupy clearly distinct pipeline stages (add, analyse, submit, search, maintain), and descriptions disambiguate well. The weakest boundaries are add_videos vs. update_creators (both queue downloads) and search_brain vs. get_topic vs. compare_creators, which an agent could occasionally pick wrong.
Everything is snake_case and mostly verb_noun (add_creator, search_brain, merge_topics, save_output). A handful of noun-prefixed forms (brain_status, brain_doctor, brain_graph, my_profile) and the awkward next_video_to_analyse deviate from the dominant pattern but remain readable.
19 tools is on the heavy side, but each maps to a real stage: ingestion, analysis, topic curation, maintenance, discovery, and output. A few (pause_brain/resume_brain, rebuild_brain) could be folded together, keeping it just short of ideal.
Covers the full lifecycle: add creators/videos, background ingest, claim submission, topic listing/merging, rebuild, status, search, topic lookup, cross-creator comparison, profile, output saving, discovery, and repair. No obvious dead ends beyond optional destructive operations like removing a creator or correcting a bad claim.