berbotu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_WRITE_PAT | No | GitHub fine-grained Personal Access Token with Contents: Read and write on berbotu/vault, required for add_demo. | |
| BERBOTU_VAULT_PATH | Yes | Path to the Berbotu vault directory. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Returns 'OK' plus server name, version, vault path, current timestamp, process id, and Node.js version. Use this to confirm the Berbotu MCP server is reachable and configured correctly. |
| list_demosA | Lists demo submissions from the Berbotu vault, sorted newest-first by received_date. Each item has: artist, track title, status (stage), received date, and an optional 1-5 star score. Use this when the user asks about incoming submissions, the demo pipeline, A&R inbox, or anything like 'what demos have we got?'. Optional |
| list_releasesA | Lists track + EP releases from the Berbotu vault, sorted newest-first by release_date. Each item has: title, artist, release date, status (stage), and EP/single flag. Use this when the user asks about the label catalog, scheduled releases, what's coming out, what shipped, or anything about 'releases'. Optional |
| add_demoA | Creates a new demo entry in the Berbotu vault by committing a Markdown file to the berbotu/vault GitHub repo (path: 00 Releases/Demos/{ARTIST} - {TITLE}.md). Use this when the user wants to log a fresh submission — e.g. 'add a demo from RULACID called UNTITLED', or 'log a new demo from the email I just pasted'. REQUIRED: artist + track. Both must be non-empty strings. OPTIONAL: stage (default 'Listening'), received_date (default today UTC), notes (default empty). Refuses to overwrite if a demo with the same artist+title already exists — in that case the user should edit via admin.berbotu.com instead. On success returns the created file path, the full frontmatter that was written, and a permalink to the GitHub commit so the user can audit the change. |
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 4 tools
Each tool has a clearly distinct purpose: ping for health check, list_demos for demo submissions, list_releases for catalog releases, and add_demo for creating new entries. No overlapping resource or action.
Tools follow a consistent verb_noun pattern with snake_case (list_demos, list_releases, add_demo). ping is a simple verb but is standard and does not disrupt the pattern.
Four tools is small but well-scoped for a niche vault/music label server. It covers health, listing, and creation, though could add more operations in the future.
The core workflow—check health, view demos and releases, add new demos—is covered. Missing update/delete operations, but this is intentionally delegated to the admin web interface, so no critical dead ends.