Bundled Notes MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUNDLED_FIREBASE_UID | Yes | Firebase UID of the authenticated Bundled Notes user. | |
| BUNDLED_FIREBASE_API_KEY | Yes | Firebase API key for the Bundled Notes web app. | |
| BUNDLED_FIREBASE_REFRESH_TOKEN | Yes | Firebase refresh token for authenticating with the Bundled Notes account. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bundled_statusA | Report configuration and validate the Firebase refresh token with a real read. |
| bundled_current_userA | Return a safe account projection; purchase and authentication tokens are always omitted. |
| bundled_list_bundlesA | List bundles, optionally including archived bundles. |
| bundled_get_bundleA | Get one bundle and all known presentation/Kanban settings. |
| bundled_create_bundleB | Create a Notes, List, or Board bundle. Requires confirm=true. |
| bundled_update_bundleB | Partially update bundle details, layout, sorting, or display settings. |
| bundled_set_bundle_archivedB | Archive or restore a bundle without deleting its contents. |
| bundled_delete_bundleA | Permanently delete a bundle plus all entry and tag subdocuments. |
| bundled_list_entriesB | List notes/entries in one bundle. |
| bundled_get_entryB | Get an entry with Markdown content, tag IDs, state, and attachment metadata. |
| bundled_search_entriesB | Client-side text search matching the web app's local title/content search semantics. |
| bundled_create_entryC | Create a Markdown entry in a bundle. |
| bundled_update_entryB | Partially update entry text, tags, or pin state. |
| bundled_set_entry_stateA | Set archived, markedAsComplete, or pinned explicitly; never toggles blindly. |
| bundled_delete_entryB | Permanently delete one entry. Account-storage files are not deleted. |
| bundled_duplicate_entryA | Copy an entry. The copy gets a new document and numeric ID; destination tags are explicit. |
| bundled_move_entryA | Copy to the destination, verify it, then delete the source; rolls back the copy if source deletion fails. |
| bundled_list_tagsA | List bundle-local tags and subscribed global tags. |
| bundled_create_tagB | Create a local/global tag, optionally with completion, archive, or tag-swap task actions. |
| bundled_update_tagC | Partially update a local or global tag definition. |
| bundled_apply_tagB | Apply a tag; optionally execute its completion/archive/swap actions. |
| bundled_remove_tagB | Remove one tag reference from an entry. |
| bundled_delete_tagB | Delete a tag. By default refuses when entries or Kanban still reference it. |
| bundled_configure_kanbanC | Enable/configure a board using ordered tag IDs as columns. |
| bundled_move_kanban_entryC | Move an entry to one configured column, or to backlog with null. |
| bundled_list_templatesA | List user-created bundle templates. |
| bundled_create_templateB | Create a custom template from a bundle, copying local tags and optionally entries. |
| bundled_apply_templateC | Create a new bundle from a custom template. |
| bundled_delete_templateB | Permanently delete a custom template and its copied tags/entries. |
| bundled_list_attachmentsA | List account-level Files & Photos metadata without download tokens. |
| bundled_upload_attachmentA | Upload a local file to account storage and attach it to an entry (400 MiB maximum). |
| bundled_remove_attachmentA | Remove an attachment reference from an entry but keep the account-storage file. |
| bundled_delete_account_attachmentA | Permanently delete the account catalog record and storage object; detach references first. |
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 33 tools
Each tool targets a specific resource and action combination, with only minor overlap between update_entry and set_entry_state around pin state. Descriptions clearly distinguish attachment reference removal from account storage deletion.
All tools share the bundled_ prefix and follow a consistent verb_noun structure, with the only exceptions being status and current_user which are intuitively named. No style mixing.
At 33 tools, the set is substantial, exceeding the 25-tool threshold for appropriate scope. While each tool has a clear purpose, the number may overwhelm agents.
The surface covers the full lifecycle for bundles, entries, tags, templates, attachments, and Kanban configuration, with no obvious dead ends. The only minor gap is lack of template update or attachment download, but these are not critical.