NotebookBrain MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_MODEL | No | Model id used by the Gemini backend. | gemini-3.8-flash |
| GEMINI_API_KEY | No | API key for the official Gemini File Search backend. | |
| NOTEBOOKBRAIN_BACKEND | No | Backend to use: local (default, requires nothing), gemini, or notebooklm-py. | local |
| NOTEBOOKBRAIN_NOTEBOOK_ID | No | Notebook id required when using the notebooklm-py backend. | |
| NOTEBOOKBRAIN_ACCEPT_UNOFFICIAL | No | Required exact value for the unofficial notebooklm-py backend: i-accept-unofficial-google-api-risk. |
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_sourceA | Add a text source (a project note, ADR, runbook...) to the brain. Sensitive content (keys, tokens, private keys; plus personal data and confidentiality markers on the unofficial backend) is refused by the risk gate before it leaves the machine. |
| list_sourcesA | List the sources the brain can cite: source_id, title, backend, size, status. |
| askA | Answer a question from the added sources only. Returns answer text with [n] markers, citations [{n, source_id, source_title, quote, start, end}], backend and grounded (false when the sources do not contain an answer). |
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 3 tools
Each tool has a distinct action and resource: add_source writes a source, list_sources enumerates sources, and ask queries the accumulated sources. There is no plausible overlap in agent selection.
add_source and list_sources follow a clear verb_noun snake_case convention, and ask is also snake_case but is a bare verb. This is mostly consistent with a minor deviation.
The set is intentionally small and well-scoped for a source-backed question-answering server: ingestion, listing, and querying are the three core operations. Each tool earns its place and three tools fit within the recommended range.
The surface covers adding sources, listing them, and asking grounded questions, but lacks update/delete operations and a way to inspect or retrieve an individual source's contents. These are notable lifecycle gaps, though the core ask workflow is present.